Fix typos in autodiscover/module docs and field descriptions

docs/reference/filebeat/configuration-autodiscover.md

@@ -226,7 +226,7 @@ The `kubernetes` autodiscover provider has the following configuration settings:
 :   (Optional) Specify at what level autodiscover needs to be done at. `scope` can either take `node` or `cluster` as values. `node` scope allows discovery of resources in the specified node. `cluster` scope allows cluster wide discovery. Only `pod` and `node` resources can be discovered at node scope.
 
 `add_resource_metadata`
-:   (Optional) Specify filters and configration for the extra metadata, that will be added to the event. Configuration parameters:
+:   (Optional) Specify filters and configuration for the extra metadata, that will be added to the event. Configuration parameters:
 
     * `node` or `namespace`: Specify labels and annotations filters for the extra metadata coming from node and namespace. By default all labels are included while annotations are not. To change default behaviour `include_labels`, `exclude_labels` and `include_annotations` can be defined. Those settings are useful when storing labels and annotations that require special handling to avoid overloading the storage output. Note: wildcards are not supported for those settings. The enrichment of `node` or `namespace` metadata can be individually disabled by setting `enabled: false`.
     * `deployment`: If resource is `pod` and it is created from a `deployment`, by default the deployment name isn’t added, this can be enabled by setting `deployment: true`.

docs/reference/filebeat/filebeat-module-crowdstrike.md

@@ -65,7 +65,7 @@ When you specify a setting at the command line, remember to prefix the setting w
 
 ### `falcon` fileset settings [_falcon_fileset_settings]
 
-The fileset is by default configured to collect JSON formated event data from `/var/log/crowdstrike/falconhoseclient/output`. It forwards DetectionSummaryEvent and IncidentSummaryEvent events.
+The fileset is by default configured to collect JSON formatted event data from `/var/log/crowdstrike/falconhoseclient/output`. It forwards DetectionSummaryEvent and IncidentSummaryEvent events.
 
 ```yaml
 var:

docs/reference/filebeat/filebeat-module-o365.md

@@ -113,7 +113,7 @@
 
 #### Alternative endpoints [_alternative_endpoints]
 
-This module supports custom endpoints for on-prem deployments as well as alternative endpoints (GCC High endponts, U.S. DoD, European Union, etc). In order to point the module to an alternative endpoint, you need to adjust the `authentication_endpoint` and `resource` variables accordingly. For example:
+This module supports custom endpoints for on-prem deployments as well as alternative endpoints (GCC High endpoints, U.S. DoD, European Union, etc). In order to point the module to an alternative endpoint, you need to adjust the `authentication_endpoint` and `resource` variables accordingly. For example:
 
 ```yaml
     var.api:
@@ -157,7 +157,7 @@
 
 #### Advanced configuration options [_advanced_configuration_options]
 
-The following configuration options are only recomended in case of problems. They must be nested under a single `var.api` key, like this:
+The following configuration options are only recommended in case of problems. They must be nested under a single `var.api` key, like this:
 
 ```yaml
     var.api:

docs/reference/filebeat/filebeat-reference-yml.md

@@ -684,7 +684,7 @@ filebeat.inputs:
   # To fetch all ".log" files from a specific level of subdirectories
   # /var/log/*/*.log can be used.
   # For each file found under this path, a harvester is started.
-  # Make sure not file is defined twice as this can lead to unexpected behaviour.
+  # Make sure no file is defined twice as this can lead to unexpected behaviour.
   paths:
     - /var/log/*.log
     #- c:\programdata\elasticsearch\logs\*

docs/reference/heartbeat/configuration-autodiscover.md

@@ -127,7 +127,7 @@ The `kubernetes` autodiscover provider has the following configuration settings:
 :   (Optional) Specify at what level autodiscover needs to be done at. `scope` can either take `node` or `cluster` as values. `node` scope allows discovery of resources in the specified node. `cluster` scope allows cluster wide discovery. Only `pod` and `node` resources can be discovered at node scope.
 
 `add_resource_metadata`
-:   (Optional) Specify filters and configration for the extra metadata, that will be added to the event. Configuration parameters:
+:   (Optional) Specify filters and configuration for the extra metadata, that will be added to the event. Configuration parameters:
 
     * `node` or `namespace`: Specify labels and annotations filters for the extra metadata coming from node and namespace. By default all labels are included while annotations are not. To change default behaviour `include_labels`, `exclude_labels` and `include_annotations` can be defined. Those settings are useful when storing labels and annotations that require special handling to avoid overloading the storage output. Note: wildcards are not supported for those settings. The enrichment of `node` or `namespace` metadata can be individually disabled by setting `enabled: false`.
     * `deployment`: If resource is `pod` and it is created from a `deployment`, by default the deployment name isn’t added, this can be enabled by setting `deployment: true`.

docs/reference/heartbeat/exported-fields-browser.md

@@ -60,7 +60,7 @@ duration of Load end event
 
 ## relative_trace [_relative_trace]
 
-trace event with timing information that are realtive to journey timings in microseconds
+trace event with timing information that are relative to journey timings in microseconds
 
 **`browser.relative_trace.name`**
 :   name of the trace event

docs/reference/metricbeat/configuration-autodiscover.md

@@ -147,7 +147,7 @@ The `kubernetes` autodiscover provider has the following configuration settings:
 :   (Optional) Specify at what level autodiscover needs to be done at. `scope` can either take `node` or `cluster` as values. `node` scope allows discovery of resources in the specified node. `cluster` scope allows cluster wide discovery. Only `pod` and `node` resources can be discovered at node scope.
 
 `add_resource_metadata`
-:   (Optional) Specify filters and configration for the extra metadata, that will be added to the event. Configuration parameters:
+:   (Optional) Specify filters and configuration for the extra metadata, that will be added to the event. Configuration parameters:
 
     * `node` or `namespace`: Specify labels and annotations filters for the extra metadata coming from node and namespace. By default all labels are included while annotations are not. To change default behaviour `include_labels`, `exclude_labels` and `include_annotations` can be defined. Those settings are useful when storing labels and annotations that require special handling to avoid overloading the storage output. Note: wildcards are not supported for those settings. The enrichment of `node` or `namespace` metadata can be individually disabled by setting `enabled: false`.
     * `deployment`: If resource is `pod` and it is created from a `deployment`, by default the deployment name isn’t added, this can be enabled by setting `deployment: true`.

docs/reference/packetbeat/exported-fields-dhcpv4.md

@@ -149,7 +149,7 @@ DHCPv4 event fields
 
 
 **`dhcpv4.option.subnet_mask`**
-:   The subnet mask that the client should use on the currnet network.
+:   The subnet mask that the client should use on the current network.
 
     type: ip
 

filebeat/_meta/config/filebeat.inputs.reference.yml.tmpl

@@ -251,7 +251,7 @@ filebeat.inputs:
   # To fetch all ".log" files from a specific level of subdirectories
   # /var/log/*/*.log can be used.
   # For each file found under this path, a harvester is started.
-  # Make sure not file is defined twice as this can lead to unexpected behaviour.
+  # Make sure no file is defined twice as this can lead to unexpected behaviour.
   paths:
     - /var/log/*.log
     #- c:\programdata\elasticsearch\logs\*

filebeat/docs/modules/crowdstrike.asciidoc

@@ -36,7 +36,7 @@ include::../include/config-option-intro.asciidoc[]
 [float]
 ==== `falcon` fileset settings
 
-The fileset is by default configured to collect JSON formated event data from `/var/log/crowdstrike/falconhoseclient/output`. It forwards DetectionSummaryEvent and IncidentSummaryEvent events.
+The fileset is by default configured to collect JSON formatted event data from `/var/log/crowdstrike/falconhoseclient/output`. It forwards DetectionSummaryEvent and IncidentSummaryEvent events.
 
 ["source","yaml",subs="attributes"]
 -----

filebeat/docs/modules/o365.asciidoc

@@ -104,7 +104,7 @@ right away.
 ===== Alternative endpoints
 
 This module supports custom endpoints for on-prem deployments as well as
-alternative endpoints (GCC High endponts, U.S. DoD, European Union, etc). In
+alternative endpoints (GCC High endpoints, U.S. DoD, European Union, etc). In
 order to point the module to an alternative endpoint, you need to adjust the
 `authentication_endpoint` and `resource` variables accordingly. For example:
 
@@ -163,7 +163,7 @@ known content-types:
 [float]
 ===== Advanced configuration options
 
-The following configuration options are only recomended in case of problems.
+The following configuration options are only recommended in case of problems.
 They must be nested under a single `var.api` key, like this:
 
 [source,yaml]

filebeat/filebeat.reference.yml

@@ -664,7 +664,7 @@ filebeat.inputs:
   # To fetch all ".log" files from a specific level of subdirectories
   # /var/log/*/*.log can be used.
   # For each file found under this path, a harvester is started.
-  # Make sure not file is defined twice as this can lead to unexpected behaviour.
+  # Make sure no file is defined twice as this can lead to unexpected behaviour.
   paths:
     - /var/log/*.log
     #- c:\programdata\elasticsearch\logs\*

heartbeat/_meta/fields.common.yml

@@ -366,7 +366,7 @@
         - name: relative_trace
           type: group
           description: >
-            trace event with timing information that are realtive to
+            trace event with timing information that are relative to
             journey timings in microseconds
           fields:
             - name: name

heartbeat/docs/fields.asciidoc

@@ -184,7 +184,7 @@ type: integer
 [float]
 === relative_trace
 
-trace event with timing information that are realtive to journey timings in microseconds
+trace event with timing information that are relative to journey timings in microseconds
 
 
 

packetbeat/docs/fields.asciidoc

@@ -1727,7 +1727,7 @@ type: object
 *`dhcpv4.option.subnet_mask`*::
 +
 --
-The subnet mask that the client should use on the currnet
+The subnet mask that the client should use on the current
 network.
 
 

packetbeat/protos/dhcpv4/_meta/fields.yml

@@ -146,7 +146,7 @@
             - name: subnet_mask
               type: ip
               description: |
-                The subnet mask that the client should use on the currnet
+                The subnet mask that the client should use on the current
                 network.
 
             - name: utc_time_offset_sec

x-pack/filebeat/filebeat.reference.yml

@@ -2364,7 +2364,7 @@ filebeat.inputs:
   # To fetch all ".log" files from a specific level of subdirectories
   # /var/log/*/*.log can be used.
   # For each file found under this path, a harvester is started.
-  # Make sure not file is defined twice as this can lead to unexpected behaviour.
+  # Make sure no file is defined twice as this can lead to unexpected behaviour.
   paths:
     - /var/log/*.log
     #- c:\programdata\elasticsearch\logs\*

x-pack/filebeat/module/crowdstrike/_meta/docs.md

@@ -53,7 +53,7 @@ When you specify a setting at the command line, remember to prefix the setting w
 
 ### `falcon` fileset settings [_falcon_fileset_settings]
 
-The fileset is by default configured to collect JSON formated event data from `/var/log/crowdstrike/falconhoseclient/output`. It forwards DetectionSummaryEvent and IncidentSummaryEvent events.
+The fileset is by default configured to collect JSON formatted event data from `/var/log/crowdstrike/falconhoseclient/output`. It forwards DetectionSummaryEvent and IncidentSummaryEvent events.
 
 ```yaml
 var:

x-pack/filebeat/module/o365/_meta/docs.md

@@ -101,7 +101,7 @@ Once the required permissions are added, click the *Grant admin consent* button.
 
 #### Alternative endpoints [_alternative_endpoints]
 
-This module supports custom endpoints for on-prem deployments as well as alternative endpoints (GCC High endponts, U.S. DoD, European Union, etc). In order to point the module to an alternative endpoint, you need to adjust the `authentication_endpoint` and `resource` variables accordingly. For example:
+This module supports custom endpoints for on-prem deployments as well as alternative endpoints (GCC High endpoints, U.S. DoD, European Union, etc). In order to point the module to an alternative endpoint, you need to adjust the `authentication_endpoint` and `resource` variables accordingly. For example:
 
 ```yaml
     var.api:
@@ -145,7 +145,7 @@ This module supports custom endpoints for on-prem deployments as well as alterna
 
 #### Advanced configuration options [_advanced_configuration_options]
 
-The following configuration options are only recomended in case of problems. They must be nested under a single `var.api` key, like this:
+The following configuration options are only recommended in case of problems. They must be nested under a single `var.api` key, like this:
 
 ```yaml
     var.api: