Clarify the snapshot doc

deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md

@@ -162,7 +162,11 @@ These recommendations do not apply to indices using better binary quantization (
 
 ## Available {{es}} APIs [elasticsearch-differences-serverless-apis-availability]
 
-Because {{serverless-full}} manages infrastructure automatically, certain Elasticsearch APIs are not available:
+::::{important}
+In {{serverless-full}}, configuration is limited to certain APIs, as Elastic automatically manages the infrastructure. As we are responsible for maintaining cluster stability, we make informed decisions about permissible actions to prevent unintended changes that could compromise service availability, performance, and data integrity, thereby ensuring the reliability of Serverless projects.
+::::
+
+
 
 Infrastructure operations
 :   * All `_nodes/*` operations
@@ -201,7 +205,9 @@ Refer to the [{{es-serverless}} API reference](https://www.elastic.co/docs/api/d
 
 ## Available {{es}} settings [elasticsearch-differences-serverless-settings-availability]
 
-In {{serverless-full}} Elasticsearch projects, you can only configure [index-level settings](elasticsearch://reference/elasticsearch/index-settings/index.md). Cluster-level settings and node-level settings are fully managed by Elastic.
+::::{important}
+In {{serverless-full}} Elasticsearch projects, configuration is limited to certain [index-level settings](elasticsearch://reference/elasticsearch/index-settings/index.md), while Elastic fully manages cluster-level and node-level settings. As we are responsible for maintaining cluster stability, we make informed decisions about permissible actions to prevent unintended changes that could compromise service availability, performance, and data integrity, thereby ensuring the reliability of Serverless projects.
+::::
 
 Available settings
 :   **Index-level settings**: Settings that control how documents are processed, stored, and searched are available to end users. These include:

deploy-manage/tools/snapshot-and-restore/create-snapshots.md

@@ -11,9 +11,9 @@
   - id: elasticsearch
 ---
 
-# Create snapshots [snapshots-take-snapshot]
+# Create, monitor and delete snapshots [snapshots-take-snapshot]
 
-This guide shows you how to take snapshots of a running cluster. You can later [restore a snapshot](restore-snapshot.md) to recover or transfer its data.
+This guide shows you how to create, monitor and delete snapshots of a running cluster. You can later [restore a snapshot](restore-snapshot.md) to recover or transfer its data.
 
 In this guide, you’ll learn how to:
 
@@ -187,6 +187,20 @@
 
 A snapshot repository can safely scale to thousands of snapshots. However, to manage its metadata, a large repository requires more memory on the master node. Retention rules ensure a repository’s metadata doesn’t grow to a size that could destabilize the master node.
 
+### Update an existing {{slm-init}} policy [create-slm-policy]
+
+You can update an existing {{slm-init}} policy after it's created. To manage {{slm-init}} in {{kib}}, go to the main menu and click **Stack Management** > **Snapshot and Restore** > **Policies**, click the pencil icon, and make the desired change. 
+
+For example, you can change the schedule, or snapshot retention related configurations.
+
+
+![change schedule](/manage-data/images/elasticsearch-reference-change-slm-schedule.png)
+
+![change snapshot retention](/manage-data/images/elasticsearch-reference-change-slm-snapshot-retention.png)
+
+
+You can also update {{slm-init}} policy using the [{{slm-init}} APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-slm), as described in [Create an {{slm-init}} policy](#create-slm-policy).
+
 
 ## Manually create a snapshot [manually-create-snapshot]
 
@@ -242,7 +256,11 @@
 
 ## Delete or cancel a snapshot [delete-snapshot]
 
-To delete a snapshot in {{kib}}, go to the **Snapshots** page and click the trash icon under the **Actions** column. You can also use the [delete snapshot API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-delete).
+To delete a snapshot in {{kib}}, go to the **Snapshots** page and click the trash icon under the **Actions** column. To delete multiple snapshots at once, select the snapshots first, and then click `Delete snapshots` button. 
+
+![delete snapshot](/manage-data/images/elasticsearch-reference-delete-snapshots.png)
+
+You can also use the [delete snapshot API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-delete).
 
 ```console
 DELETE _snapshot/my_repository/my_snapshot_2099.05.06