Index: rsb/configuration.rst
===================================================================
--- rsb/configuration.rst	(revision 9742e45add23c7bb7f0f42a47421dc532fac9e45)
+++ rsb/configuration.rst	(revision c41810b079d761dd4bb759792192f3d88efa039f)
@@ -116,5 +116,5 @@
   XY
 
-The output of the decompression tool is feed to the standard ``tar`` utility if
+The output of the decompression tool is fed to the standard ``tar`` utility if
 not a ZIP file and unpacked into the build directory. ZIP files are unpacked by
 the decompression tool and all other files must be in the tar file format.
@@ -122,10 +122,10 @@
 The ``%source`` directive typically supports a single source file tar or zip
 file. The ``set`` command is used to set the URL for a specific source
-group. The first set command encoutner is registered and any further set
+group. The first set command encountered is registered and any further set
 commands are ignored. This allows you to define a base standard source location
 and override it in build and architecture specific files. You can also add
 extra source files to a group. This is typically done when a collection of
 source is broken down in a number of smaller files and you require the full
-package. The source's ``setup`` command must reide in the ``%prep:`` section
+package. The source's ``setup`` command must reside in the ``%prep:`` section
 and it unpacks the source code ready to be built.
 
@@ -585,5 +585,5 @@
 The next section defines the source and any patches. In this case there is a
 single source package and it can be downloaded using the HTTP protocol. The RSB
-knows this is GZip'ped tar file. If more than one package package is needed add
+knows this is GZip'ped tar file. If more than one package is needed, add
 them increasing the index. The ``gcc-4.8-1.cfg`` configuration contains
 examples of more than one source package as well as conditionally including
@@ -643,5 +643,5 @@
 running ``make``. Note the use of the RSB macros for commands. In the case of
 ``%{__make}`` it maps to the correct make for your host. In the case of BSD
-systems we need to use the GNU make and not the GNU make.
+systems we need to use the BSD make and not the GNU make.
 
 If your package requires a configuration stage you need to run this before the
@@ -750,8 +750,8 @@
 packages. In this example I cannot let the source builder perform the install
 because I never run the RSB with root priviledges so a build set or bset tar
-file is created. This can then be installed using root privildges.
+file is created. This can then be installed using root priviledges.
 
 The command also supplies the ``--trace`` option. The output in the log file
-will contian all the macros.
+will contain all the macros.
 
 Debugging
@@ -769,5 +769,5 @@
 technique such as ``set +x`` to output the commands or ``echo``
 statements. Debugging package related issues may require you start a build with
-teh RSB and supply ``--no-clean`` option and then locate the build directories
+the RSB and supply ``--no-clean`` option and then locate the build directories
 and change directory into them and manually run commands until to figure what
 the package requires.
@@ -824,5 +824,5 @@
 
 ``%patch``:
-  Define a patch. This macro has a is number appended.
+  Define a patch. This macro has a number appended.
 
 ``%hash``:
@@ -1019,5 +1019,5 @@
 the build will succeed.
 
-The following is an example take from the GutHub STLink project. The STLink is
+The following is an example take from the GitHub STLink project. The STLink is
 a JTAG debugging device for the ST ARM family of processors::
 
@@ -1079,5 +1079,5 @@
 The ``%install`` macro starts a block that continues until the next block
 macro. The install block is a series of shell commands that execute to install
-the package. You can assume the package has build correctly when this block
+the package. You can assume the package has built correctly when this block
 starts executing.
 
@@ -1103,5 +1103,5 @@
   1. Setup the PATH environment variable. This is not always needed.
 
-  2. Clean any installed files. This make sure the install is just what the
+  2. Clean any installed files. This makes sure the install is just what the
      package installs and not any left over files from a broken build or
      install.
@@ -1161,6 +1161,6 @@
 ~~~~~~~~
 
-The ``%release`` is packaging number that allows revisions of a package to
-happen where none package versions change. This value typically increases when
+The ``%release`` is a packaging number that allows revisions of a package to
+happen where no package versions change. This value typically increases when
 the configuration building the package changes::
 
@@ -1197,12 +1197,12 @@
 requires one or more dependent packages. These are typically the packages
 source code plus dependent libraries or modules. You can create any number of
-these source groups and set each of them up with a separe source group for each
-needed library or module. Each source group normally has a single tar, zip or
-repository and the ``set`` defines this. Some projects split the source code
+these source groups and set each of them up with a separate source group for
+each needed library or module. Each source group normally has a single tar, zip
+or repository and the ``set`` defines this. Some projects split the source code
 into separate tar or zip files and you install them by using the ``add``
 command.
 
 The first instance of a ``set`` command creates the source group and sets the
-source files to be set up. Subsequence ``set`` commands for the same source
+source files to be set up. Subsequent ``set`` commands for the same source
 group are ignored. this lets you define the standard source files and override
 them for specific releases or snapshots. To set a source file group:
@@ -1259,6 +1259,6 @@
 
 The ``%patch`` macro has the same 3 command as the ``%source`` command however
-the ``set`` commands is not really that useful with the with command. You add
-patches with the ``add`` command and ``setup`` applies the patches. Patch
+the ``set`` commands is not really that useful with the ``%patch`` command. You
+add patches with the ``add`` command and ``setup`` applies the patches. Patch
 options can be added to each patch by placing them before the patch URL. If no
 patch option is provided the default options passed to the ``setup`` command
@@ -1269,5 +1269,5 @@
 control applying a group of patches to a specific source tree.
 
-The ``__patchdir`` path is search.
+The ``__patchdir`` path is searched.
 
 To add a patch::
@@ -1296,9 +1296,9 @@
 The ``%hash`` macro requires 3 arguments and defines a checksum for a specific
 file. The checksum is not applied until the file is checked before downloading
-and once downloaded. A patch or source file that does not has a hash defined
+and once downloaded. A patch or source file that does not have a hash defined
 generates a warning.
 
-A file to be checksum must be unqiue in the any of the source and patch
-directories. The basename of the file is used as the key for the hash.
+A file to be checksummed must be unique in the source and patch directories.
+The basename of the file is used as the key for the hash.
 
 The hash algorthim can be ``md5``, ``sha1``, ``sha224``, ``sha256``,
@@ -1321,5 +1321,5 @@
 create confusion. This does mean files with hashes must be unique.
 
-Downloading of repositories such as git and cvs cannot be checksumed. It is
+Downloading off repositories such as git and cvs cannot be checksummed. It is
 assumed those protocols and tools manage the state of the files.
 
@@ -1347,8 +1347,8 @@
 The ``%select`` macro selects the map specified. If there is no map no error or
 warning is generated. Macro maps provide a simple way for a user to override
-the settings is a configuration file without having to edit it. The changes are
-recorded in the build report so can be traced.
-
-Configuration use different maps so macro overrides can target a specific
+the settings in a configuration file without having to edit it. The changes are
+recorded in the build report so they can be traced.
+
+Configurations use different maps so macro overrides can target a specific
 package.
 
