docs/tasks.html: It's raptor doing the upstreaming

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/tasks.html b/docs/tasks.html
index 3d01587..d0dd8f1 100644
--- a/docs/tasks.html
+++ b/docs/tasks.html
@@ -65,16 +65,16 @@
 							upstreamed into coreboot. This is not as simple as just releasing the code; coreboot has a very strict code
 							review process (in place to ensure quality control). The patches will have to be split up, with people's
 							concerns and comments addressed over a long period, with patches constantly rebased to keep up with the
-							latest coreboot master branch. In order to get this done in a decent enough time frame, Timothy will need
+							latest coreboot master branch. In order to get this done in a decent enough time frame, Raptor Engineering will need
 							to work on a more-or-less full-time basis. The funding amounts that he has asked for, are as follows:
 							<ul>
 								<li>35K USD - This pays for basic support (Fam10h)</li>
 								<li>+15K USD (stretch goal) - This pays for S3 (suspend/resume) and text-mode graphics initialization</li>
 								<li>+40K USD (stretch goal) - Fam15h CPU support</li>
 							</ul>
-							Although Timothy would be working for many months to get this upstreamed (merged in coreboot's master branch
+							Although Raptor would be working for many months to get this upstreamed (merged in coreboot's master branch
 							in the git repository), libreboot would merge it more or less instantly, probably in the same week that the
-							code is released for review. Timothy would also of course be rebasing the patches on a regular basis, as part
+							code is released for review. Raptor would also of course be rebasing the patches on a regular basis, as part
 							of the review process, so even if it takes longer for the patches to be merged in coreboot, libreboot would have
 							support for this board.<br/><br/>