Adding mentions of streams in the failure store for data stream doc

Author: yetanothertw

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

@@ -27,7 +27,7 @@ Starting with {{stack}} version 9.2, **Streams** provides a centralized interfac
 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 configuration settings {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`
 

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

@@ -88,6 +88,12 @@ PUT _data_stream/my-datastream-existing/_options
 
 1. Redirecting failed documents into the failure store will now be disabled.
 
+:::{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.
+:::
+
 ### Enable failure store via cluster setting [set-up-failure-store-cluster-setting]
 
 If you have a large number of existing data streams you may want to enable their failure stores in one place. Instead of updating each of their options individually, set `data_streams.failure_store.enabled` to a list of index patterns in the [cluster settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). Any data streams that match one of these patterns will operate with their failure store enabled.

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

@@ -91,6 +91,11 @@ To add a mapping for a new field to a data stream, following these steps:
     ```
 
 
+:::{tip}
+:applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
+
+You can also add a new field mapping to a data stream 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 **Schema** tab where you can find the **+ Add field** button.
+:::
 
 ### Change an existing field mapping in a data stream [change-existing-field-mapping-in-a-data-stream]
 
@@ -168,6 +173,12 @@ The documentation for each [mapping parameter](elasticsearch://reference/elastic
     ```
 
 
+:::{tip}
+:applies_to: {"stack": "ga 9.2, preview 9.1", "serverless": "ga"}
+
+You can also update a field's mapping in a data stream 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 **Schema** tab. Next, find the field for which you want to update the mapping and select the required field action. For more information, refer to [ADD LINK to /solutions/observability/streams/management/schema.md when it's merged].
+:::
+
 Except for supported mapping parameters, we don’t recommend you change the mapping or field data type of existing fields, even in a data stream’s matching index template or its backing indices. Changing the mapping of an existing field could invalidate any data that’s already indexed.
 
 If you need to change the mapping of an existing field, create a new data stream and reindex your data into it. See [Use reindex to change mappings or settings](../data-streams/modify-data-stream.md#data-streams-use-reindex-to-change-mappings-settings).