Fix more typos

vishaangelova · vishaangelova · commit dd42150d0bcf · 2025-10-01T11:06:52.000+02:00
diff --git a/manage-data/ingest/ingest-reference-architectures/ls-multi.md b/manage-data/ingest/ingest-reference-architectures/ls-multi.md
@@ -22,7 +22,7 @@ Use when
 :   Data collected by {{agent}} needs to be routed to different {{es}} clusters or non-{{es}} destinations depending on the content
 
 Example
-:   Let’s take an example of a Windows workstation, for which we are collecting different types of logs using the System and Windows integrations. These logs need to be sent to different {{es}} clusters and to S3 for backup and a mechanism to send it to other destinations such as different SIEM solutions. In addition, the {{es}} destination is derived based on the type of datastream and an organization identifier.
+:   Let’s take an example of a Windows workstation, for which we are collecting different types of logs using the System and Windows integrations. These logs need to be sent to different {{es}} clusters and to S3 for backup and a mechanism to send it to other destinations such as different SIEM solutions. In addition, the {{es}} destination is derived based on the type of data stream and an organization identifier.
 
     In such use cases, agents send the data to {{ls}} as a routing mechanism to different destinations. Note that the System and Windows integrations must be installed on all {{es}} clusters to which the data is routed.
 
diff --git a/reference/fleet/add-cloud-metadata-processor.md b/reference/fleet/add-cloud-metadata-processor.md
@@ -55,7 +55,7 @@ The metadata that is added to events varies by hosting provider. For examples, r
 | --- | --- | --- | --- |
 | `timeout` | No | `3s` | Maximum amount of time to wait for a successful response when detecting the hosting provider. If a timeout occurs, no instance metadata is added to the events. This makes it possible to enable this processor for all your deployments (in the cloud or on-premise). |
 | `providers` | No |  | List of provider names to use. If `providers` is not configured, all providers that do not access a remote endpoint are enabled by default. The list of providers may alternatively be configured with the environment variable `BEATS_ADD_CLOUD_METADATA_PROVIDERS`, by setting it to a comma-separated list of provider names.<br><br>The list of supported provider names includes:<br><br>* `alibaba` or `ecs` for the Alibaba Cloud provider (disabled by default).<br>* `azure` for Azure Virtual Machine (enabled by default).<br>* `digitalocean` for Digital Ocean (enabled by default).<br>* `aws` or `ec2` for Amazon Web Services (enabled by default).<br>* `gcp` for Google Compute Engine (enabled by default).<br>* `openstack` or `nova` for Openstack Nova (enabled by default).<br>* `openstack-ssl` or `nova-ssl` for Openstack Nova when SSL metadata APIs are enabled (enabled by default).<br>* `tencent` or `qcloud` for Tencent Cloud (disabled by default).<br>* `huawei` for Huawei Cloud (enabled by default).<br> |
-| `overwrite` | No | `false` | Whether to overwrite existing cloud fields. If `true`, the processoroverwrites existing `cloud.*` fields. |
+| `overwrite` | No | `false` | Whether to overwrite existing cloud fields. If `true`, the processor overwrites existing `cloud.*` fields. |
 
 The `add_cloud_metadata` processor supports SSL options to configure the http client used to query cloud metadata.
 
diff --git a/reference/fleet/add_cloudfoundry_metadata-processor.md b/reference/fleet/add_cloudfoundry_metadata-processor.md
@@ -66,5 +66,5 @@ For efficient annotation, application metadata retrieved by the Cloud Foundry cl
 | `client_secret` | Yes |  | Client Secret to authenticate with Cloud Foundry. |
 | `cache_duration` | No | `120s` | Maximum amount of time to cache an application’s metadata. |
 | `cache_retry_delay` | No | `20s` | Time to wait before trying to obtain an application’s metadata again in case of error. |
-| `ssl` | No |  | SSL configuration to use when connecting to Cloud Foundry. For a list ofavailable settings, refer to [SSL/TLS](/reference/fleet/elastic-agent-ssl-configuration.md), specificallythe settings under [Table 7, Common configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#common-ssl-options) and [Table 8, Client configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#client-ssl-options). |
+| `ssl` | No |  | SSL configuration to use when connecting to Cloud Foundry. For a list of available settings, refer to [SSL/TLS](/reference/fleet/elastic-agent-ssl-configuration.md), specifically the settings under [Table 7, Common configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#common-ssl-options) and [Table 8, Client configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#client-ssl-options). |
 
diff --git a/reference/fleet/add_docker_metadata-processor.md b/reference/fleet/add_docker_metadata-processor.md
@@ -74,7 +74,7 @@ If the Docker daemon is restarted, the mounted socket will become invalid, and m
 | Name | Required | Default | Description |
 | --- | --- | --- | --- |
 | `host` | No | `unix:///var/run/docker.sock` | Docker socket (UNIX or TCP socket). |
-| `ssl` | No |  | SSL configuration to use when connecting to the Docker socket. For a list ofavailable settings, refer to [SSL/TLS](/reference/fleet/elastic-agent-ssl-configuration.md), specificallythe settings under [Table 7, Common configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#common-ssl-options) and [Table 8, Client configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#client-ssl-options). |
+| `ssl` | No |  | SSL configuration to use when connecting to the Docker socket. For a list of available settings, refer to [SSL/TLS](/reference/fleet/elastic-agent-ssl-configuration.md), specifically the settings under [Table 7, Common configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#common-ssl-options) and [Table 8, Client configuration options](/reference/fleet/elastic-agent-ssl-configuration.md#client-ssl-options). |
 | `match_fields` | No |  | List of fields to match a container ID. At least one of the fields most hold a container ID to get the event enriched. |
 | `match_pids` | No | `["process.pid", "process.parent.pid"]` | List of fields that contain process IDs. If the process is running in Docker, the event will be enriched. |
 | `match_source` | No | `true` | Whether to match the container ID from a log path present in the `log.file.path` field. |
diff --git a/reference/fleet/agent-command-reference.md b/reference/fleet/agent-command-reference.md
@@ -441,7 +441,7 @@ elastic-agent inspect components [--show-config]
     :   Use to display the configuration in all units.
 
     `--show-spec`
-    :   Use to get input/output runtime spectification for a component.
+    :   Use to get input/output runtime specification for a component.
 
 
 `--help`
diff --git a/reference/fleet/community_id-processor.md b/reference/fleet/community_id-processor.md
@@ -55,5 +55,5 @@ If the necessary fields are not present in the event, the processor silently con
 | --- | --- | --- | --- |
 | `fields` | No |  | Field names that the processor reads from:<br><br>`source_ip`<br>:   Field containing the source IP address.<br><br>`source_port`<br>:   Field containing the source port.<br><br>`destination_ip`<br>:   Field containing the destination IP address.<br><br>`destination_port`<br>:   Field containing the destination port.<br><br>`iana_number`<br>:   Field containing the IANA number. The following protocol numbers are currently supported: 1 ICMP, 2 IGMP, 6 TCP, 17 UDP, 47 GRE, 58 ICMP IPv6, 88 EIGRP, 89 OSPF, 103 PIM, and 132 SCTP.<br><br>`transport`<br>:   Field containing the transport protocol. Used only when the `iana_number` field is not present.<br><br>`icmp_type`<br>:   Field containing the ICMP type.<br><br>`icmp_code`<br>:   Field containing the ICMP code.<br> |
 | `target` | No |  | Field that the computed hash is written to. |
-| `seed` | No |  | Seed for the community ID hash. Must be between 0 and 65535 (inclusive). Theseed can prevent hash collisions between network domains, such as a staging andproduction network that use the same addressing scheme. This setting results ina 16-bit unsigned integer that gets incorporated into all generated hashes. |
+| `seed` | No |  | Seed for the community ID hash. Must be between 0 and 65535 (inclusive). The seed can prevent hash collisions between network domains, such as a staging and production network that use the same addressing scheme. This setting results ina 16-bit unsigned integer that gets incorporated into all generated hashes. |
 
diff --git a/reference/fleet/data-streams-ilm-tutorial.md b/reference/fleet/data-streams-ilm-tutorial.md
@@ -17,7 +17,7 @@ These tutorials explain how to apply a custom {{ilm-init}} policy to an integrat
 
 For certain features you’ll need to use a slightly different procedure to manage the index lifecycle:
 
-* APM: For verions 8.15 and later, refer to [Index lifecycle management](/solutions/observability/apm/index-lifecycle-management.md).
+* APM: For versions 8.15 and later, refer to [Index lifecycle management](/solutions/observability/apm/index-lifecycle-management.md).
 * Synthetic monitoring: Refer to [Manage data retention](/solutions/observability/synthetics/manage-data-retention.md).
 * Universal Profiling: Refer to [Universal Profiling index life cycle management](/solutions/observability/infra-and-hosts/universal-profiling-index-life-cycle-management.md).
 
diff --git a/reference/fleet/data-streams.md b/reference/fleet/data-streams.md
@@ -97,7 +97,7 @@ When you install an integration, {{fleet}} creates two default `@custom` compone
 * A `@custom` component template allowing customization across all documents of a given data stream type, named following the pattern: `<data_stream_type>@custom`.
 * A `@custom` component template for each data stream, named following the pattern: `<name_of_data_stream>@custom`.
 
-The `@custom` component template specific to a datastream has higher precedence over the data stream type `@custom` component template.
+The `@custom` component template specific to a data stream has higher precedence over the data stream type `@custom` component template.
 
 You can edit a `@custom` component template to customize your {{es}} indices:
 
diff --git a/reference/fleet/detect_mime_type-processor.md b/reference/fleet/detect_mime_type-processor.md
@@ -36,7 +36,7 @@ In this example, `http.request.body.content` is used as the source, and `http.re
 | Name | Required | Default | Description |
 | --- | --- | --- | --- |
 | `field` | Yes |  | Field used as the data source. |
-| `target` | Yes |  | Field to populate with the detected type. You can use the `@metadata.` prefixto set the value in the event metadata instead of fields. |
+| `target` | Yes |  | Field to populate with the detected type. You can use the `@metadata.` prefix to set the value in the event metadata instead of fields. |
 
 See [Conditions](/reference/fleet/dynamic-input-configuration.md#conditions) for a list of supported conditions.
 
diff --git a/reference/fleet/hints-annotations-autodiscovery.md b/reference/fleet/hints-annotations-autodiscovery.md
@@ -144,7 +144,7 @@ co.elastic.hints/processors.dissect.tokenizer: "%{key2} %{key1}"
 In the above sample the processor definition tagged with `1` would be executed first.
 
 ::::{important}
-Processor configuration is not supported on the datastream level, so annotations like `co.elastic.hints/<datastream>.processors` are ignored.
+Processor configuration is not supported on the data stream level, so annotations like `co.elastic.hints/<datastream>.processors` are ignored.
 ::::
 
 
diff --git a/reference/fleet/ingest-pipeline-kubernetes.md b/reference/fleet/ingest-pipeline-kubernetes.md
@@ -37,7 +37,7 @@ Enabling deployment and cronjob metadata enrichment leads to an increase of Elas
 
 As an alternative to keeping the feature enabled and using more memory resources for {{agent}}, users can make use of ingest pipelines to add the missing fields of `kubernetes.deployment.name` and `kubernetes.cronjob.name`.
 
-Navigate to `state_pod` datastream under: **Kubernetes Integration Policy > Collect Kubernetes metrics from Kube-state-metrics > Kubernetes Pod Metrics**.
+Navigate to `state_pod` data stream under: **Kubernetes Integration Policy > Collect Kubernetes metrics from Kube-state-metrics > Kubernetes Pod Metrics**.
 
 Create the following custom ingest pipeline with two processors:
 
diff --git a/reference/fleet/integrations-assets-best-practices.md b/reference/fleet/integrations-assets-best-practices.md
@@ -67,7 +67,7 @@ While creating a `@custom` component template for a package integration is suppo
 
 For example:
 
-* If the `@package` component template of an integration is changed from a "normal" datastream to `TSDB` or `LogsDB`, some of the custom settings or mappings introduced may not be compatible with these indexing modes.
+* If the `@package` component template of an integration is changed from a "normal" data stream to `TSDB` or `LogsDB`, some of the custom settings or mappings introduced may not be compatible with these indexing modes.
 * If the type of an ECS field is overridden from, for example, `keyword` to `text`, aggregations based on that field may be prevented for built-in dashboards.
 
 A similar caution against custom index mappings is noted in [Edit the {{es}} index template](/reference/fleet/data-streams.md#data-streams-index-templates-edit).
@@ -86,6 +86,6 @@ When you clone the index template of an integration package, this involves risk
 
 Additionally, cloning index templates to add or inject additional component templates cannot be tested by Elastic, so we cannot guarantee that the template will work in future releases.
 
-If you want to change the ILM Policy, the number of shards, or other settings for the datastreams of one or more integrations, but the changes do not need to be specific to a given namespace, it’s highly  recommended to use the `package@custom` component templates, as described in [Scenario 1](/reference/fleet/data-streams-scenario1.md) and [Scenario 2](/reference/fleet/data-streams-scenario2.md) of the Customize data retention policies tutorial, so as to avoid the problems mentioned above.
+If you want to change the ILM Policy, the number of shards, or other settings for the data streams of one or more integrations, but the changes do not need to be specific to a given namespace, it’s highly  recommended to use the `package@custom` component templates, as described in [Scenario 1](/reference/fleet/data-streams-scenario1.md) and [Scenario 2](/reference/fleet/data-streams-scenario2.md) of the Customize data retention policies tutorial, so as to avoid the problems mentioned above.
 
 If you want to change these settings for the data streams in one or more integrations and the changes **need to be namespace specific**, then you can do so following the steps in [Scenario 3](/reference/fleet/data-streams-scenario3.md) of the Customize data retention policies tutorial, but be aware of the restrictions mentioned above.
diff --git a/reference/fleet/migrate-auditbeat-to-agent.md b/reference/fleet/migrate-auditbeat-to-agent.md
@@ -40,7 +40,7 @@ The following table describes the integrations you can use instead of {{auditbea
 | [System.process](beats://reference/auditbeat/auditbeat-dataset-system-process.md) dataset | [Endpoint](/solutions/security/configure-elastic-defend/install-elastic-defend.md) | Best replacement because out of the box it reports events for every process in [ECS](integration-docs://reference/index.md) format and has excellent integration in [Kibana](/get-started/the-stack.md). |
 | [Custom Windows event log](integration-docs://reference/winlog/index.md) and [Sysmon](integration-docs://reference/sysmon_linux/index.md) integrations | Provide process data. |
 | [Osquery](integration-docs://reference/osquery/index.md) or[Osquery Manager](integration-docs://reference/osquery_manager/index.md) integration | Collect data from the [process](https://www.osquery.io/schema/5.1.0/#process) table on some operating systems without polling. |
-| [System.socket](beats://reference/auditbeat/auditbeat-dataset-system-socket.md) dataset | [Endpoint](/solutions/security/configure-elastic-defend/install-elastic-defend.md) | Best replacement because it supports monitoring network connections on Linux,Windows, and MacOS. Includes process and user metadata. Currently does not do flow accounting (byte and packet counts) or domain name enrichment (but doescollect DNS queries separately). |
+| [System.socket](beats://reference/auditbeat/auditbeat-dataset-system-socket.md) dataset | [Endpoint](/solutions/security/configure-elastic-defend/install-elastic-defend.md) | Best replacement because it supports monitoring network connections on Linux,Windows, and MacOS. Includes process and user metadata. Currently does not do flow accounting (byte and packet counts) or domain name enrichment (but does collect DNS queries separately). |
 | [Osquery](integration-docs://reference/osquery/index.md) or [Osquery Manager](integration-docs://reference/osquery_manager/index.md) integration | Monitor socket events via the [socket_events](https://www.osquery.io/schema/5.1.0/#socket_events) table for Linux and MacOS. |
 | [System.user](beats://reference/auditbeat/auditbeat-dataset-system-user.md) dataset | [Osquery](integration-docs://reference/osquery/index.md) or [Osquery Manager](integration-docs://reference/osquery_manager/index.md) integration | Monitor local users via the [user](https://www.osquery.io/schema/5.1.0/#user) table for Linux, Windows, and MacOS. |
 
diff --git a/reference/fleet/processor-parse-aws-vpc-flow-log.md b/reference/fleet/processor-parse-aws-vpc-flow-log.md
@@ -127,7 +127,7 @@ This mode maps the original VPC flow log fields into their associated Elastic Co
 
 ### ECS and Original [_ecs_and_original]
 
-This mode maps the fields into ECS and retains all the original fields. Below is an example document produced using `ecs_and_orignal` mode.
+This mode maps the fields into ECS and retains all the original fields. Below is an example document produced using `ecs_and_original` mode.
 
 ```json
 {
diff --git a/reference/fleet/script-processor.md b/reference/fleet/script-processor.md
@@ -101,11 +101,11 @@ The `Event` object passed to the `process` method has the following API.
 
 | Method | Description |
 | --- | --- |
-| `Get(string)` | Get a value from the event (either a scalar or an object). If the key does notexist `null` is returned. If no key is provided then an object containing allfields is returned.<br>**Example**: `var value = event.Get(key);` |
-| `Put(string, value)` | Put a value into the event. If the key was already set then theprevious value is returned. It throws an exception if the key cannot be setbecause one of the intermediate values is not an object.<br>**Example**: `var old = event.Put(key, value);` |
-| `Rename(string, string)` | Rename a key in the event. The target key must not exist. Itreturns true if the source key was successfully renamed to the target key.<br>**Example**: `var success = event.Rename("source", "target");` |
+| `Get(string)` | Get a value from the event (either a scalar or an object). If the key does not exist `null` is returned. If no key is provided then an object containing all fields is returned.<br>**Example**: `var value = event.Get(key);` |
+| `Put(string, value)` | Put a value into the event. If the key was already set then the previous value is returned. It throws an exception if the key cannot be set because one of the intermediate values is not an object.<br>**Example**: `var old = event.Put(key, value);` |
+| `Rename(string, string)` | Rename a key in the event. The target key must not exist. It returns true if the source key was successfully renamed to the target key.<br>**Example**: `var success = event.Rename("source", "target");` |
 | `Delete(string)` | Delete a field from the event. It returns true on success.<br>**Example**: `var deleted = event.Delete("user.email");` |
-| `Cancel()` | Flag the event as cancelled which causes the processor to dropevent.<br>**Example**: `event.Cancel(); return;` |
-| `Tag(string)` | Append a tag to the `tags` field if the tag does not alreadyexist. Throws an exception if `tags` exists and is not a string or a list ofstrings.<br>**Example**: `event.Tag("user_event");` |
-| `AppendTo(string, string)` | `AppendTo` is a specialized `Put` method that converts the existing value to anarray and appends the value if it does not already exist. If there is anexisting value that’s not a string or array of strings then an exception isthrown.<br>**Example**: `event.AppendTo("error.message", "invalid file hash");` |
+| `Cancel()` | Flag the event as cancelled which causes the processor to drop event.<br>**Example**: `event.Cancel(); return;` |
+| `Tag(string)` | Append a tag to the `tags` field if the tag does not already exist. Throws an exception if `tags` exists and is not a string or a list of strings.<br>**Example**: `event.Tag("user_event");` |
+| `AppendTo(string, string)` | `AppendTo` is a specialized `Put` method that converts the existing value to an array and appends the value if it does not already exist. If there is an existing value that’s not a string or array of strings then an exception is thrown.<br>**Example**: `event.AppendTo("error.message", "invalid file hash");` |
 
diff --git a/reference/fleet/timestamp-processor.md b/reference/fleet/timestamp-processor.md
diff --git a/reference/fleet/upgrade-standalone.md b/reference/fleet/upgrade-standalone.md
