[pypy-commit] pypy improve-docs: Merged in numerodix/pypy/improve-docs-fixes (pull request #262)

[mjacob]

Author: Manuel Jacob <me at manueljacob.de>
Branch: improve-docs
Changeset: r72668:79d59d37eb63
Date: 2014-08-03 18:14 +0200
http://bitbucket.org/pypy/pypy/changeset/79d59d37eb63/

Log:	Merged in numerodix/pypy/improve-docs-fixes (pull request #262)

	various minor doc fixes

diff --git a/pypy/doc/build.rst b/pypy/doc/build.rst
--- a/pypy/doc/build.rst
+++ b/pypy/doc/build.rst
@@ -61,6 +61,9 @@
 bz2
     libbz2
 
+lzma (required for PyPy3)
+    liblzma
+
 sqlite3
     libsqlite3
 
@@ -81,11 +84,15 @@
     apt-get install gcc make libffi-dev pkg-config libz-dev libbz2-dev \
     libsqlite3-dev libncurses-dev libexpat1-dev libssl-dev
 
+For PyPy3 you will also need ``liblzma-dev``.
+
 On Fedora::
 
     yum install gcc make libffi-devel pkgconfig zlib-devel bzip2-devel \
     lib-sqlite3-devel ncurses-devel expat-devel openssl-devel
 
+For PyPy3 you will also need ``xz-devel``.
+
 On Mac OS X, most of these build-time dependencies are installed alongside
 the Developer Tools. However, note that in order for the installation to
 find them you may need to run::
diff --git a/pypy/doc/cpython_differences.rst b/pypy/doc/cpython_differences.rst
--- a/pypy/doc/cpython_differences.rst
+++ b/pypy/doc/cpython_differences.rst
@@ -75,9 +75,6 @@
     zipimport
     zlib
 
-  When translated to Java or .NET, the list is smaller; see
-  :source:`pypy/config/pypyoption.py` for details.
-
   When translated on Windows, a few Unix-only modules are skipped,
   and the following module is built instead:
 
diff --git a/pypy/doc/index.rst b/pypy/doc/index.rst
--- a/pypy/doc/index.rst
+++ b/pypy/doc/index.rst
@@ -110,7 +110,7 @@
 .. _here: http://www.tismer.com/pypy/irc-logs/pypy/
 .. _Development mailing list: http://mail.python.org/mailman/listinfo/pypy-dev
 .. _Commit mailing list: http://mail.python.org/mailman/listinfo/pypy-commit
-.. _Development bug/feature tracker: https://bugs.pypy.org/
+.. _Development bug/feature tracker: https://bitbucket.org/pypy/pypy/issues
 
 
 Indices and tables
diff --git a/pypy/doc/you-want-to-help.rst b/pypy/doc/you-want-to-help.rst
--- a/pypy/doc/you-want-to-help.rst
+++ b/pypy/doc/you-want-to-help.rst
@@ -14,14 +14,14 @@
 * 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
@@ -32,13 +32,13 @@
 * :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.
 
@@ -67,7 +67,7 @@
   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