[PATCH rtems-docs] user/rsb: Fix typos (#3922)

Chris Johns chrisj at rtems.org
Thu Apr 2 09:27:03 UTC 2020


Pushed. Thanks.

Chris

On 2020-04-02 19:18, Mritunjay wrote:
> Closes #3922
> ---
>   user/rsb/configuration.rst        | 14 +++++++-------
>   user/rsb/cross-canadian-cross.rst |  2 +-
>   user/rsb/project-sets.rst         |  2 +-
>   user/rsb/third-party-packages.rst |  2 +-
>   4 files changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst
> index fc387a1..8c8c87f 100644
> --- a/user/rsb/configuration.rst
> +++ b/user/rsb/configuration.rst
> @@ -181,7 +181,7 @@ errors that can arise.
>   
>   The protocol option lets you set a specific protocol. The ``git://`` prefix
>   used by the RSB to select a git repository can be removed using *none* or
> -replaced with one of the standard git protcols.
> +replaced with one of the standard git protocols.
>   
>   CVS
>   ~~~
> @@ -315,7 +315,7 @@ Maps are declared anywhere in the map using the map directive:
>   
>     1. The map is set to ``my-special-map``.
>   
> -Any macro defintions following a map declaration are placed in that map and the
> +Any macro definitions following a map declaration are placed in that map and the
>   default map is ``global`` when loading a file. Maps are selected in
>   configuration files by using the ``%select`` directive:
>   
> @@ -328,7 +328,7 @@ if present return that value else the ``global`` map is used. Any new macros or
>   changes update only the ``global`` map. This may change in future releases so
>   please make sure you use the ``override`` attribute.
>   
> -The macro files specificed on the command line are looked for in the
> +The macro files specified on the command line are looked for in the
>   ``_configdir`` paths. See <<X1,``_configdir``>> variable for details. Included
>   files need to add the ``%{_configdir}`` macro to the start of the file.
>   
> @@ -636,8 +636,8 @@ source packages based on the outer configuration options:
>   The remainder of the script is broken in to the various phases of a build. They
>   are:
>   
> -. Preperation
> -. Bulding
> +. Preparation
> +. Building
>   . Installing, and
>   . Cleaning
>   
> @@ -799,8 +799,8 @@ 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 priviledges.
> +because I never run the RSB with root privileges so a build set or bset tar
> +file is created. This can then be installed using root privileges.
>   
>   The command also supplies the ``--trace`` option. The output in the log file
>   will contain all the macros.
> diff --git a/user/rsb/cross-canadian-cross.rst b/user/rsb/cross-canadian-cross.rst
> index 8eceed3..7ccd6c3 100644
> --- a/user/rsb/cross-canadian-cross.rst
> +++ b/user/rsb/cross-canadian-cross.rst
> @@ -37,7 +37,7 @@ To build the Curl package for RTEMS you enter the RSB command:
>   
>     2. The ``--host`` command is the RTEMS architecture and version.
>   
> -  3. The BSP is built and installed in the prefix. The arhcitecture must match
> +  3. The BSP is built and installed in the prefix. The architecture must match
>        the ``--host`` architecture.
>   
>   .. note: Installing Into Different Directories
> diff --git a/user/rsb/project-sets.rst b/user/rsb/project-sets.rst
> index 6eb8729..54a3f8e 100644
> --- a/user/rsb/project-sets.rst
> +++ b/user/rsb/project-sets.rst
> @@ -154,7 +154,7 @@ Patches are added to a component's name and in the ``%prep:`` section the
>   patches can be set up, meaning they are applied to source. The patches are
>   applied in the order they are added. If there is a dependency make sure you
>   order the patches correctly when you add them. You can add any number of
> -patches and the RSB will handle them efficently.
> +patches and the RSB will handle them efficiently.
>   
>   Patches can have options. These are added before the patch URL. If no options
>   are provided the patch's setup default options are used.
> diff --git a/user/rsb/third-party-packages.rst b/user/rsb/third-party-packages.rst
> index 0d9fa81..8610650 100644
> --- a/user/rsb/third-party-packages.rst
> +++ b/user/rsb/third-party-packages.rst
> @@ -133,7 +133,7 @@ A custom RTEMS patch to an executate's source code can turn it into a function
>   that can be called by the RTEMS shell. Users can call the function in their
>   executables simulating the running of the package's command. If the package
>   does not export the code in a suitable manner please contact the project's
> -commuinity and see if you can work with them to provide a way for the code to
> +community and see if you can work with them to provide a way for the code to
>   be exported. This may be difficult because exporting internal headers and
>   functions opens the project up to API compatibility issues they did not have
>   before. In the simplest case attempting to get the code into a static library
> 


More information about the devel mailing list