--- a/Allura/docs/platform.rst
+++ b/Allura/docs/platform.rst
@@ -13,7 +13,7 @@
Before we get into the details of how to extend the Allura platform, perhaps
it would be smart to explain some of the big pieces and why there are there.
-We wanted PyForge tools to be fast, we needed them to scale, and we had some
+We wanted Allura tools to be fast, we needed them to scale, and we had some
complex requirements for data storage and extensibility. So, we needed a
**fast,** flexible, and easy to use data persistence system.
@@ -39,7 +39,7 @@
In spite of the power and flexibility of the Roundup HyperTable
implementation, we had some concerns about performance and scalability.
-Fortunately several of the PyForge authors (including me) used MongoDB
+Fortunately several of the Allura authors (including me) used MongoDB
in rewriting the download flow of SourceForge.net, and knew that it could
handle huge loads (we saturated a 2gb network connection on the server
with 6% cpu utilization).
@@ -78,7 +78,7 @@
onto another queue.
Nearly everything in Roundup is implemented as either an auditor or a reactor,
-and PyForge definitely steals that idea and runs with it.
+and Allura definitely steals that idea and runs with it.
TODO: Finish reactor overview (after reactor code is written).
@@ -94,7 +94,7 @@
:alt: App Tools
:align: right
-When you write PyForge tools, you'll get lots of stuff for free:
+When you write Allura tools, you'll get lots of stuff for free:
* Search-ability of your Artifacts
* Artifact versioning for accountability and transparency