---
rsb/configuration.rst | 56 +--
1 file changed, 28 insertions(+), 28 deletions(-)
diff --git a/rsb/configuration.rst b/rsb/configuration.rst
index 62fc073..b2745a5 100644
--- a/rsb/configuration.rst
+++ b/rsb/configuration.rst
@@ -115,18 +115,18 @@ supported compression formats are:
``xy``:
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.
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.
If the source URL references the GitHub API server https://api.github.com/ a
@@ -584,7 +584,7 @@ information is kept updated and accurate::
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
source packages based on the outer configuration options::
@@ -642,7 +642,7 @@ control. Newlib is taken directly from its CVS repository.
Next is the building phase and for the DTC example this is simply a matter of
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
make stage. Again the GCC common configuration file provides a detailed
example::
@@ -749,10 +749,10 @@ To build this you can use something similar to::
The build is for a FreeBSD host and the prefix is for user installed
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
~
@@ -768,7 +768,7 @@ phases. These are usually a mix of shell script bugs or
package set up or
configuration bugs. Here you can use any normal shell script type debug
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.
@@ -823,7 +823,7 @@ The script language is implemented in terms of macros. The
built-in list is:
Define a source code package. This macro has a number appended.
``%patch``:
- Define a patch. This macro has a is number appended.
+ Define a patch. This macro has a number appended.
``%hash``:
Define a checksum for a source or patch file.
@@ -1018,7 +1018,7 @@ macro. The build block is a series of shell commands that
execute to build the
package. It assumes all source code has been unpacked, patch and adjusted so
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::
%build
@@ -1078,7 +1078,7 @@ a JTAG debugging device for the ST ARM family of
processors::
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
