metricbeat/filebeat: fix typos in iis, oracle, etcd, sql, decode_cef, and netflow modules

docs/reference/filebeat/exported-fields-cef.md

@@ -221,7 +221,7 @@ Collection of key-value pairs carried in the CEF extension field.
 
 
 **`cef.extensions.destinationMacAddress`**
-:   Six colon-seperated hexadecimal numbers.
+:   Six colon-separated hexadecimal numbers.
 
     type: keyword
 
@@ -689,7 +689,7 @@ Collection of key-value pairs carried in the CEF extension field.
 
 
 **`cef.extensions.deviceZoneURI`**
-:   Thee URI for the Zone that the device asset has been assigned to in ArcSight.
+:   The URI for the Zone that the device asset has been assigned to in ArcSight.
 
     type: keyword
 

docs/reference/metricbeat/exported-fields-etcd.md

@@ -83,7 +83,7 @@ Server metrics from the Etcd V3 /metrics endpoint
 
 
 **`etcd.server.proposals_committed.count`**
-:   Number of consensus proposals commited
+:   Number of consensus proposals committed
 
     type: long
 

docs/reference/metricbeat/exported-fields-oracle.md

@@ -128,7 +128,7 @@ Opened cursors statistic
 
 ## parse [_parse]
 
-Parses statistic information that occured in the current session
+Parses statistic information that occurred in the current session
 
 **`oracle.performance.cursors.parse.real`**
 :   Real number of parses that occurred: session cursor cache hits - parse count (total)

docs/reference/metricbeat/metricbeat-metricset-iis-application_pool.md

@@ -16,7 +16,7 @@ This metricset allows users to retrieve relevant metrics for the application poo
 
 Metric values are divided in several groups:
 
-The `process` object contains System/Process counters like the the overall server and CPU usage for the IIS Worker Process and memory (currently used and available memory for the IIS Worker Process).
+The `process` object contains System/Process counters like the overall server and CPU usage for the IIS Worker Process and memory (currently used and available memory for the IIS Worker Process).
 
 The `net_clr` object which returns ASP.NET error rate counter values. Users can specify the application pools they would like to monitor using the configuration option `application_pool.name`, else, all application pools are considered.
 

docs/reference/metricbeat/metricbeat-metricset-iis-webserver.md

@@ -16,7 +16,7 @@ This metricset allows users to retrieve relevant metrics from IIS.
 
 Metric values are divided in several groups:
 
-The `process` object contains System/Process counters like the the overall server and CPU usage for the IIS Worker Processes and memory (currently used and available memory for the IIS Worker Processes).
+The `process` object contains System/Process counters like the overall server and CPU usage for the IIS Worker Processes and memory (currently used and available memory for the IIS Worker Processes).
 
 The `network` object contains the IIS Performance counters like: Web Service: Bytes Received/Sec (helpful to track to identify potential spikes in traffic), Web Service: Bytes Sent/Sec (helpful to track to identify potential spikes in traffic), Web Service: Current Connections (through experience with their apps app, users can identify what is a normal value for this) and others.
 

docs/reference/metricbeat/metricbeat-module-http.md

@@ -54,7 +54,7 @@ metricbeat.modules:
   #paths:
   #  - path: "/foo"
   #    namespace: "foo"
-  #    fields: # added to the the response in root. overwrites existing fields
+  #    fields: # added to the response in root. overwrites existing fields
   #      key: "value"
 ```
 

docs/reference/metricbeat/metricbeat-module-iis.md

@@ -26,9 +26,9 @@
 
 The `iis` module will periodically retrieve IIS related metrics using performance counters such as:
 
-* System/Process counters like the the overall server and CPU usage for the IIS Worker Process and memory (currently used and available memory for the IIS Worker Process).
+* System/Process counters like the overall server and CPU usage for the IIS Worker Process and memory (currently used and available memory for the IIS Worker Process).
 * IIS performance counters like Web Service: Bytes Received/Sec, Web Service: Bytes Sent/Sec, etc, which are helpful to track to identify potential spikes in traffic.
 * Web Service Cache counters in order to monitor user mode cache and output cache.
 
 The `iis` module metricsets are `webserver`, `website` and `application_pool`.
 

docs/reference/metricbeat/metricbeat-module-sql.md

@@ -32,7 +32,7 @@ After enabling the module, open `modules.d/sql.yml` and set the required fields:
 :   The driver can be any driver that has a {{metricbeat}} module, such as `mssql` or `postgres`.
 
 `fetch_from_all_databases`
-:   Expects either `true` or `false` and it is by default set to `false`. Marking as `true` will enable execution `sql_queries` or `sql_query` for all databases in a server. Currently only `mssql` driver supports this feature. For other drivers, if enabled, "fetch from all databases feature is not supported for driver: <driver_name>" error would be logged.
+:   Expects either `true` or `false` and it is by default set to `false`. Setting this to true enables execution of `sql_queries` or `sql_query` for all databases on a server. Currently only `mssql` driver supports this feature. For other drivers, if enabled, "fetch from all databases feature is not supported for driver: <driver_name>" error would be logged.
 
 `raw_data.enabled`
 :   Expects either `true` or `false` and it is by default set to `false`. Marking as `true` will generate event results in a new field format.

docs/reference/metricbeat/metricbeat-reference-yml.md

@@ -432,7 +432,7 @@ metricbeat.modules:
   #paths:
   #  - path: "/foo"
   #    namespace: "foo"
-  #    fields: # added to the the response in root. overwrites existing fields
+  #    fields: # added to the response in root. overwrites existing fields
   #      key: "value"
 
 #------------------------------- Jolokia Module -------------------------------

docs/reference/metricbeat/monitoring-metricbeat-collection.md

@@ -71,7 +71,7 @@ To collect and ship monitoring data:
 
 1. The next step depends on how you want to run {{metricbeat}}:
 
-    * If you’re running as a service and want to run a separate monitoring instance, take the the steps required for your environment to run two instances of {{metricbeat}} as a service. The steps for doing this vary by platform and are beyond the scope of this documentation.
+    * If you’re running as a service and want to run a separate monitoring instance, take the steps required for your environment to run two instances of {{metricbeat}} as a service. The steps for doing this vary by platform and are beyond the scope of this documentation.
     * If you’re running the binary directly in the foreground and want to run a separate monitoring instance, install {{metricbeat}} to a different path. If necessary, set `path.config`, `path.data`, and `path.log` to point to the correct directories. See [Directory layout](/reference/metricbeat/directory-layout.md) for the default locations.
 
 2. Enable the `beat-xpack` module in {{metricbeat}}.<br>

metricbeat/metricbeat.reference.yml

@@ -412,7 +412,7 @@ metricbeat.modules:
   #paths:
   #  - path: "/foo"
   #    namespace: "foo"
-  #    fields: # added to the the response in root. overwrites existing fields
+  #    fields: # added to the response in root. overwrites existing fields
   #      key: "value"
 
 #------------------------------- Jolokia Module -------------------------------

metricbeat/module/etcd/metrics/_meta/fields.yml

@@ -17,7 +17,7 @@
     - name: proposals_committed.count
       type: long
       description: >
-        Number of consensus proposals commited
+        Number of consensus proposals committed
 
     - name: proposals_pending.count
       type: long

metricbeat/module/http/_meta/config.yml

@@ -23,5 +23,5 @@
   #paths:
   #  - path: "/foo"
   #    namespace: "foo"
-  #    fields: # added to the the response in root. overwrites existing fields
+  #    fields: # added to the response in root. overwrites existing fields
   #      key: "value"

metricbeat/modules.d/http.yml.disabled

@@ -26,5 +26,5 @@
   #paths:
   #  - path: "/foo"
   #    namespace: "foo"
-  #    fields: # added to the the response in root. overwrites existing fields
+  #    fields: # added to the response in root. overwrites existing fields
   #      key: "value"

x-pack/filebeat/input/netflow/decoder/fields/ipfix-information-elements.csv

@@ -3617,7 +3617,7 @@ of this field is limited to 10 characters, UTF-8 encoded.",,,,[Felix_Erlacher],0
     [RFC7231]. Encoded in UTF-8.",,,[RFC7231],[Andrew_Feren],0,2017-04-19
 469,httpContentType,string,default,current,"The HTTP Content-Type header field as defined in section 3.1.1.5 of 
     [RFC7231]. Encoded in UTF-8.",,,[RFC7231],[Andrew_Feren],0,2017-04-19
-470,httpReasonPhrase,string,default,current,"The HTTP reason phrase as defined in section 6.1 of of 
+470,httpReasonPhrase,string,default,current,"The HTTP reason phrase as defined in section 6.1 of
     [RFC7231].",,,[RFC7231],[Felix_Erlacher],0,2017-06-19
 471,maxSessionEntries,unsigned32,identifier,current,"This element represents the maximum session entries that
     can be created by the NAT device.",,,"See [RFC3022] for the definition of NAT.  

x-pack/filebeat/processors/decode_cef/_meta/fields.yml

@@ -159,7 +159,7 @@
 
             - name: destinationMacAddress
               type: keyword
-              description: Six colon-seperated hexadecimal numbers.
+              description: Six colon-separated hexadecimal numbers.
 
             - name: destinationNtDomain
               type: keyword
@@ -471,7 +471,7 @@
 
             - name: deviceZoneURI
               type: keyword
-              description: Thee URI for the Zone that the device asset has been assigned to in ArcSight.
+              description: The URI for the Zone that the device asset has been assigned to in ArcSight.
 
             - name: endTime
               type: date