Commits

Martin Matusiak  committed b3db056

fix typos and awkward wording

  • Participants
  • Parent commits cbb086c
  • Branches improve-docs-fixes

Comments (0)

Files changed (1)

File pypy/doc/you-want-to-help.rst

 * Because of the above, we are very serious about Test Driven Development.
   It's not only what we believe in, but also that PyPy's architecture is
   working very well with TDD in mind and not so well without it. Often
-  the development means progressing in an unrelated corner, one unittest
+  development means progressing in an unrelated corner, one unittest
   at a time; and then flipping a giant switch, bringing it all together.
   (It generally works out of the box.  If it doesn't, then we didn't
-  write enough unit tests.)  It's worth repeating - PyPy
-  approach is great if you do TDD, not so great otherwise.
+  write enough unit tests.)  It's worth repeating - PyPy's
+  approach is great if you do TDD, and not so great otherwise.
 
 * PyPy uses an entirely different set of tools - most of them included
-  in the PyPy repository. There is no Makefile, nor autoconf. More below
+  in the PyPy repository. There is no Makefile, nor autoconf. More below.
 
 
 Architecture
 * :doc:`RPython <rpython:rpython>` is the language in which we write interpreters. Not the entire
   PyPy project is written in RPython, only the parts that are compiled in
   the translation process. The interesting point is that RPython has no parser,
-  it's compiled from the live python objects, which make it possible to do
+  it's compiled from the live python objects, which makes it possible to do
   all kinds of metaprogramming during import time. In short, Python is a meta
   programming language for RPython.
 
   The RPython standard library is to be found in the ``rlib`` subdirectory.
 
-* The translation toolchain - this is the part that takes care about translating
+* The translation toolchain - this is the part that takes care of translating
   RPython to flow graphs and then to C. There is more in the :doc:`architecture <architecture>`
   document written about it.
 
   that turns it into machine code.  Writing a new backend is a
   traditional way to get into the project.
 
-* Garbage Collectors (GC): as you can notice if you are used to CPython's
+* Garbage Collectors (GC): as you may notice if you are used to CPython's
   C code, there are no ``Py_INCREF/Py_DECREF`` equivalents in RPython code.
   :doc:`rpython:garbage-collection` is inserted
   during translation.  Moreover, this is not reference counting; it is a real