Merge pull request #147 from lsolano/fixes/remove_duplicated_words

Removes duplicated words from asciidoc files ( fixes issue #146 )

chapter-concepts.asciidoc

@@ -371,7 +371,7 @@ complexity overheads
 [[supply-chain]]
 === Software Supply Chain Automation
 
-Once you adopting a repository manager as a central point of of
+Once you adopting a repository manager as a central point of
 storage and exchange for all component usage, the next step is expand
 its use in your efforts to automate and manage the software supply
 chain throughout your software development lifecycle.

chapter-configuration.asciidoc

@@ -585,7 +585,7 @@ documented in <<manual-routing>>.
 Automatic routing is handled on a per repository
 basis. You can access the configuration and further details in the
 Routing tab after selecting a repository in the list accessible via the
-'Repositories' item in the the 'Views/Repositories' left-hand menu.
+'Repositories' item in the 'Views/Repositories' left-hand menu.
 
 The routing information consists of the top two levels of the directory structure of the repository and is stored
 in a prefixes.txt file. It allows the repository manager to automatically route only component requests with the

chapter-eval.asciidoc

@@ -173,7 +173,7 @@ NOTE: This guide and the examples reference the  URL
 http://localhost:8081/nexus. If you have chosen to use a different
 port during the installation of the trial simply change the URLs.
 
-Below are are several directories to know:
+Below are several directories to know:
 
 Installation Directory: This is where the application files are installed on your system. We refer to this as
 *<nexus_install>*.
@@ -825,7 +825,7 @@ and Ant are part of the eval guide resources.
 
 . Inspect the preconfigured 'Example Release Profile' staging profile
 by selecting it from the list available after selecting 'Staging
-Profiles' in the the 'Build Promotion' menu in the left-hand
+Profiles' in the 'Build Promotion' menu in the left-hand
 navigation.
 
 . Notice that the version of the simple-project in the pom.xml ends
@@ -1036,7 +1036,7 @@ username and password again, and inspect the tokens in the pop-up dialog.
 .Conclusion
 ****
 The distribution of +settings.xml+ is a crucial part of the rollout of repository manager usage. With the help of
-the the Nexus M2Settings Maven Plugin and the server side settings template, it is possible to automate initial
+the Nexus M2Settings Maven Plugin and the server side settings template, it is possible to automate initial
 distribution as well as updates to the used +settings.xml+ files. The User Token feature allows you to avoid
 having SSO credentials exposed in your file system at all.
 ****

chapter-installation.asciidoc

@@ -29,7 +29,7 @@ differences are explored in <<intro>>.
 ==== Downloading {oss}
 
 To download the latest {oss} distribution, go to http://www.sonatype.org/nexus/go[http://www.sonatype.org/nexus/go]
-and choose 'Nexus (TGZ)' or 'Nexus (ZIP)' shown in <<fig-installing-open-source-dl>>. This will download a a Gzip TAR (TGZ)
+and choose 'Nexus (TGZ)' or 'Nexus (ZIP)' shown in <<fig-installing-open-source-dl>>. This will download a Gzip TAR (TGZ)
 or a ZIP with identical contents. Your download will be file named +nexus-{version-exact}-bundle.zip+ or
 +nexus-{version-exact}-bundle.tar.gz+.
 

chapter-maven-settings.asciidoc

@@ -49,7 +49,7 @@ file from this template.
 
 Server side interpolation takes effect even when the download of the
 settings template is done with tools like curl. These properties can 
-be referenced in the settings file using the the syntax +$\{property\}+:
+be referenced in the settings file using the syntax +$\{property\}+:
 
 ----
 <settings>
@@ -103,7 +103,7 @@ username and password:
 </server>
 ----
 
-You can also use the the usertoken equivalent: 
+You can also use the usertoken equivalent: 
 
 ----
 <server>
@@ -219,7 +219,7 @@ nexusUrl:: Points to the repository manager installation's base URL. If you have
 on your local machine, this would be http://localhost:8081/nexus/. Access via HTTP only works with the +secure+
 configuration parameter set to +false+.
 
-username:: The username to use for authenticating to the repository manager. Default value is the the Java System
+username:: The username to use for authenticating to the repository manager. Default value is the Java System
 property +user.name+.
 
 password:: The password to use for authenticating to the repository manager.

chapter-maven.asciidoc

@@ -310,7 +310,7 @@ These minimal settings allow Gradle to download the declared
 dependencies.
 
 The above setup is specific to each project. Alternatively an +init.gradle+ file placed e.g., in +~/.gradle+ can
-establish the repository as the the source for dependencies in all projects. A simple implementation could look
+establish the repository as the source for dependencies in all projects. A simple implementation could look
 like
 
 ----

chapter-procurement.asciidoc

@@ -119,7 +119,7 @@ additional components that have been authored internally in the organization and
 manager as well.
 
 In order to use a combination of such components together with the
-procured component, you should set up a a repository group that
+procured component, you should set up a repository group that
 contains all repositories with preapproved components as well as the
 procurement repository. For example, the release and snapshot repositories
 could be added to the group, based on the assumption that any

chapter-rubygems.asciidoc

@@ -82,7 +82,7 @@ This main configuration for proxying RubyGems is visible in
 image::figs/web/rubygems-proxy.png[scale=50]
 
 If you are using {pro} and are proxying a repository via HTTPS, you can get the certificate added to the
-repository manager truststore to simplify management using the the SSL tab of the repository configuration.
+repository manager truststore to simplify management using the SSL tab of the repository configuration.
 
 <<scheduled-tasks, Scheduled tasks>> can be used to purge broken
 metadata of a proxy gem repository as well as to synchronize the

chapter-staging.asciidoc

@@ -291,7 +291,7 @@ Template:: The template for repositories generated by this
 build promotion profile. The default value for this field is +Maven2
 (group)+.
 
-Target Groups:: The 'Target Groups' field is is the most important 
+Target Groups:: The 'Target Groups' field is the most important 
 configuration field for a build promotion profile, as it controls the 
 group through which promoted components are made available. Components 
 can be made available through one or more groups.
@@ -500,7 +500,7 @@ repository manager.
 If more control is desired over when the plugins deploy goal is
 activated or if Maven 2 is used, you have to explicitly deactivate the
 Maven Deploy plugin and replace the Maven Deploy plugin invocation
-with the Nexus Staging Maven plugin like visible in
+with the Nexus Staging Maven plugin like visible
 in <<fig-staging-maven2and3>>.
 
 [[fig-staging-maven2and3]]