[pypy-svn] rev 1500 - pypy/trunk/doc/funding

[dinu at codespeak.net]

Author: dinu
Date: Wed Oct  1 14:03:52 2003
New Revision: 1500

Modified:
   pypy/trunk/doc/funding/B6.1_plan_introduction.txt
Log:
fixed some types

Modified: pypy/trunk/doc/funding/B6.1_plan_introduction.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.1_plan_introduction.txt	(original)
+++ pypy/trunk/doc/funding/B6.1_plan_introduction.txt	Wed Oct  1 14:03:52 2003
@@ -154,7 +154,7 @@
 The main lack of flexibility in CPython stems from the
 fact that all structures are hard-coded in C, and there is
 no abstraction layer. PyPy does provide this abstraction layer,
-since it's RPython implementation is not meant to be
+since its RPython implementation is not meant to be
 executed directly, but goes though a code generator which
 produces the actual machine code. This layer is highly configurable.
 
@@ -189,14 +189,14 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Since the standard object space allows coexistence of different
   implementations of the same type, we can develop
-  **several object implementations** .
+  **several object implementations**.
   We will develop heuristics to switch between different
   implementations during execution.
   The goal is to study the efficiency of different approaches,
   with the possibility to change the default implementation
   if favor of a different one, not known in CPython.
   Some object layouts will further exist in parallel, if their
-  efficiency is highly application dependant..
+  efficiency is highly application dependant.
 
 WP43_: Translator Optimisations
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~