[pypy-svn] r51634 - pypy/extradoc/talk/pycon2008

[arigo at codespeak.net]

Author: arigo
Date: Tue Feb 19 16:31:37 2008
New Revision: 51634

Modified:
   pypy/extradoc/talk/pycon2008/sprint.txt
Log:
Only typos


Modified: pypy/extradoc/talk/pycon2008/sprint.txt
==============================================================================
--- pypy/extradoc/talk/pycon2008/sprint.txt	(original)
+++ pypy/extradoc/talk/pycon2008/sprint.txt	Tue Feb 19 16:31:37 2008
@@ -7,8 +7,8 @@
 a very flexible compiler toolchain which can compile so called RPython
 (restricted Python, a subset of Python without dynamic features) into
 a variety of platforms including C/POSIX, JVM and CLI. PyPy also features
-set of experimental features, like different gcs or different threading
-models, which makes it a good platform to experiment with python language.
+a set of experimental features, like different GCs or different threading
+models, which makes it a good platform to experiment with the python language.
 
 Sprint leader: Maciej Fijalkowski (fijall at gmail.com)
                XXX holger?
@@ -21,21 +21,21 @@
 repository and all documentation are available on the website.
 
 Some instructions: This sprint is newcomer-friendly sprint. We'll present
-PyPy tutorial and code-walk on sunday afternoon. List of task is as usual
+a PyPy tutorial and code-walk on Sunday afternoon. The list of task is as usual
 very long and depending on attendees. It's suggested that people would
 come to an IRC and chat a bit to have a clue what is feasible on a sprint
 and what is not. For example, we can work on:
 
 * JVM backend bindings for Java libraries
-* Extending pypy necessary for software X to run
+* Extending pypy as necessary for software X to run
 * Adding more modules to pypy
 * Sketching ctypes-based software, killing dependency on C modules
   written using C/CPython API.
 * Optimizing certain parts of pypy for certain micro-benchmarks.
 * XXX whatever...
 
-Software requirements: That depends on a thing that people would like to
-work on, but in general pygame, libgc and libffi are very very usefull (although
-not needed). PyPy checkout, gcc and such things are a must. For people
-wanting to work on particular backends, aproprietly Java, Mono (or .NET),
+Software requirements: the details depends on what people would like to
+work on, but in general pygame, libgc and libffi are very very useful (although
+not needed). A PyPy checkout, gcc and such things are a must. For people
+wanting to work on particular backends, appropriately Java, Mono (or .NET),
 spidermonkey are needed.