Making some final revisions

Author: yetanothertw

manage-data/data-store/data-streams.md

@@ -19,19 +19,13 @@ You can submit indexing and search requests directly to a data stream. The strea
 
 You can also use a [data stream lifecycle](../lifecycle/data-stream.md) to automate lifecycle management according to your retention requirements.
 
-:::{admonition} Streams
+:::{admonition} Managing data streams with Streams
 :applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
 
-Starting with {{stack}} version 9.2, **Streams** provides a centralized interface for managing your data in {{kib}}. It consolidates common data management tasks and eliminates the need for manual configuration of multiple applications and components. A stream directly corresponds to an {{es}} data stream, for example `logs-myapp-default`. Any changes that you make in Streams are automatically propagated to the associated data stream.
+Starting with {{stack}} version 9.2, [Streams](/solutions/observability/streams/streams.md) provides a centralized interface for managing your data in {{kib}}. It consolidates common data management tasks and eliminates the need for manual configuration of multiple applications and components. A stream maps directly to an {{es}} data stream, for example `logs-myapp-default`. Any changes that you make in Streams are automatically propagated to the associated data stream.
 
-You can use Streams to perform the following data management tasks:
-* defining parsing and field extraction logic to structure incoming data {applies_to}`"stack": "ga 9.2, preview 9.1"` 
-* configuring data retention policies {applies_to}`"stack": "ga 9.2, preview 9.1"`
-* manually adjusting index settings {applies_to}`"stack": "ga 9.2, preview 9.1"`
-* managing and updating field mappings {applies_to}`stack: ga 9.2` 
-* identifying failed and degraded documents {applies_to}`stack: ga 9.2`
+For more information, refer to [Manage data streams with Streams](/manage-data/data-store/data-streams/manage-data-stream.md#manage-data-streams-with-streams).
 
-For more information, refer to [Streams](/solutions/observability/streams/streams.md).
 :::
 
 ## Should you use a data stream? [should-you-use-a-data-stream]

manage-data/data-store/data-streams/failure-store.md

@@ -93,7 +93,7 @@ PUT _data_stream/my-datastream-existing/_options
 :::{tip}
 :applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
 
-You can also enable the data stream failure store in {{kib}}. Locate the data stream on the **Streams** page, where a stream directly corresponds to a data stream. Select a stream to view its details and go to the **Retention** tab where you can find the **Enable failure store** button.
+You can also enable the data stream failure store in {{kib}}. Locate the data stream on the **Streams** page, where a stream maps directly to a data stream. Select a stream to view its details and go to the **Retention** tab where you can find the **Enable failure store** option.
 :::
 
 ### Enable failure store via cluster setting [set-up-failure-store-cluster-setting]

manage-data/data-store/data-streams/manage-data-stream.md

@@ -23,12 +23,12 @@ In {{es-serverless}}, indices matching the `logs-*-*` pattern use the logsDB ind
 * To view information about the stream’s backing indices, click the number in the **Indices** column.
 * To modify the data retention value, select a data stream, open the **Manage**  menu, and click **Edit data retention**.
 
-## Manage data streams in Streams
+## Manage data streams with Streams [manage-data-streams-with-streams]
 ```{applies_to}
 serverless: ga
 stack: preview 9.1, ga 9.2
 ```
-Starting with {{stack}} version 9.2, [**Streams**](/solutions/observability/streams/streams.md) provides a centralized interface for managing your data in {{kib}}. It consolidates common data management tasks and eliminates the need for manual configuration of multiple applications and components. A stream directly corresponds to an {{es}} data stream, for example `logs-myapp-default`. Any changes that you make in Streams are automatically propagated to the associated data stream.
+Starting with {{stack}} version 9.2, [Streams](/solutions/observability/streams/streams.md) provides a centralized interface for managing your data in {{kib}}. It consolidates common data management tasks and eliminates the need for manual configuration of multiple applications and components. A stream maps directly to an {{es}} data stream, for example `logs-myapp-default`. Any changes that you make in Streams are automatically propagated to the associated data stream.
 
 :::{image} /manage-data/images/data-stream-management-streams.png
 :alt: Streams details
@@ -37,8 +37,9 @@ Starting with {{stack}} version 9.2, [**Streams**](/solutions/observability/stre
 
 
 You can perform the following data management tasks in Streams:
-* [define parsing and field extraction logic](ADD LINK to /solutions/observability/streams/management/extract.md) to structure incoming data {applies_to}`"stack": "ga 9.2, preview 9.1"` 
-* [configure data retention policies](ADD LINK to /solutions/observability/streams/management/retention.md) {applies_to}`"stack": "ga 9.2, preview 9.1"`
-* [manually adjust index settings](ADD LINK to/solutions/observability/streams/management/advanced.md) {applies_to}`"stack": "ga 9.2, preview 9.1"`
-* [manage and update field mappings](ADD LINK to/solutions/observability/streams/management/schema.md) {applies_to}`stack: ga 9.2` 
-* [identify failed and degraded documents](ADD LINK to/solutions/observability/streams/management/data-quality.md) {applies_to}`stack: ga 9.2`
+* [define parsing and field extraction logic](ADD LINK to /solutions/observability/streams/management/extract.md) to process and structure incoming data 
+* [configure data retention policies](ADD LINK to /solutions/observability/streams/management/retention.md)
+* [manually adjust index settings](ADD LINK to /solutions/observability/streams/management/advanced.md)
+* [manage and update field mappings](ADD LINK to /solutions/observability/streams/management/schema.md) {applies_to}`stack: unavailable 9.1`
+* [identify failed and degraded documents](ADD LINK to /solutions/observability/streams/management/data-quality.md) {applies_to}`stack: unavailable 9.1`
+* [partition data into child streams](ADD LINK to /solutions/observability/streams/management/partitioning.md) {applies_to}`stack: preview 9.2` {applies_to}`serverless: preview`

manage-data/data-store/data-streams/modify-data-stream.md

@@ -234,7 +234,7 @@ To change the `index.lifecycle.name` setting, first use the [remove policy API](
 
 You can also update certain dynamic index settings for a data stream in {{kib}}, such as the number of shards, replicas, and the refresh interval used. 
 
-Locate the data stream on the **Streams** page, where a stream directly corresponds to a data stream. Select the stream to view its details and go to the **Advanced** tab to make your adjustments. For more information, refer to [ADD LINK to /solutions/observability/streams/management/advanced.md#index-configuration when it's merged].
+Locate the data stream on the **Streams** page, where a stream maps directly to a data stream. Select the stream to view its details and go to the **Advanced** tab to make your adjustments. For more information, refer to [ADD LINK to /solutions/observability/streams/management/advanced.md#index-configuration when it's merged].
 :::
 
 ### Change a static index setting for a data stream [change-static-index-setting-for-a-data-stream]

manage-data/data-store/index-basics.md

@@ -156,8 +156,7 @@ In {{es-serverless}}, indices matching the `logs-*-*` pattern use the logsDB ind
 :::{admonition} Streams
 :applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
 
-Starting with {{stack}} version 9.2, **Streams** provides a centralized interface for common data management tasks in {{kib}}, including tasks such as [modifying data retention](/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md#data-retention-streams) values.
-For more information, refer to [Streams](/solutions/observability/streams/streams.md).
+Starting with {{stack}} version 9.2, [Streams](/solutions/observability/streams/streams.md) provides a centralized interface for common data management tasks in {{kib}}, including tasks such as [modifying data retention](/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md#data-retention-streams) values.
 :::
 
 ### Manage index templates [index-management-manage-index-templates]

manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md

@@ -107,7 +107,7 @@ Global default and max retention do not apply to data streams internal to elasti
     :::{tip}
     :applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
 
-    To adjust the retention period of a data stream in {{kib}}, locate a data stream on the **Streams** page. A stream directly corresponds to a data stream. Next, select a stream to view its details and review the **Retention** tab to find out how it's managed before making your adjustments.
+    To adjust the retention period of a data stream in {{kib}}, locate a data stream on the **Streams** page. A stream maps directly to a data stream. Next, select a stream to view its details and review the **Retention** tab to find out how it's managed before making your adjustments.
     :::
 
 * By setting the global retention via the `data_streams.lifecycle.retention.default` and/or `data_streams.lifecycle.retention.max` that are set on a cluster level. You can set this via the [update cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). For example:

manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md

@@ -13,7 +13,7 @@ products:
 In this tutorial we’ll look at migrating an existing data stream from [Index Lifecycle Management ({{ilm-init}})](../index-lifecycle-management.md) to [data stream lifecycle](../data-stream.md). The existing {{ilm-init}} managed backing indices will continue to be managed by {{ilm-init}} until they age out and get deleted by {{ilm-init}}; however, the new backing indices will be managed by data stream lifecycle. This way, a data stream is gradually migrated away from being managed by {{ilm-init}} to being managed by data stream lifecycle. As we’ll see, {{ilm-init}} and data stream lifecycle can co-manage a data stream; however, an index can only be managed by one system at a time.
 
 
-:::{admonition} Configure data retention policies in Streams
+:::{admonition} Configure data retention policies for Streams
 :applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
 
 Starting with {{stack}} version 9.2, [Streams](/solutions/observability/streams/streams.md) provides a centralized interface for common data management tasks in {{kib}}, including tasks such as configuring data retention policies. You can choose to retain your data indefinitely, for a custom period, or by following an existing ILM policy. For more information, refer to [Manage data retention in Streams](/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md#data-retention-streams).

manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md

@@ -14,7 +14,7 @@ Follow these steps to configure or remove data stream lifecycle settings for an
 
 - [Set a data stream’s lifecycle](#set-lifecycle)
 - [Remove the lifecycle for a data stream](#delete-lifecycle)
-- [Manage data retention in Streams](#data-retention-streams)
+- [Manage data retention for Streams](#data-retention-streams)
 
 Note that these steps are for data stream lifecycle only. For the steps to configure {{ilm}}, refer to the [{{ilm-init}} documentation](/manage-data/lifecycle/index-lifecycle-management.md). For a comparison between the two, refer to [](/manage-data/lifecycle.md).
 
@@ -215,17 +215,18 @@ GET .ds-my-data-stream-*/_lifecycle/explain
 :::
 :::::
 
-## Manage data retention in Streams [data-retention-streams]
+## Manage data retention for Streams [data-retention-streams]
 ```{applies_to}
 serverless: ga
 stack: preview 9.1, ga 9.2
 ```
 
-Starting with {{stack}} version 9.2, **Streams** provides a centralized interface for common data management tasks in {{kib}}.
+Starting with {{stack}} version 9.2, **Streams** provides a centralized interface for common data management tasks in {{kib}}, including getting insight into how your data streams retain data. 
 
 1. Go to the **Streams** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
-1. A stream directly corresponds to an {{es}} data stream. Select a stream to view its details.
+1. Each stream maps directly to an {{es}} data stream. Select a stream to view its details.
 1. Go to the **Retention** tab to set how long your stream retains data and to get insight into your stream's data ingestion and storage size.
-1. Select **Edit data retention** and choose to retain your data indefinitely, for a custom period, or by following an existing ILM policy.
+1. Select **Edit data retention** and choose to retain your data indefinitely, for a custom period, or by following an existing ILM policy. You can also use the data retention configuration that's set in the index template by enabling the  **Inherit from index template** option. If you use this option, you don't need to specify a custom retention period or policy.
+
+For more information about the retention configuration options, refer to [](ADD LINK to /solutions/observability/streams/management/retention.md).
 
-Any changes you make in Streams are automatically propagated to the associated data stream.

manage-data/lifecycle/index-lifecycle-management/policy-view-status.md

@@ -54,8 +54,8 @@ To learn how to create a specialized ILM policy for any data stream, such as tho
 Starting with {{stack}} version 9.2, [Streams](/solutions/observability/streams/streams.md) provides a centralized interface for common data management tasks in {{kib}}.
 
 1. Go to the **Streams** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
-1. A stream directly corresponds to an {{es}} data stream. Select a stream to view its details.
-1. Go to the **Retention** tab to see how long your stream retains data and to get insight into your stream's data ingestion and storage size. A stream can retain the data indefinitely, for a custom period, or by following an existing ILM policy.
+1. A stream maps directly to an {{es}} data stream. Select a stream to view its details.
+1. Go to the **Retention** tab to see how long your stream retains data and to get insight into your stream's data ingestion and storage size. A stream can retain the data indefinitely, for a custom period, or by following an existing ILM policy. For more information, refer to [](ADD LINK to /solutions/observability/streams/management/retention.md).
 
 ::::