documentation update

guilhemmarchand · Apr 7, 2017 · 71c19fc · 71c19fc
1 parent ff711a1
commit 71c19fc
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/docs/download.rst b/docs/download.rst
@@ -12,7 +12,7 @@ TA-nmon
 
 The official release of the TA-nmon can be downloaded from Splunk Base: https://splunkbase.splunk.com/app/3248
 
-Note: The TA-nmon is NOT Splunk certified for some reasons, specially because it contains various binaries, and this would restrict the TA-nmon functionaries.
+Note: The TA-nmon is NOT Splunk certified for some reasons, specially because it contains various binaries, and this would restrict the TA-nmon features.
 
 Github releases
 ===============

diff --git a/docs/installation_splunkcloud.rst b/docs/installation_splunkcloud.rst
@@ -4,7 +4,7 @@ Deploy to Splunk Cloud
 
 **Deploying Nmon Performance Monitor in Splunk Cloud**
 
-Nmon Performance Monitor is entirely compatible with a Splunk Cloud deployment, offering 100% of app functionality to monitor your own servers.
+Nmon Performance Monitor is entirely compatible with a Splunk Cloud deployment, offering 100% of application features to monitor your own servers.
 
 However, please note that Splunk does not allow any application to monitor Cloud instances performances, such as the deployment matrix differs from on premise installations.
 

diff --git a/docs/installation_windows.rst b/docs/installation_windows.rst
@@ -16,7 +16,7 @@ Running on Windows
 
 * In distributed / standalone instance to manage cold nmon files generated out of Splunk
 
-100% of App's functionality are available on Windows hosts running Nmon Performance app.
+100% of application features are available on Windows hosts running Nmon Performance.
 
 **1. Install the Python interpreter for Windows (version 2.x)**
 

diff --git a/docs/topologies.rst b/docs/topologies.rst
@@ -42,7 +42,7 @@ This is an example of deployment for standard scenario with a single Splunk forw
 
 **Additionally and since the version 1.6.14, it is possible to use Syslog as the transport layer associated with a third party package called "nmon-logger"**
 
-This deployment topology provides all of application functionality without any deployment of Universal Forwarders on end servers, using rsyslog or syslog-ng.
+This deployment topology provides all the application features without any deployment of Universal Forwarders on end servers, using rsyslog or syslog-ng.
 Such a deployment answers the need for people that cannot or do not want to install any third party agent.
 
 **The nmon-logger package is available for download in GitHub:** https://github.com/guilhemmarchand/nmon-logger

diff --git a/docs/upgrade.rst b/docs/upgrade.rst
@@ -149,7 +149,7 @@ Migrate from version 1.7.x to version 1.9.x
 Migrate from version 1.8.x to version 1.9.x
 """""""""""""""""""""""""""""""""""""""""""
 
-**The release 1.9.x is new main release for Nmon Core application as well for the TA-nmon technical addon**
+**The release 1.9.x is a new main release for the Nmon Core application, and as well for the TA-nmon technical addon**
 
 There are some changes in these releases than can require specific actions:
 
@@ -161,7 +161,7 @@ There are some changes in these releases than can require specific actions:
 
 **If you have previously deployed the PA-nmon in your clustered indexers, follow these simple steps:**
 
-* if you have defined any custom index in the PA-nmon, backup this configuration and backport it to the PA-nmon_light (see above)
+* if you have defined any custom index in the PA-nmon, backup this configuration and move it to the PA-nmon_light (see above)
 * remove the PA-nmon from the "master-apps" of the master node
 * extract the PA-nmon_light archive in the master node "master-apps" directory
 * extract the TA-nmon archive in the master node "master-apps" directory if you want to collect performance statistics from your indexers