Fix spelling

git-svn-id: https://svn.code.sf.net/p/docutils/code/trunk/docutils@8860 929543f6-e4f2-0310-98a6-ba3bd3dd1d04

6 files changed, 19 insertions, 19 deletions

diff --git a/docs/dev/policies.txt b/docs/dev/policies.txt
index accb89c22..a623087ce 100644
--- a/docs/dev/policies.txt
+++ b/docs/dev/policies.txt
@@ -620,7 +620,7 @@ ways to keep the Docutils code accessible during development:
    __ repository.html
 
 2. Create a symlink to the docutils package directory somewhere in the
-   module serach path (``sys.path``), e.g., ::
+   module search path (``sys.path``), e.g., ::
 
      ln -s ~/projects/docutils/docutils \
           /usr/local/lib/python2.7/site-packages/
@@ -688,7 +688,7 @@ The Wiki
 
 There is a development wiki at http://docutils.python-hosting.com/ as
 a scratchpad for transient notes.  Please use the repository for
-permament document storage.
+permanent document storage.
 
 Extensions and Related Projects
 ===============================
diff --git a/docs/dev/pysource.txt b/docs/dev/pysource.txt
index 5184e4e61..190781f39 100644
--- a/docs/dev/pysource.txt
+++ b/docs/dev/pysource.txt
@@ -54,7 +54,7 @@ goes something like this:
 
 I've had trouble reconciling the roles of input parser and output
 writer with the idea of modes ("readers" or "directors").  Does the
-mode govern the tranformation of the input, the output, or both?
+mode govern the transformation of the input, the output, or both?
 Perhaps the mode should be split into two.
 
 For example, say the source of our input is a Python module.  Our
diff --git a/docs/dev/repository.txt b/docs/dev/repository.txt
index 1eb1b4c26..df01f2e7c 100644
--- a/docs/dev/repository.txt
+++ b/docs/dev/repository.txt
@@ -147,7 +147,7 @@ __ http://sourceforge.net/p/forge/documentation/svn/
 Setting Up Your Subversion Client For Development
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Before commiting changes to the repository, please ensure that the
+Before committing changes to the repository, please ensure that the
 following lines are contained (and uncommented) in your local
 ~/.subversion/config file, so that new files are added with the
 correct properties set::
diff --git a/docs/dev/rst/alternatives.txt b/docs/dev/rst/alternatives.txt
index 2b1ca7220..949d03a9c 100644
--- a/docs/dev/rst/alternatives.txt
+++ b/docs/dev/rst/alternatives.txt
@@ -513,7 +513,7 @@ used square brackets for phrase-links.  I changed my mind because:
    etc. names) into hyperlinks is a useful feature.  PyDoc recognizes
    identifiers heuristically, but it doesn't take much imagination to
    come up with counter-examples where PyDoc's heuristics would result
-   in embarassing failure.  I wanted to do it deterministically, and
+   in embarrassing failure.  I wanted to do it deterministically, and
    that called for syntax.  I called this construct "interpreted
    text".
 
@@ -838,7 +838,7 @@ Currently reStructuredText has two hyperlink syntax variations:
     - The plaintext is readable.
     - Each target may be reused multiple times (e.g., just write
       ``"reference_"`` again).
-    - No syncronized ordering of references and targets is necessary.
+    - No synchronized ordering of references and targets is necessary.
 
   + Disadvantages:
 
@@ -996,7 +996,7 @@ A new type of "inline external hyperlink" has been proposed.
    (reference/target pairs must be proximate [refA trgA refB trgB],
    not interleaved [refA refB trgA trgB] or nested [refA refB trgB
    trgA]).  This variation is too problematic; references and inline
-   external targets will have to be kept imediately adjacent (see (3)
+   external targets will have to be kept immediately adjacent (see (3)
    below).
 
    The ``"reference__ __<target>"`` syntax is actually for "anonymous
@@ -1086,7 +1086,7 @@ maintainable web pages.  The arguments go something like this:
 
   To which I said, "So use anonymous hyperlinks."
 
-- Anonymous hyperlinks are difficult to maintain becuase the
+- Anonymous hyperlinks are difficult to maintain because the
   references and targets have to be kept in sync.
 
   "So keep the targets close to the references, grouped after each
@@ -1278,7 +1278,7 @@ Syntax for Line Blocks
   (Awful, and arguably invalid, since in Japanese the word "haiku"
   contains three syllables not two.)
 
-  This idea was superceded by the rules for escaped whitespace, useful
+  This idea was superseded by the rules for escaped whitespace, useful
   for `character-level inline markup`_.
 
 * In a `2004-02-22 docutils-develop message`__, Jarno Elonen proposed
@@ -2339,7 +2339,7 @@ __ http://thread.gmane.org/gmane.text.docutils.devel/1386
 
 7. "I'd prefer to see double-dot-space / command / double-colon as the
    standard Docutils markup-marker.  It's unusual enough to avoid
-   being accidently used.  Everything that starts with a double-dot
+   being accidentally used.  Everything that starts with a double-dot
    should end with a double-colon."
 
    That would increase the punctuation verbosity of some constructs
diff --git a/docs/dev/semantics.txt b/docs/dev/semantics.txt
index 07b28de5e..5a6742465 100644
--- a/docs/dev/semantics.txt
+++ b/docs/dev/semantics.txt
@@ -53,7 +53,7 @@ prescribes a methodology.
             default).
 
       :Return:
-          - a list of indented lines with mininum indent removed;
+          - a list of indented lines with minimum indent removed;
           - the amount of the indent;
           - whether or not the block finished with a blank line or at
             the end of `lines`.
diff --git a/docs/dev/todo.txt b/docs/dev/todo.txt
index ef532d161..133c58b7e 100644
--- a/docs/dev/todo.txt
+++ b/docs/dev/todo.txt
@@ -181,7 +181,7 @@ General
     for language-dependent features.
 
     Make this the default for output (as opposed to input)?
-    Throw an error with a helpfull message, e.g.
+    Throw an error with a helpful message, e.g.
 
       Default "contents" title for language %s missing, please specify
       an explicit title.
@@ -337,7 +337,7 @@ General
 
 * Add testing for Docutils' front end tools?
 
-* Publisher: "Ordinary setup" shouldn't requre specific ordering; at
+* Publisher: "Ordinary setup" shouldn't require specific ordering; at
   the very least, there ought to be error checking higher up in the
   call chain.  [Aahz]
 
@@ -525,7 +525,7 @@ General
   For example, top/bottom/side navigation bars for web pages.  Generic
   decorations?
 
-  Seems like a bad idea as long as it isn't independent from the ouput
+  Seems like a bad idea as long as it isn't independent from the output
   format (for example, navigation bars are only useful for web pages).
 
 * docutils_update: Check for a ``Makefile`` in a directory, and run
@@ -767,7 +767,7 @@ Miscellaneous ideas:
 
 * Should standalone strings also become (module/class) docstrings?
   Under what conditions?  We want to prevent arbitrary strings from
-  becomming docstrings of prior attribute assignments etc.  Assume
+  becoming docstrings of prior attribute assignments etc.  Assume
   that there must be no blank lines between attributes and attribute
   docstrings?  (Use lineno of NEWLINE token.)
 
@@ -1133,7 +1133,7 @@ Misc
 
     Currently, `document.reporter` uses a state machine instance to
     determine the "source" and "line" info from
-    `statemachine.input_lines` if not given explicitely. Except for
+    `statemachine.input_lines` if not given explicitly. Except for
     special cases, the "line" argument is not needed because,
     `document.statemachine` keeps record of the current line number.
 
@@ -1145,7 +1145,7 @@ Misc
     too?  Add a set_info method?  To what?)
 
     The "source" (and line number in the source) can either be added
-    explicitely to the elements or determined from the “raw” line
+    explicitly to the elements or determined from the “raw” line
     number by `document.statemachine.get_source_and_line`.
 
   - Some line numbers in elements are not being set properly
@@ -1382,7 +1382,7 @@ Use a directive option to specify an alternative input format, e.g. (but not
 limited to):
 
 MathML_
-  Not for hand-written code but maybe usefull when pasted in (or included
+  Not for hand-written code but maybe useful when pasted in (or included
   from a file)
 
   For an overview of MathML implementations and tests, see, e.g.,
@@ -1791,7 +1791,7 @@ when used in a document.
 
     My first idea would be to add a set of conditional directives.
     Let's call them "writer-is" and "writer-is-not" for discussion
-    purposes (don't worry about implemention details).  We might
+    purposes (don't worry about implementation details).  We might
     have::
 
          .. writer-is:: text-only