clarfiy (#30943)

Author: maycmlee

content/en/observability_pipelines/destinations/amazon_s3.md

@@ -3,13 +3,13 @@ title: Amazon S3 Destination
 disable_toc: false
 ---
 
-Use the Amazon S3 destination to send logs to Amazon S3. If you want to send logs in Datadog-rehydratable format to Amazon S3 for [archiving][1] and [rehydration][2], you must [configure Log Archives](#configure-log-archives). If you want to send your logs directly to Amazon S3, without converting them to Datadog-rehydratable format, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
+Use the Amazon S3 destination to send logs to Amazon S3. If you want to send logs to Amazon S3 for [archiving][1] and [rehydration][2], you must [configure Log Archives](#configure-log-archives). If you don't want to rehydrate your logs in Datadog, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
 
 You can also [route logs to Snowflake using the Amazon S3 destination](#route-logs-to-snowflake-using-the-amazon-s3-destination).
 
 ## Configure Log Archives
 
-This step is only required if you want to send logs to Amazon S3 in Datadog-rehydratable format for [archiving][1] and [rehydration][2], and you don't already have a Datadog Log Archive configured for Observability Pipelines. If you already have a Datadog Log Archive configured or only want to send your logs directly to Amazon S3, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
+This step is only required if you want to send logs to Amazon S3 for [archiving][1] and [rehydration][2], and you don't already have a Datadog Log Archive configured for Observability Pipelines. If you already have a Datadog Log Archive configured or don't want to rehydrate logs in Datadog, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
 
 You need to have Datadog's [AWS integration][3] installed to set up Datadog Log Archives.
 

content/en/observability_pipelines/destinations/azure_storage.md

@@ -3,11 +3,11 @@ title: Azure Storage Destination
 disable_toc: false
 ---
 
-Use the Azure Storage destination to send logs to an Azure Storage bucket. If you want to send logs in Datadog-rehydratable format to Azure Storage for [archiving][1] and [rehydration][2], you must [configure Log Archives](#configure-log-archives). If you want to send your logs directly to Azure Storage, without converting them to Datadog-rehydratable format, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
+Use the Azure Storage destination to send logs to an Azure Storage bucket. If you want to send logs to Azure Storage for [archiving][1] and [rehydration][2], you must [configure Log Archives](#configure-log-archives). If you don't want to rehydrate logs in Datadog, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
 
 ## Configure Log Archives
 
-This step is only required if you want to send logs to Azure Storage in Datadog-rehydratable format for [archiving][1] and [rehydration][2], and you don't already have a Datadog Log Archive configured for Observability Pipelines. If you already have a Datadog Log Archive configured or only want to send your logs directly to Azure Storage, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
+This step is only required if you want to send logs to Azure Storage in Datadog-rehydratable format for [archiving][1] and [rehydration][2], and you don't already have a Datadog Log Archive configured for Observability Pipelines. If you already have a Datadog Log Archive configured or don't want to rehydrate logs in Datadog, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).
 
 You need to have Datadog's [Azure integration][3] installed to set up Datadog Log Archives.
 

content/en/observability_pipelines/destinations/google_cloud_storage.md

@@ -5,13 +5,13 @@ disable_toc: false
 
 <div class="alert alert-warning">For Worker versions 2.7 and later, the Google Cloud destination supports <a href = "https://cloud.google.com/storage/docs/uniform-bucket-level-access">uniform bucket-level access</a>. Google <a href = "https://cloud.google.com/storage/docs/uniform-bucket-level-access#should-you-use">recommends</a> using uniform bucket-level access. <br>For Worker version older than 2.7, only <a href = "https://cloud.google.com/storage/docs/access-control/lists">Access Control Lists</a> is supported.</div>
 
-Use the Google Cloud Storage destination to send your logs to a Google Cloud Storage bucket. If you want to send logs in Datadog-rehydratable format to Google Cloud Storage for [archiving][1] and [rehydration][2], you must [configure Log Archives](#configure-log-archives). If you want to send your logs directly to Google Cloud Storage, without converting them to Datadog-rehydratable format, skip to [Set up the destination for your pipeline](#set-up-the-destinations).
+Use the Google Cloud Storage destination to send your logs to a Google Cloud Storage bucket. If you want to send logs to Google Cloud Storage for [archiving][1] and [rehydration][2], you must [configure Log Archives](#configure-log-archives). If you do not want to rehydrate logs in Datadog, skip to [Set up the destination for your pipeline](#set-up-the-destinations).
 
 The Observability Pipelines Worker uses standard Google authentication methods. See [Authentication methods at Google][6] for more information about choosing the authentication method for your use case.
 
 ## Configure Log Archives
 
-This step is only required if you want to send logs to Google Cloud Storage in Datadog-rehydratable format for [archiving][1] and [rehydration][2], and you don't already have a Datadog Log Archive configured for Observability Pipelines. If you already have a Datadog Log Archive configured or only want to send your logs directly to Google Cloud Storage, skip to [Set up the destination for your pipeline](#set-up-the-destinations).
+This step is only required if you want to send logs to Google Cloud Storage for [archiving][1] and [rehydration][2], and you don't already have a Datadog Log Archive configured for Observability Pipelines. If you already have a Datadog Log Archive configured or do not want to rehydrate your logs in Datadog, skip to [Set up the destination for your pipeline](#set-up-the-destinations).
 
 If you already have a Datadog Log Archive configured for Observability Pipelines, skip to [Set up the destination for your pipeline](#set-up-the-destination-for-your-pipeline).