[pypy-svn] r3813 - pypy/trunk/doc/funding

[hpk at codespeak.net]

Author: hpk
Date: Tue Apr  6 12:31:30 2004
New Revision: 3813

Modified:
   pypy/trunk/doc/funding/B6.0_detailed_implementation.txt
Log:
some minor grammar/typo fixing 



Modified: pypy/trunk/doc/funding/B6.0_detailed_implementation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.0_detailed_implementation.txt	(original)
+++ pypy/trunk/doc/funding/B6.0_detailed_implementation.txt	Tue Apr  6 12:31:30 2004
@@ -355,7 +355,7 @@
 into the interpreter itself. These include transparent interfaces to remote
 objects (like CORBA, Java RMI...), transparent distribution of objects, and
 transparent distribution of processes themselves. For example, a foreseen
-solution for the CORBA model would be to design a proxying Object Space that
+solution for the CORBA model would be to design a Proxy Object Space that
 delegates operations to a remote CORBA object server over the network, thus
 hiding the complexities of the underlying protocols. We will also study
 approaches enabling transparent distributed execution, i.e. in which the
@@ -461,7 +461,7 @@
 Documentation and Dissemination
 -------------------------------
 
-The documentational aspect of the dissemination goal is handled by one of the
+The documentation aspect of the dissemination goal is handled by one of the
 few workpackages that run for the whole duration of the project.
 
 Each sprint, as well as the regular progress of non-sprint development, will
@@ -496,7 +496,7 @@
 fundamental concepts, as appropriate to the audience and the subject matter. 
 
 To ensure stakeholder participation and feedback that goes beyond the
-python community, wp14_ also consists of arranging workshops ( 6 in total)
+python community, WP14_ also consists of arranging workshops ( 6 in total)
 to disseminate the ongoing process- and development progress.The majority
 of the workshops are going to target important stakeholder groups and will
 primarily focus on disseminating PyPy results from an implementation
@@ -566,8 +566,8 @@
 granted that the risks associated with the following decisions are almost
 non-existent at this point:
 
-- writing a Python interpreter in Python is not only possible -- it is, in
-  proven fact, markedly faster and easier than in C.
+- writing a Python interpreter in Python is not only possible -- it is
+  markedly faster and easier to do than in a low level language like C.
 
 - following some of the basic design decisions of CPython (the internals of
   whom most of us are intimately familiar with) leads to fast development and