chore: remove engage section, just use the one from the footer

Author: carlota-moh

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
@@ -480,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"