Typo/spacing fix

As well as "114" both areas.

chapter-npm.asciidoc

@@ -37,17 +37,13 @@ version 1.4 and above.
 [[npm-proxying-registries]]
 === Proxying npm Registries
 
-To reduce duplicate downloads and improve download speeds for your
-developers and CI servers, you should proxy the registry hosted at
--https://registry.npmjs.org[https://registry.npmjs.org]. It is
-accessed directly by npm out-of-the-box. You can also proxy any other
-registries you require.
+To reduce duplicate downloads and improve download speeds for your developers and CI servers, you should proxy the
+registry hosted at https://registry.npmjs.org[https://registry.npmjs.org]. It is accessed directly by npm
+out-of-the-box. You can also proxy any other registries you require.
 
-To proxy an external npm registry, you simply create a new 'Proxy
-Repository' as documented in <<confignx-sect-manage-repo>>. The
-'Provider' has to be set to +NPM+. The 'Remote Storage Location' has
-to be set to the URL of the remote repository you want to proxy. The official
-URL for the main npm registry is 
+To proxy an external npm registry, you simply create a new 'Proxy Repository' as documented in 
+<<confignx-sect-manage-repo>>. The 'Provider' has to be set to +NPM+. The 'Remote Storage Location' has to be set
+to the URL of the remote repository you want to proxy. The official URL for the main npm registry is 
 
 ----
 https://registry.npmjs.org
@@ -67,26 +63,23 @@ is not supported
 === Private npm Registries
 
 A private npm registry can be used to upload your own packages as well as third-party packages. You can create a
-private npm registry by setting up a hosted repository with the npm format in the repository manager.It is good
+private npm registry by setting up a hosted repository with the npm format in the repository manager. It is good
 practice to create two separate hosted repositories for these purposes.
 
-To create a hosted repository with npm format, simply create a new 'Hosted
-Repository' and set the 'Provider' to +npm+ as documented in
-<<confignx-sect-manage-repo>>. A sample configuration for an internal
-releases npm hosted repository is displayed in <<fig-npm-hosted>>.
+To create a hosted repository with npm format, simply create a new 'Hosted Repository' and set the 'Provider' to
++npm+ as documented in <<confignx-sect-manage-repo>>. A sample configuration for an internal releases npm hosted 
+repository is displayed in <<fig-npm-hosted>>.
 
 [[fig-npm-hosted]]
 .Example Configuration for a Private npm Registry
 image::figs/web/npm-hosted.png[scale=50]
 
-The npm registry information is immediately updated as packages are
-deployed or deleted from the repository.
+The npm registry information is immediately updated as packages are deployed or deleted from the repository.
 
 WARNING: Browsing the registry storage or searching for packages is not supported.
 
-The scheduled tasks to recreate the npm metadata database based on the
-components in a hosted repository and to back up the database are
-documented in <<scheduled-tasks>>.
+The scheduled tasks to recreate the npm metadata database based on the components in a hosted repository and to 
+back up the database are documented in <<scheduled-tasks>>.
 
 [[npm-grouping-registries]]
 === Grouping npm Registries