<div dir="ltr">Hi Gedare,<div><br></div><div>Apologies as I missed that rsb is moved to user/rsb in the master. After going</div><div>through it, I have found that files:</div><div>rsb/hosts.rst <br></div><div>rsb/quick-start.rst <br></div><div>are no longer there in the master branch. However, most of the typos are still there in other remaining files. </div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 31, 2020 at 9:40 PM Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Mritunjay,<br>
<br>
Are these all fixed already in master branch? these docs moved to user/rsb/*<br>
<br>
On Tue, Mar 31, 2020 at 4:22 AM Mritunjay <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
><br>
> ---<br>
><br>
> This patch fixes typos encountered while going through the documentation<br>
> of rtems-docs-4.11/rsb.<br>
><br>
> rsb/configuration.rst | 24 ++++++++++++------------<br>
> rsb/cross-canadian-cross.rst | 2 +-<br>
> rsb/hosts.rst | 4 ++--<br>
> rsb/project-sets.rst | 4 ++--<br>
> rsb/quick-start.rst | 6 +++---<br>
> rsb/third-party-packages.rst | 4 ++--<br>
> 6 files changed, 22 insertions(+), 22 deletions(-)<br>
><br>
> diff --git a/rsb/configuration.rst b/rsb/configuration.rst<br>
> index 62fc073..bf3dfaa 100644<br>
> --- a/rsb/configuration.rst<br>
> +++ b/rsb/configuration.rst<br>
> @@ -121,12 +121,12 @@ the decompression tool and all other files must be in the tar file format.<br>
><br>
> The ``%source`` directive typically supports a single source file tar or zip<br>
> file. The ``set`` command is used to set the URL for a specific source<br>
> -group. The first set command encoutner is registered and any further set<br>
> +group. The first set command encounter is registered and any further set<br>
> commands are ignored. This allows you to define a base standard source location<br>
> and override it in build and architecture specific files. You can also add<br>
> extra source files to a group. This is typically done when a collection of<br>
> source is broken down in a number of smaller files and you require the full<br>
> -package. The source's ``setup`` command must reide in the ``%prep:`` section<br>
> +package. The source's ``setup`` command must reside in the ``%prep:`` section<br>
> and it unpacks the source code ready to be built.<br>
><br>
> If the source URL references the GitHub API server <a href="https://api.github.com/" rel="noreferrer" target="_blank">https://api.github.com/</a> a<br>
> @@ -180,7 +180,7 @@ errors that can arise.<br>
><br>
> The protocol option lets you set a specific protocol. The ``git://`` prefix<br>
> used by the RSB to select a git repository can be removed using *none* or<br>
> -replaced with one of the standard git protcols.<br>
> +replaced with one of the standard git protocols.<br>
><br>
> CVS<br>
> ~~~<br>
> @@ -304,7 +304,7 @@ Maps are declared anywhere in the map using the map directive::<br>
><br>
> 1. The map is set to ``my-special-map``.<br>
><br>
> -Any macro defintions following a map declaration are placed in that map and the<br>
> +Any macro definitions following a map declaration are placed in that map and the<br>
> default map is ``global`` when loading a file. Maps are selected in<br>
> configuration files by using the ``%select`` directive::<br>
><br>
> @@ -315,7 +315,7 @@ if present return that value else the ``global`` map is used. Any new macros or<br>
> changes update only the ``global`` map. This may change in future releases so<br>
> please make sure you use the ``override`` attribute.<br>
><br>
> -The macro files specificed on the command line are looked for in the<br>
> +The macro files specified on the command line are looked for in the<br>
> ``_configdir`` paths. See <<X1,``_configdir``>> variable for details. Included<br>
> files need to add the ``%{_configdir}`` macro to the start of the file.<br>
><br>
> @@ -494,7 +494,7 @@ To create a private configuration change to a suitable directory::<br>
><br>
> and create a ``config`` directory. Here you can add a new configuration or<br>
> build set file. The section 'Adding New Configurations' details how to add a<br>
> -new confguration.<br>
> +new configuration.<br>
><br>
> New Configurations<br>
> ------------------<br>
> @@ -597,8 +597,8 @@ source packages based on the outer configuration options::<br>
> The remainder of the script is broken in to the various phases of a build. They<br>
> are:<br>
><br>
> -. Preperation<br>
> -. Bulding<br>
> +. Preparation<br>
> +. Building<br>
> . Installing, and<br>
> . Cleaning<br>
><br>
> @@ -748,11 +748,11 @@ To build this you can use something similar to::<br>
><br>
> The build is for a FreeBSD host and the prefix is for user installed<br>
> packages. In this example I cannot let the source builder perform the install<br>
> -because I never run the RSB with root priviledges so a build set or bset tar<br>
> -file is created. This can then be installed using root privildges.<br>
> +because I never run the RSB with root privileges so a build set or bset tar<br>
> +file is created. This can then be installed using root privileges.<br>
><br>
> The command also supplies the ``--trace`` option. The output in the log file<br>
> -will contian all the macros.<br>
> +will contain all the macros.<br>
><br>
> Debugging<br>
> ~~~~~~~~~<br>
> @@ -1320,7 +1320,7 @@ Do not include a path with the file name. Only the basename is required. Files<br>
> can be searched for from a number of places and having a path conponent would<br>
> create confusion. This does mean files with hashes must be unique.<br>
><br>
> -Downloading of repositories such as git and cvs cannot be checksumed. It is<br>
> +Downloading of repositories such as git and cvs cannot be checksummed. It is<br>
> assumed those protocols and tools manage the state of the files.<br>
><br>
> %echo<br>
> diff --git a/rsb/cross-canadian-cross.rst b/rsb/cross-canadian-cross.rst<br>
> index d4fce9e..039c7a7 100644<br>
> --- a/rsb/cross-canadian-cross.rst<br>
> +++ b/rsb/cross-canadian-cross.rst<br>
> @@ -36,7 +36,7 @@ To build the NTP package for RTEMS you enter the RSB command::<br>
><br>
> 2. The ``--host`` command is the RTEMS architecture and version.<br>
><br>
> - 3. The BSP is built and installed in the prefix. The arhcitecture must match<br>
> + 3. The BSP is built and installed in the prefix. The architecture must match<br>
> the ``--host`` architecture.<br>
><br>
> .. note: Installing Into Different Directories<br>
> diff --git a/rsb/hosts.rst b/rsb/hosts.rst<br>
> index a4226f3..ebcca23 100644<br>
> --- a/rsb/hosts.rst<br>
> +++ b/rsb/hosts.rst<br>
> @@ -14,7 +14,7 @@ new version of a host is known to work and it not listed please lets us know.<br>
> Linux<br>
> -----<br>
><br>
> -A number of different Linux distrubutions are known to work. The following have<br>
> +A number of different Linux distributions are known to work. The following have<br>
> been tested and report as working.<br>
><br>
> .. _ArchLinux:<br>
> @@ -122,7 +122,7 @@ ports::<br>
> # portinstall --batch devel/mingw32-binutils devel/mingw32-gcc<br>
> # portinstall --batch devel/mingw32-zlib devel/mingw32-pthreads<br>
><br>
> -The +zlip+ and +pthreads+ ports for MinGW32 are used for builiding a Windows<br>
> +The +zlip+ and +pthreads+ ports for MinGW32 are used for building a Windows<br>
> QEMU.<br>
><br>
> If you are on FreeBSD 10.0 and you have pkgng installed you can use 'pkg<br>
> diff --git a/rsb/project-sets.rst b/rsb/project-sets.rst<br>
> index 8abd080..6ca27e7 100644<br>
> --- a/rsb/project-sets.rst<br>
> +++ b/rsb/project-sets.rst<br>
> @@ -159,7 +159,7 @@ tools within that release. If the package is not specific to any release the<br>
> patch can be added closer to the top under the package's name. Patches to fix<br>
> specific tool related issues for a specific architecture should be grouped<br>
> under the specific architecture and only applied when building that<br>
> -architecture avoiding a patch breaking an uneffected architecture.<br>
> +architecture avoiding a patch breaking an unaffected architecture.<br>
><br>
> Patches in the RTEMS Tools repository need to be submitted to the upstream<br>
> project. It should not be a clearing house for patches that will not be<br>
> @@ -169,7 +169,7 @@ Patches are added to a component's name and in the ``%prep:`` section the<br>
> patches can be set up, meaning they are applied to source. The patches<br>
> are applied in the order they are added. If there is a dependency make<br>
> sure you order the patches correctly when you add them. You can add any<br>
> -number of patches and the RSB will handle them efficently.<br>
> +number of patches and the RSB will handle them efficiently.<br>
><br>
> Patches can have options. These are added before the patch URL. If no options<br>
> are provided the patch's setup default options are used.<br>
> diff --git a/rsb/quick-start.rst b/rsb/quick-start.rst<br>
> index f39c0a6..e39a914 100644<br>
> --- a/rsb/quick-start.rst<br>
> +++ b/rsb/quick-start.rst<br>
> @@ -429,7 +429,7 @@ A build set tar file is created by adding ``--bset-tar-file`` option to the<br>
> 3. Creating the build set tar file.<br>
><br>
> You can also suppress installing the files using the ``--no-install``<br>
> -option. This is useful if your prefix is not accessiable, for example when<br>
> +option. This is useful if your prefix is not accessible, for example when<br>
> building Canadian cross compiled tool sets::<br>
><br>
> $ ../source-builder/sb-set-builder --log=l-sparc.txt \<br>
> @@ -462,7 +462,7 @@ building Canadian cross compiled tool sets::<br>
><br>
> .. topic:: Items<br>
><br>
> - 1. The option to supressing installing the packages.<br>
> + 1. The option to suppressing installing the packages.<br>
><br>
> 2. Create the build set tar.<br>
><br>
> @@ -517,7 +517,7 @@ because they are implemented with the configuration scripts. The best way to<br>
> find what is available is to grep the configuration files. for ``with`` and<br>
> ``without``.<br>
><br>
> -Following are currentlt available:<br>
> +Following are currently available:<br>
><br>
> ``--without-rtems``<br>
> Do not build RTEMS when building an RTEMS build set.<br>
> diff --git a/rsb/third-party-packages.rst b/rsb/third-party-packages.rst<br>
> index a43abeb..1ef7c68 100644<br>
> --- a/rsb/third-party-packages.rst<br>
> +++ b/rsb/third-party-packages.rst<br>
> @@ -66,7 +66,7 @@ this may require you asking questions on the package's user or development<br>
> support lists as well as RTEMS's developers list. Your porting effort may end<br>
> up with a patch. RTEMS requires a patch be submitted upstream to the project's<br>
> community as well as RTEMS so it can be added to the RTEMS Tools git<br>
> -repository. A patch in the RTEMS Tools git reposiitory can then be referenced<br>
> +repository. A patch in the RTEMS Tools git repository can then be referenced<br>
> by an RSB configuration file.<br>
><br>
> A package may create executables, for example NTP normally creates executables<br>
> @@ -75,7 +75,7 @@ when testing the package however they are of limited use by RTEMS users because<br>
> they cannot be directly linked into a user application. Users need to link to<br>
> the functions in these executables or even the executable as a function placed<br>
> in libraries. If the package does not export the code in a suitable manner<br>
> -please contact the project's commuinity and see if you can work them to provide<br>
> +please contact the project's community and see if you can work them to provide<br>
> a way for the code to be exported. This may be difficult because exporting<br>
> internal headers and functions opens the project up to API compatibility issues<br>
> they did not have before. In the simplest case attempting to get the code into<br>
> --<br>
> 2.17.1<br>
><br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div>