Merge pull request #86 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/destinations/catalog/actions-amplitude/index.md

@@ -170,6 +170,9 @@ When you send an "Order Completed" event from Segment, an "Order Completed" even
 
 #### Track Revenue Per Product
 
+> info ""
+> If you use Track Revenue Per Product, add a `revenue` property inside the `products` array of the Order Completed event.
+
 Amplitude has two different ways to track revenue associated with a multi-product purchase. You can choose which method you want to use using the **Track Revenue Per Product** destination setting.
 
 If you disable the setting ("off"), Segment sends a single revenue event with the total amount purchased and adds revenue data the Amplitude "Order Completed" event. The "Product Purchased" events do not contain any native Amplitude revenue data.

src/connections/storage/catalog/amazon-s3/index.md

@@ -166,6 +166,9 @@ Segment recommends doing this as a best practice. The following policy strictly
 
 ## Region
 
+> warning ""
+> The Amazon S3 destination only supports workspaces in the US region. Workspaces outside of the US can't connect to this destination. If you wish to connect to a different region use Segment's new [AWS S3 destination](https://segment.com/docs/connections/storage/catalog/aws-s3/) instead.
+
 Segment infers the region of your bucket when data is copied to it, so you don't need to specify a bucket region in your configuration. If you're using VPC Endpoints for your S3 bucket, make sure you configure the endpoint in the same region as your bucket. You can find more information on this in the AWS S3 docs [here](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-endpoints-s3.html).
 
 ## Custom Path Prefix