update wording

Author: mdbirnstiehl

solutions/observability/logs/streams/management/advanced.md

@@ -4,7 +4,7 @@ applies_to:
 ---
 # Configure advanced settings [streams-advanced-settings]
 
-The **Advanced** tab shows the lower-level details of your stream. While streams attempt to make things as easy as possible, streams does not support every change yet. For these, you can manually interact with the index or component templates, or modify any of the other ingest pipelines that are being used.
+The **Advanced** tab shows the lower-level details of your stream. While Streams attempt to make things as easy as possible, it doesn't support every change yet. For these, you can manually interact with the index or component templates, or modify any of the other ingest pipelines that are being used.
 This UI is only intended for more advanced users.
 
 ![alt text](<advanced.png>)

solutions/observability/logs/streams/management/extract.md

@@ -102,7 +102,7 @@ These failures may be something you should address, but in some cases they also
 
 ### Mapping Conflicts
 
-As part of processing, streams also checks for mapping conflicts by simulating the change end to end. If a mapping conflict is detected, streams marks the processor as failed and displays a failure message:
+As part of processing, Streams also checks for mapping conflicts by simulating the change end to end. If a mapping conflict is detected, Streams marks the processor as failed and displays a failure message:
 
 ![alt text](<mapping-conflicts.png>)
 
@@ -114,35 +114,35 @@ Once saved, the processor also gives you a quick look at how successful the proc
 
 ## Advanced: How and where do these changes get applied to the underlying datastream? [streams-applied-changes]
 
-When you save processors, streams modifies the "best matching" ingest pipeline for the data stream. In short, streams either chooses the best matching pipeline ending in `@custom` that is already part of your data stream, or it adds one for you.
+When you save processors, Streams modifies the "best matching" ingest pipeline for the data stream. In short, Streams either chooses the best matching pipeline ending in `@custom` that is already part of your data stream, or it adds one for you.
 
 Streams identifies the appropriate @custom pipeline (for example, `logs-myintegration@custom` or `logs@custom`).
 It checks the default_pipeline that is set on the datastream.
 
 You can view the default pipeline at **Management** → **Advanced** under **Ingest pipeline**.
 In this default pipeline, we locate the last processor that calls a pipeline ending in `@custom`. For integrations, this would result in a pipeline name like `logs-myintegration@custom`. Without an integration, the only `@custom` pipeline available may be `logs@custom`.
 
-- If no default pipeline is detected, streams adds a default pipeline to the data stream by updating the index templates.
-- If a default pipeline is detected, but it does not contain a custom pipeline, streams adds the pipeline processor directly to the pipeline.
+- If no default pipeline is detected, Streams adds a default pipeline to the data stream by updating the index templates.
+- If a default pipeline is detected, but it does not contain a custom pipeline, Streams adds the pipeline processor directly to the pipeline.
 
-Streams then adds a pipeline processor to the end of that `@custom` pipeline. This processor definition directs matching documents to a dedicated pipeline managed by streams called `<data_stream_name>@stream.processing`:
+Streams then adds a pipeline processor to the end of that `@custom` pipeline. This processor definition directs matching documents to a dedicated pipeline managed by Streams called `<data_stream_name>@stream.processing`:
 
 // Example processor added to the relevant @custom pipeline
 {
   "pipeline": {
     "name": "<data_stream_name>@stream.processing", // e.g., [email protected]
     "if": "ctx._index == '<data_stream_name>'",
     "ignore_missing_pipeline": true,
-    "description": "Call the stream's managed pipeline - do not change this manually but instead use the streams UI or API"
+    "description": "Call the stream's managed pipeline - do not change this manually but instead use the Streams UI or API"
   }
 }
 
 Streams then creates and manages the `<data_stream_name>@stream.processing` pipeline, placing the processors you configured in the UI (Grok, Set, etc.) inside it.
 
 ### User interaction with pipelines
 
-Do not manually modify the `<data_stream_name>@stream.processing` pipeline created by streams.
-You can still add your own processors manually to the `@custom` pipeline if needed. Adding processors before the pipeline processor streams created may cause unexpected behavior.
+Do not manually modify the `<data_stream_name>@stream.processing` pipeline created by Streams.
+You can still add your own processors manually to the `@custom` pipeline if needed. Adding processors before the pipeline processor Streams created may cause unexpected behavior.
 
 ## Known limitations [streams-known-limitations]
 

solutions/observability/logs/streams/management/retention.md

@@ -5,7 +5,7 @@ applies_to:
 
 # Manage data retention [streams-data-retention]
 
-Use the **Data retention** page under the **Management** tab to set how long your stream retains data and to get insight into your streams data ingestion and storage size.
+Use the **Data retention** page under the **Management** tab to determine how long your stream retains data and to get insight into your stream's data ingestion and storage size.
 
 ![alt text](<retention.png>)
 

solutions/observability/logs/streams/streams.md

@@ -21,13 +21,13 @@ Streams requires the following Elastic Cloud Serverless roles:
 
 % - TODO
 
-## Access streams
-To access streams:
+## Access Streams
+To access Streams:
 
 - From the navigation menu, select **Streams**.
 
 - From discover, expand a document's details flyout.
-Select the **Stream** link or action associated with the document's data stream to open the streams interface, filtered to show only the selected stream.
+Select the **Stream** link or action associated with the document's data stream to open the Streams interface, filtered to show only the selected stream.
 
 
 ## Overview tab [streams-overview-tab]