diff --git a/src/connections/storage/catalog/amazon-s3/index.md b/src/connections/storage/catalog/amazon-s3/index.md
index bad80cfdfa..6fd7c6e306 100644
--- a/src/connections/storage/catalog/amazon-s3/index.md
+++ b/src/connections/storage/catalog/amazon-s3/index.md
@@ -83,7 +83,9 @@ Segment stores logs as gzipped, newline-separated JSON containing the full call
 
 Segment groups logs by day, and names them using the following format:
 
-    s3://{bucket}/segment-logs/{source-id}/{received-day}/filename.gz
+```
+s3://{bucket}/segment-logs/{source-id}/{received-day}/filename.gz
+```
 
 The received-day refers to the UTC date unix timestamp, that the API receives the file, which makes it easy to find all calls received within a certain timeframe.
 
diff --git a/src/connections/storage/catalog/aws-s3/index.md b/src/connections/storage/catalog/aws-s3/index.md
index e79b16e872..df08fd9f4d 100644
--- a/src/connections/storage/catalog/aws-s3/index.md
+++ b/src/connections/storage/catalog/aws-s3/index.md
@@ -2,7 +2,6 @@
 title: AWS S3 with IAM Role Support Destination
 redirect_from:
   - '/connections/destinations/catalog/aws-s3/'
-hide-personas-partial: true
 ---
 
 ## Differences between the Amazon S3 destination and the AWS S3 destination
@@ -462,7 +461,9 @@ Segment stores logs as gzipped, newline-separated JSON containing the full call
 
 Segment groups logs by day, and names them using the following format:
 
-    s3://{bucket}/segment-logs/{source-id}/{received-day}/filename.gz
+```
+s3://{bucket}/segment-logs/{source-id}/{received-day}/filename.gz
+```
 
 The received-day refers to the UTC date Unix timestamp, that the API receives the file, which makes it easy to find all calls received within a certain timeframe.
 
@@ -478,18 +479,6 @@ To use a custom key prefix for the files in your bucket, append the path to the
 
 Amazon provides several methods to download data from an S3 bucket. For more information, see [Downloading an object](https://docs.aws.amazon.com/AmazonS3/latest/userguide/download-objects.html){:target="_blank"}.
 
-
-## Engage
-
-> warning ""
-> As mentioned above, the AWS S3 destination works differently than other destinations in Segment. As a result, Segment sends **all** data from a Engage source to S3 during the sync process, not only the connected audiences and traits.
-
-You can send computed traits and audiences generated using [Engage](/docs/engage) to this destination as a **user property**. 
-
-For user-property destinations, Segment sends an [identify](/docs/connections/spec/identify/) call to the destination for each user added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.
-
-When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs send updates for users whose membership has changed since the last sync.
-
 ## FAQ
 
 ### AWS S3 destination connection error “Multiple instance of AWS S3 are not allowed for this source"