Merge branch 'master' into DOC-48_priv-and-stripe-updates

Author: markzegarelli

src/_sass/components/_markdown.scss

@@ -233,6 +233,7 @@
 
       &:first-of-type {
         padding-left: 5px;
+        min-width: 150px;
       }
 
       &:last-of-type {

src/connections/destinations/catalog/repeater/index.md

@@ -6,22 +6,20 @@ This destination is maintained by Segment.
 
 ## Getting Started
 
-The Repeater destination forwards events from a source back into another source, as though that event occured in the second source.
+The Repeater destination forwards events from a source back into another source, as though that event occurred in the second source.
 
-Events are not cached in the Repeater, so it only handles real-time events. You can specify multiple sources as Repeater destinatons.
-
-*Segment does not double count MTUs for Repeater events.*
+Events are not cached in the Repeater, so it only handles real-time events. You can specify multiple sources as Repeater destinations.
 
 ## Configuration
 
-Add the Repeater as a destination for the source that you would like to replicate events from.
+Add the Repeater as a destination for the source that you want to replicate events from.
 
-Find the source that you would like events to flow to, and copy the write key from that source.
+Find the source that you want events to flow to, and copy the `writeKey` from that source.
 
-Go back to the Repeater destination and add this write key to the write keys list for Repeater.
+Go back to the Repeater destination's settings, and add this `writeKey` to the write keys list for Repeater.
 
 You can do this for as many sources as you need.
 
 ![](images/write-key-settings.png)
 
-Repeater will replay all events it gets to the sources you specified using the write key(s) you specified.
+Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.

src/connections/sources/about-cloud-sources.md

@@ -28,9 +28,11 @@ Sources are functionally comprised of either one or both of the following compon
 
 ### Sync frequency
 
-When you enable a source and grant us access by pasting an API key or authenticating with OAuth, Segment starts a scheduled job on your behalf which makes requests to the downstream tool, normalizes and transforms the data, and forwards the data to the Segment API. We make an effort to use as few API calls as possible, opting to fetch only data that has changed since the previous sync where possible. This can be an intensive process, especially on first sync, so we have lots of affordances in place for retries and to respect rate limits imposed by the partner.
+You enable a cloud source from the Segment web app, and grant Segment access by pasting an API key or authenticating with OAuth. Segment then starts a scheduled job on your behalf which makes requests to the downstream tool, normalizes and transforms the data, and forwards that data to the Segment API.
 
-### API Call Usage and Collection Selection
+Cloud sources attempt to use as few API calls as possible, and (where possible) only fetch data that changed since the last sync. The syncs might take a long time (especially on the first sync), so the cloud source syncs have robust retry and rate limiting logic.
+
+### API call use and collection selection
 
 We make an effort to be respectful of your API call allotments and limits. For example, in the case of Salesforce, we issue only one query per collection per run, using the absolute minimum number of API calls possible (typically about 350/day).
 
@@ -83,7 +85,7 @@ Sometimes, when the sync job fails due to an unhandled error or is mysteriously
 
 In general, we've focused on pulling all of the collections directly related to the customer experience. We do not automatically pull all collections available from a partner API, since many of them aren't relevant to the customer journey. You can see a list of the collections we pull in the docs [for each cloud source](/docs/connections/sources/catalog/#cloud-apps). Each collection reflects a table in your database.
 
-[Let us know](https://segment.com/help/contact) if you need additional data collected or to change the schema to do the analysis you want. We'd love to know what analysis you're trying to run, what additional data you need, and we'll share with the product team to evaluate.
+[Contact Segment Product Support](https://segment.com/help/contact) if you need additional data collected, or to change the schema to do the analysis you want. We'd love to know what analysis you're trying to run, what additional data you need, and we'll share with the product team to evaluate.
 
 ### What questions can you answer with data from cloud, web, and mobile sources combined in a single warehouse?
 

src/connections/sources/catalog/cloud-apps/shopify-littledata/index.md

@@ -1,6 +1,7 @@
 ---
 title: Shopify by Littledata Source
 source-type: event
+published: false
 ---
 
 Littledata is a smart analytics app that automates ecommerce tracking. Littledata's [Shopify-to-Segment connection](https://www.littledata.io/connections/segment/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) automatically tracks key ecommerce events on a Shopify or Shopify Plus store, so you can use Shopify as a source in your Segment workspace.