Enhancements to common questions, migrate with logstash, fix heading order

serverless/pages/index-management.mdx

@@ -83,7 +83,6 @@ current index lifecycle policy, click the stream's name. From this view, you can
 further explore data within the data stream.
 
 * <DocBadge template="technical preview" /> To edit the data retention value, open the **Manage** menu, and then click **Edit data retention**.
-This action is only available if your data stream is not managed by an ILM policy.
 
 {/*
 TO-DO: This screenshot is not accurate since it contains several toggles that don't exist in serverless.

serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.mdx

@@ -41,9 +41,9 @@ Set the value to port `:443` instead.
 
 To use ((ls)) to send data to ((es3)), you must be using:
 - ((ls)) 8.10.1 or later
-- ((ls)) [Elasticsearch output plugin](((logstash-ref))/plugins-outputs-elasticsearch.html) 11.18.0 or later
-- ((ls)) [Elasticsearch input plugin](((logstash-ref))/plugins-inputs-elasticsearch.html) 4.18.0 or later
-- ((ls)) [Elasticsearch filter plugin](((logstash-ref))/plugins-filters-elasticsearch.html) 3.16.0 or later
+- ((ls)) [((es)) output plugin](((logstash-ref))/plugins-outputs-elasticsearch.html) 11.18.0 or later
+- ((ls)) [((es)) input plugin](((logstash-ref))/plugins-inputs-elasticsearch.html) 4.18.0 or later
+- ((ls)) [((es)) filter plugin](((logstash-ref))/plugins-filters-elasticsearch.html) 3.16.0 or later
 
 
 ## Secure connection
@@ -63,7 +63,7 @@ You can create as many API keys as necessary.
 When you set up your API keys, use the metadata option to tag each API key with details that are meaningful to you.
 This step makes managing multiple API keys easier.
 
-After you generate an API key, add it to your ((ls)) [Elasticsearch output plugin](((logstash-ref))/plugins-outputs-elasticsearch.html) config file's `api_key` setting.
+After you generate an API key, add it to your ((ls)) [((es)) output plugin](((logstash-ref))/plugins-outputs-elasticsearch.html) config file's `api_key` setting.
 Here's an example:
 
 ```bash
@@ -74,6 +74,15 @@ output {
 }
 ```
 
+## Migrating Elasticsearch data using ((ls))
+
+You can use ((ls)) to migrate data from self-managed ((es)) or ((ess)) to ((es3)), or to migrate data from one ((es3)) deployment to another. 
+
+Create a [((ls)) pipeline](((logstash-ref))/configuration.html) that includes the ((es)) [input plugin](((logstash-ref))/plugins-inputs-elasticsearch.html) and [output plugin](((logstash-ref))/plugins-outputs-elasticsearch.html).
+
+Configure the ((es)) input to point to your source deployment or instance, and configure the ((es)) output with the `cloud_id` and `api_key` settings for your target ((es3)) instance. 
+
+If your origin index is using <DocLink slug="/serverless/elasticsearch/differences">settings that aren't supported in Serverless</DocLink>, then you might need to adjust your index settings. 
 ## Next steps
 
 Check out the [Logstash product page](https://www.elastic.co/logstash) to see what ((ls)) can do for you.

serverless/pages/technical-preview-limitations.mdx

@@ -14,7 +14,7 @@ The following are currently not available:
 - Cross-cluster search and cross-cluster replication
 - Snapshot and restore 
 - Clone index API
-- Migrations from non-serverless ((es)) deployments
+- Migrations from non-serverless ((es)) deployments. In the interim, you can <DocLink slug="/serverless/elasticsearch/ingest-data-through-logstash" section="migrating-elasticsearch-data-using-logstash">use Logstash</DocLink> to move data to and from serverless projects.
 - Custom roles 
 - Audit logging
 - Elasticsearch for Apache Hadoop

serverless/pages/what-is-serverless.mdx

@@ -64,6 +64,14 @@ There is no official SLA for Support in Serverless until General Availability (G
 
 Migration paths between hosted deployments and serverless projects are currently unsupported.
 
+**How can I move data to or from serverless projects?**
+
+We are working on data migration tools! In the interim, you can <DocLink slug="/serverless/elasticsearch/ingest-data-through-logstash" section="migrating-elasticsearch-data-using-logstash">use Logstash</DocLink> with Elasticsearch input and output plugins to move data to and from serverless projects. 
+
+**How can I move data to or from serverless projects?**
+
+We are working on data migration tools! In the interim, you can <DocLink slug="/serverless/elasticsearch/ingest-data-through-logstash" section="migrating-elasticsearch-data-using-logstash">use Logstash</DocLink> with Elasticsearch input and output plugins to move data to and from serverless projects. 
+
 **How does serverless ensure compatibility between software versions?**
 
 Connections and configurations are unaffected by upgrades. To ensure compatibility between software versions, quality testing and API versioning are used.
@@ -82,6 +90,10 @@ Create API keys for service accounts in your serverless projects. Options to aut
 
 To raise a Support case with Elastic, raise a case for your subscription the same way you do today. In the body of the case, make sure to mention you are working in serverless to ensure we can provide the appropriate support.
 
-**When will pricing information be available for serverless?**
+**Where can I learn about pricing for serverless?**
+
+See serverless pricing information for [Search](https://www.elastic.co/pricing/serverless-search), [Observability](https://www.elastic.co/pricing/serverless-observability), and [Security](https://www.elastic.co/pricing/serverless-security).
+
+**Can I request backups or restores for my projects?**
 
-Pricing will be available through account representatives and published at a later date.
+It is not currently possible to request backups or restores for projects, but we are working on data migration tools to better support this.