[jhbuild] doc: Fix typos

[Anders Jonsson <ajonsson src gnome org>]

commit 114aca967acaff3c4740640353c9ba4a5a84f2e7
Author: Anders Jonsson <anders jonsson norsjovallen se>
Date:   Fri Dec 18 18:41:38 2015 +0100

    doc: Fix typos
    
    https://bugzilla.gnome.org/show_bug.cgi?id=757738

 doc/C/index.docbook |   20 ++++++++++----------
 1 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/doc/C/index.docbook b/doc/C/index.docbook
index 6228fac..8af2ef7 100644
--- a/doc/C/index.docbook
+++ b/doc/C/index.docbook
@@ -462,7 +462,7 @@
       <title>Running the GNOME Desktop Environment</title>
 
       <para>Create a new user account to run the JHBuild GNOME. Running
-        JHBuild GNOME using different user account is recommended to avoid
+        JHBuild GNOME using a different user account is recommended to avoid
         problems caused by user settings stored in the home directory. This
         manual refers to the new account as
         <systemitem class="username">gnomedev</systemitem>.</para>
@@ -874,7 +874,7 @@ jhbuildbot_password = 'password'
               distclean</command> before building modules.</simpara>
 
             <note>
-              <simpara>This option will delete any uncommited changes.
+              <simpara>This option will delete any uncommitted changes.
               </simpara>
             </note>
           </listitem>
@@ -1776,7 +1776,7 @@ Optional packages: (JHBuild will build the missing packages)
               A boolean value (default <literal>True</literal>) which controls if
               <literal>--disable-Werror</literal> will be passed to automake builds.  Many packages use this
               flag as a way to disable fatal compiler warnings.  The value of <literal>True</literal> is
-              selected as a resonable default for those using jhbuild as a means to get an up-to-date 
version of
+              selected as a reasonable default for those using jhbuild as a means to get an up-to-date 
version of
               software packages without being side-tracked by build failures in other people's modules.
               Settings this value to <literal>False</literal> may make sense for those using jhbuild as part 
of
               a continuous integration or testing system.
@@ -1823,7 +1823,7 @@ Optional packages: (JHBuild will build the missing packages)
               <varname>prefix</varname> variable.  Adding directories to
               <varname>extra_prefixes</varname> will cause these prefixes to be
               included as well, at a lower precedence than the JHBuild
-              <varname>prefix</varname>, but at a higher precendence than system
+              <varname>prefix</varname>, but at a higher precedence than system
               directories.  This variable is empty by default except on systems
               that install software in <filename>/usr/local</filename>, in which
               case it contains this directory.
@@ -2539,7 +2539,7 @@ Optional packages: (JHBuild will build the missing packages)
   [ hash="<replaceable>hash</replaceable>" ]/&gt;
 </programlisting>
 
-      <para>All atributes have sensible defaults and depend on the module and
+      <para>All attributes have sensible defaults and depend on the module and
         repository definitions. Common attributes are described here.</para>
 
       <para>The <sgmltag class="attribute">repo</sgmltag> attribute is used to
@@ -2575,15 +2575,15 @@ Optional packages: (JHBuild will build the missing packages)
           <sgmltag class="element">branch</sgmltag> element in the module
           definitions can specify <sgmltag class="attribute">branch</sgmltag>
           and <sgmltag class="attribute">user</sgmltag> attributes. These values
-          will be substitued in the templates. If either of those are defined
+          will be substituted in the templates. If either of those are defined
           <sgmltag class="attribute">branches-template</sgmltag> is used,
           otherwise <sgmltag class="attribute">trunk-template</sgmltag> is used.
-          This way you can ovveride repository to build modules from your
+          This way you can override repository to build modules from your
           personal branch or build many modules from a repository with
           non-standard layout.</para>
 
         <para>An addition <sgmltag class="element">branch</sgmltag> element
-          accepts <sgmltag class="attribute">revspec</sgmltag> attibute to
+          accepts <sgmltag class="attribute">revspec</sgmltag> attribute to
           anchor on a particular revision. Any valid <literal>bzr
           revspec</literal> is accepted, for example <literal>date:yesterday,
           -5, tag:0.1</literal> to get first revision since yesterday, 5 commits
@@ -2743,7 +2743,7 @@ Optional packages: (JHBuild will build the missing packages)
     href="http://svn.gnome.org/svn/"/&gt;
         </programlisting>
 
-<!-- So how do I checkut out branch at a specific revision? -->
+<!-- So how do I checkout a branch at a specific revision? -->
 
         <para>It allows a <sgmltag class="attribute">revision</sgmltag> on the
           <sgmltag class="element">branch</sgmltag> element. This attribute
@@ -3381,7 +3381,7 @@ Optional packages: (JHBuild will build the missing packages)
 <programlisting>
   &lt;tarball id="<replaceable>modulename</replaceable>"
               [ version="<replaceable>version</replaceable>" ]
-              [ checkourdir="<replaceable>checkoutdir</replaceable>" ]
+              [ checkoutdir="<replaceable>checkoutdir</replaceable>" ]
               [ autogenargs="<replaceable>autogenargs</replaceable>" ]
               [ makeargs="<replaceable>makeargs</replaceable>" ]
               [ autogen-sh="<replaceable>autogen-sh</replaceable>" ]