[Python-checkins] devguide: devguide: fix some typos

[georg.brandl]

http://hg.python.org/devguide/rev/9cf7dc7aca86
changeset:   501:9cf7dc7aca86
user:        Georg Brandl <georg at python.org>
date:        Tue Apr 03 09:12:53 2012 +0200
summary:
  devguide: fix some typos

files:
  buildbots.rst     |  2 +-
  committing.rst    |  4 ++--
  communication.rst |  4 ++--
  compiler.rst      |  2 +-
  documenting.rst   |  6 +++---
  faq.rst           |  6 +++---
  gdb.rst           |  2 +-
  grammar.rst       |  4 ++--
  triaging.rst      |  2 +-
  9 files changed, 16 insertions(+), 16 deletions(-)


diff --git a/buildbots.rst b/buildbots.rst
--- a/buildbots.rst
+++ b/buildbots.rst
@@ -156,7 +156,7 @@
 ------------------
 
 While we try to make the test suite as reliable as possible, some tests do
-not reach a perfect level of reproduceability.  Some of them will sometimes
+not reach a perfect level of reproducibility.  Some of them will sometimes
 display spurious failures, depending on various conditions.  Here are common
 offenders:
 
diff --git a/committing.rst b/committing.rst
--- a/committing.rst
+++ b/committing.rst
@@ -399,7 +399,7 @@
 If you are coming from Subversion, you might be surprised by Mercurial
 :ref:`merges <hg-merge>`.
 Despite its name, ``svnmerge`` is different from ``hg merge``: while ``svnmerge``
-allows to cherrypick individual revisions, ``hg merge`` can only merge whole
+allows to cherry-pick individual revisions, ``hg merge`` can only merge whole
 lines of development in the repository's :abbr:`DAG (directed acyclic graph)`.
 Therefore, ``hg merge`` might force you to review outstanding changesets by
 someone else that haven't been merged yet.
@@ -503,7 +503,7 @@
 
 In this scheme, your work will probably consist of many commits (some of
 them merges).  If you want to upload a patch for review somewhere, you need
-a single agregate patch.  This is where having a dedicated named branch
+a single aggregate patch.  This is where having a dedicated named branch
 ``mywork`` gets handy.
 
 First ensure that you have pulled *and merged* all changes from the main
diff --git a/communication.rst b/communication.rst
--- a/communication.rst
+++ b/communication.rst
@@ -48,8 +48,8 @@
 
 A complete list of Python mailing lists can be found at http://mail.python.org.
 Most lists are also mirrored at http://news.gmane.org/ and can be read and
-posted to in various ways, including via web browers, NNTP newsreaders, and
-RSS feed readers. 
+posted to in various ways, including via web browsers, NNTP newsreaders, and
+RSS feed readers.
 
 .. _issue tracker: http://bugs.python.org
 .. _new-bugs-announce: http://mail.python.org/mailman/listinfo/new-bugs-announce
diff --git a/compiler.rst b/compiler.rst
--- a/compiler.rst
+++ b/compiler.rst
@@ -186,7 +186,7 @@
 of Python uses reference counting, there is extra support added
 to the arena to cleanup each PyObject that was allocated.  These cases
 are very rare.  However, if you've allocated a PyObject, you must tell
-the arena about it by calling PyArena_AddPyObject().
+the arena about it by calling ``PyArena_AddPyObject()``.
 
 
 Parse Tree to AST
diff --git a/documenting.rst b/documenting.rst
--- a/documenting.rst
+++ b/documenting.rst
@@ -6,7 +6,7 @@
 The Python language has a substantial body of documentation, much of it
 contributed by various authors. The markup used for the Python documentation is
 `reStructuredText`_, developed by the `docutils`_ project, amended by custom
-directives and using a toolset named `Sphinx`_ to postprocess the HTML output.
+directives and using a toolset named `Sphinx`_ to post-process the HTML output.
 
 This document describes the style guide for our documentation as well as the
 custom reStructuredText markup introduced by Sphinx to support Python
@@ -108,7 +108,7 @@
 
 Apple style guide recommends the use of title case in section titles.
 However, rules for which words should be capitalized in title case
-vary greaty between publications.
+vary greatly between publications.
 
 In Python documentation, use of sentence case in section titles is
 preferable, but consistency within a unit is more important than
@@ -327,7 +327,7 @@
 
 List markup is natural: just place an asterisk at the start of a paragraph and
 indent properly.  The same goes for numbered lists; they can also be
-autonumbered using a ``#`` sign::
+automatically numbered using a ``#`` sign::
 
    * This is a bulleted list.
    * It has two items, the second
diff --git a/faq.rst b/faq.rst
--- a/faq.rst
+++ b/faq.rst
@@ -475,7 +475,7 @@
  hg add PATH
 
 If ``PATH`` is a directory, Mercurial will recursively add any files in that
-directory and its descendents.
+directory and its descendants.
 
 If you want Mercurial to figure out by itself which files should be added
 and/or removed, just run::
@@ -534,7 +534,7 @@
 
 .. note::
    If you do not like the default text editor Mercurial uses for
-   entering commmit messages, you may specify a different editor,
+   entering commit messages, you may specify a different editor,
    either by changing the ``EDITOR`` environment variable or by setting
    a Mercurial-specific editor in your global ``.hgrc`` with the ``editor``
    option in the ``[ui]`` section.
@@ -562,7 +562,7 @@
  hg status
 
 will list any pending changes in the working copy.  These changes will get
-commited to the local repository if you issue an ``hg commit`` without
+committed to the local repository if you issue an ``hg commit`` without
 specifying any path.
 
 Some
diff --git a/gdb.rst b/gdb.rst
--- a/gdb.rst
+++ b/gdb.rst
@@ -131,7 +131,7 @@
     the python source.
 
 ``py-up`` and ``py-down``
-  The ``py-up`` and ``py-down`` commands are analagous to gdb's regular ``up``
+  The ``py-up`` and ``py-down`` commands are analogous to gdb's regular ``up``
   and ``down`` commands, but try to move at the level of CPython frames, rather
   than C frames.
 
diff --git a/grammar.rst b/grammar.rst
--- a/grammar.rst
+++ b/grammar.rst
@@ -39,7 +39,7 @@
 * Parser/pgen needs to be rerun to regenerate Include/graminit.h and
   Python/graminit.c. (make should handle this for you.)
 
-* Python/symbtable.c: This handles the symbol collection pass
+* Python/symtable.c: This handles the symbol collection pass
   that happens immediately before the compilation pass.
 
 * Python/compile.c: You will need to create or modify the
@@ -60,7 +60,7 @@
 
 * Documentation must be written!
 
-* After everything's been checked in, you're likely to see a new
+* After everything has been checked in, you're likely to see a new
   change to Python/Python-ast.c.  This is because this
   (generated) file contains the hg version of the source from
   which it was generated.  There's no way to avoid this; you just
diff --git a/triaging.rst b/triaging.rst
--- a/triaging.rst
+++ b/triaging.rst
@@ -180,7 +180,7 @@
 attention. Use the :ref:`experts` to know who wants to be added to the nosy
 list for issues targeting specific areas.
 
-If you have Javascript enabled and permission to edit the nosy list, you can
+If you have JavaScript enabled and permission to edit the nosy list, you can
 use the ``[+]`` button to add yourself to the nosy (remember to click on
 "Submit Changes" afterwards).  Note that you are added to the nosy
 automatically when you submit a message.

-- 
Repository URL: http://hg.python.org/devguide