Merge branch 'master' into pwseg-patch-1

Author: markzegarelli

src/_sass/components/_markdown.scss

@@ -293,7 +293,7 @@
 
 }
 
-a[target="_blank"]:after{
+a[target="_blank"]:after:not(.reference-button){
   content: url("/docs/images/external-link-alt-solid.svg");
   margin-left: 4px;
 }

src/connections/sources/catalog/libraries/server/net/index.md

@@ -355,7 +355,7 @@ If you're running a web server, you might want to send [context variables](https
 Analytics.Client.Page("019mr8mf4r", "Login", new Properties() {
     { "path", "/login" },
     { "title", "Initech Login" }
-}), new Options()
+}, new Options()
     .SetContext (new Context () {
         { "userAgent", "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"},
         { "ip", "12.212.12.49" },
@@ -364,7 +364,7 @@ Analytics.Client.Page("019mr8mf4r", "Login", new Properties() {
           { "clientId", User.ClientId }
           }
         }
-});
+}));
 ```
 
 ## Anonymous ID

src/connections/sources/catalog/libraries/website/shopify-littledata/index.md

@@ -41,6 +41,8 @@ Here's an architecture diagram that shows how the Littledata app mediates data f
 
 Below is a table of events that **Shopify by Littledata** sends to Segment through the analytics.js library. These events will show up as tables in your warehouse, and as regular events in your other Destinations supporting device-mode.
 
+You can _opt out_ of device-mode pageviews or events by setting `disableClientSideEvents: true` or `disablePageviews: true` in the `LittledataLayer` settings.
+
 | Event Name            | Description                                                         |
 | --------------------- | ------------------------------------------------------------------- |
 | Cart Viewed           | A user has viewed the /cart page                                    |
@@ -55,7 +57,7 @@ Below is a table of events that **Shopify by Littledata** sends to Segment throu
 | Thank you Page Viewed | A user has viewed the thank you page after completing an order\*    |
 
 > note ""
-> *This is less reliable than the de-duplicated `Order Completed` event sent from the Littledata servers, but you can use it in device-mode destinations to trigger a conversion. The `payment_method` and `shipping_method` properties are not available with this event.
+> \*This is less reliable than the de-duplicated `Order Completed` event sent from the Littledata servers, but you can use it in device-mode destinations to trigger a conversion. The `payment_method` and `shipping_method` properties are not available with this event.
 
 ## Cloud-mode events
 
@@ -98,6 +100,7 @@ The following traits are included with an Identify call:
 
 | Property Name                | Description                                                                                                                | Property Type |
 | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------- |
+| `accepts_marketing`          | Whether the customer has accepted marketing                                                                                | Boolean       |
 | `createdAt`                  | The date customer record was created                                                                                       | Date          |
 | `customerLifetimeValue`      | The total spend of customer on the Shopify store                                                                           | Double        |
 | `default_address.street`     | The customer's default street address                                                                                      | String        |
@@ -177,7 +180,7 @@ The list below outlines the properties included in the events listed above.
 | `userId`                               | Chosen user identifier, defaulting to Shopify Customer ID                                          | String        |
 
 > note ""
-> *`revenue` is available only with the Order Completed event, and only if the store opts in via the Littledata application. Revenue is a reserved property in many Segment destinations. Opting in will override the `total` property sent to Google Analytics.
+> \*`revenue` is available only with the Order Completed event, and only if the store opts in via the Littledata application. Revenue is a reserved property in many Segment destinations. Opting in will override the `total` property sent to Google Analytics.
 
 ## Product properties
 

src/connections/storage/warehouses/index.md

@@ -10,13 +10,13 @@ redirect_from: '/connections/warehouses/'
 {% include content/whats-a-warehouse.md %}
 
 
-When selecting and building a data warehouse, there are three questions to consider:
+When selecting and building a data warehouse, consider three questions:
 
 1.  What type of data will be collected?
 2.  How many data sources will there be?
 3.  How will the data be used?
 
-Relational databases are great when you know and predefine the information collected and how it will be linked. This is usually the type of database used in the world of user analytics. For instance, a users table might be populated with the columns "name", "email address", "plan name", etc.
+Relational databases are great when you know and predefine the information collected and how it will be linked. This is usually the type of database used in the world of user analytics. For instance, a users table might be populated with the columns `name`, `email_address`, or `plan_name`.
 
 Examples of data warehouses include Amazon Redshift, Google BigQuery, and Postgres.