[pypy-svn] r64426 - pypy/trunk/pypy/doc

[pedronis at codespeak.net]

Author: pedronis
Date: Mon Apr 20 00:24:42 2009
New Revision: 64426

Modified:
   pypy/trunk/pypy/doc/release-1.1.0.txt
Log:
porting after the fact tweaks

Modified: pypy/trunk/pypy/doc/release-1.1.0.txt
==============================================================================
--- pypy/trunk/pypy/doc/release-1.1.0.txt	(original)
+++ pypy/trunk/pypy/doc/release-1.1.0.txt	Mon Apr 20 00:24:42 2009
@@ -23,15 +23,15 @@
 ==========================
 
   - More of CPython's standard library extension modules are supported,
-    among them ctypes, sqlite3, csv, and many more. Most of these modules 
-    extension are fully supported under Windows as well.
+    among them ctypes, sqlite3, csv, and many more. Most of these extension 
+    modules are fully supported under Windows as well.
 
     http://codespeak.net/pypy/dist/pypy/doc/cpython_differences.html
     http://morepypy.blogspot.com/2008/06/pypy-improvements.html
 
   - Through a large number of tweaks, performance has been improved by
     10%-50% since the 1.0 release. The Python interpreter is now between
-    0.8-2x (and in some corner case 3-4x) of the speed of CPython. A large
+    0.8-2x (and in some corner case 3-4x) slower than CPython. A large
     part of these speed-ups come from our new generational garbage
     collectors.
 
@@ -126,7 +126,7 @@
 
 The framework allows for alternative frontends and for alternative
 backends, currently C, Java and .NET.  For our main target "C", we can
-can "mix in" different garbage collectors and threading models,
+"mix in" different garbage collectors and threading models,
 including micro-threads aka "Stackless".  The inherent complexity that
 arises from this ambitious approach is mostly kept away from the Python
 interpreter implementation, our main frontend.