Author: Armin Rigo <ar...@tunes.org> Branch: Changeset: r64814:da8f1e729f4d Date: 2013-06-06 20:25 +0200 http://bitbucket.org/pypy/pypy/changeset/da8f1e729f4d/
Log: issue1501: minor English fixes diff --git a/pypy/doc/getting-started-dev.rst b/pypy/doc/getting-started-dev.rst --- a/pypy/doc/getting-started-dev.rst +++ b/pypy/doc/getting-started-dev.rst @@ -8,7 +8,8 @@ interpreter is written mostly in RPython (with pieces in Python), while the RPython compiler is written in Python. The hard to understand part is that Python is a meta-programming language for RPython, that is, -RPython is considered from live objects **after** the imports are done. +"being valid RPython" is a question that only makes sense on the +live objects **after** the imports are done. This might require more explanation. You start writing RPython from ``entry_point``, a good starting point is ``rpython/translator/goal/targetnopstandalone.py``. This does not do all that @@ -37,7 +38,7 @@ In this example ``entry_point`` is RPython, ``add`` and ``sub`` are RPython, however, ``generator`` is not. -A good introductory level articles are available: +The following introductory level articles are available: * Laurence Tratt -- `Fast Enough VMs in Fast Enough Time`_. _______________________________________________ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
