Merge branch 'master' into functions-rewrite

Author: sanscontext

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2020-07-06 
+# destination categories last updated 2020-07-09 
 items:
 - display_name: Email Marketing
   slug: email-marketing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2020-07-06 
+# source cateogries last updated 2020-07-09 
 items:
 - display_name: Server
   slug: server

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# sources last updated 2020-07-06 
+# sources last updated 2020-07-09 
 items:
 - display_name: .NET
   slug: net

src/_data/catalog/sources.yml

@@ -42,7 +42,7 @@ Computed trait: |
   [Computed traits](/docs/personas/computed-traits/) are per-user, or per-account [traits](#traits) that you create or “compute” in [Personas](/docs/personas/). When you build a Computed Trait, Personas adds it to relevant user profiles.
 
 Custom trait: |
-  [Custom Traits](/docs/personas/#custom-traits) are user or account properties collected from all the events you send to Personas.  For example, you can add any properties that you send as a part of your track calls or identify calls (`email`, `first_name`, `last_name`) as custom traits. You can then view them in the profile explorer, and use them in your audiences, computed traits and SQL traits.
+  [Custom Traits](/docs/personas/audiences/#custom-traits) are user or account properties collected from all the events you send to Personas.  For example, you can add any properties that you send as a part of your track calls or identify calls (`email`, `first_name`, `last_name`) as custom traits. You can then view them in the profile explorer, and use them in your audiences, computed traits and SQL traits.
 
 Debugger: |
   This is the place in the app where you can see your events flowing through Segment
@@ -84,7 +84,7 @@ Method: |
   A method is programming speak for "an action an object can take". It's a specific type of function that is attached to an object. All of our analytics tracking libraries create `analytics` objects, and then `track`, `identify`, `page`, [etc](/docs/connections/spec/) are methods you can invoke on those objects.
 
 MTU: |
-  Monthly Tracked Users. You can find more about how they are calculated [here](https://segment.com/docs/guides/usage-and-billing/how-are-mtus-calculated-by-segment/) but in short, they are calculated by adding the number unique userIds and number of unique anonymousIds that a customer tracks with Segment.
+  Monthly Tracked Users. You can find more about how they are calculated [here](https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/#how-does-segment-calculate-mtus) but in short, they are calculated by adding the number unique userIds and number of unique anonymousIds that a customer tracks with Segment.
 
 Object: |
   An object is a type of data that persists over time and can be updated, for example a Business or a User record. Objects have "traits" which record information about that object, and which can change over time. For example a "user" object could have a trait of "email" which doesn't change often, but could also have a [computed trait](#computed-trait) like `logged_in_last_7_days`. (Objects are in contrast to "[events](#event)" which happen at a single moment in time, and whose properties do not change.)

src/_data/glossary.yml

@@ -2,7 +2,7 @@
 
 Many times this is a limitation on the tool's detection process, where the detector is looking for a specific HTML element on your page. Our client side analytics.js library asynchronously loads the tool's library or pixel onto the page. As such, the detection fails.
 
-In order to confirm that the tool's library or pixel is actually loaded onto the page, you can open up the [javascript console](/docs/connections/sources/catalog/libraries/website/javascript#how-do-i-open-the-javascript-console-in-your-debugger-) and go to the network tab when the page is loading.
+In order to confirm that the tool's library or pixel is actually loaded onto the page, you can open up the [javascript console](/docs/connections/sources/catalog/libraries/website/javascript#how-do-i-open-the-javascript-console-in-your-debugger) and go to the network tab when the page is loading.
 
 ![Checking network tab to see if script loads](https://i.imgur.com/FdILEbO.gif)
 

src/_includes/content/client-side-script-unverified.md

@@ -1,3 +1,3 @@
 ### More About Identify
 
-To learn more about how `identify` works, check out our [Identify docs](/docs/connections/spec/identify). For example, `email` and `name` are two of our [special traits](/docs/connections/spec/identify#special-traits) that we recognize semantically.
+To learn more about how `identify` works, check out our [Identify docs](/docs/connections/spec/identify). For example, `email` and `name` are two of our [special traits](/docs/connections/spec/identify/#traits) that we recognize semantically.

src/_includes/content/integrations-identify.md

@@ -1,4 +1,4 @@
-The most basic Segment message requires only a `userID` or `anonymousID`; all other fields are optional to allow for maximum flexibility. However, a normal Segment message has three main parts: the [common fields](/docs/spec/common/), the ["context" object](/docs/spec/common#context), and the properties (if it's an event) or traits (if it's an object).
+The most basic Segment message requires only a `userID` or `anonymousID`; all other fields are optional to allow for maximum flexibility. However, a normal Segment message has three main parts: the [common fields](/docs/connections/spec/common/), the ["context" object](/docs/connections/spec/common#context), and the properties (if it's an event) or traits (if it's an object).
 
 The common fields include information specific to how the call was generated, like the timestamp and library name and version. The fields in the context object are usually generated by the library, and include information about the environment in which the call was generated: page path, user agent, OS, locale settings, etc. The properties and traits are optional and are where you customize the information you want to collect for your implementation.
 

src/_includes/content/message-anatomy.md

@@ -1,5 +1,5 @@
 ### No events in my debugger
 
-1. Double check that you've followed all the steps in the [Quickstart](quickstart/#getting-started).
+1. Double check that you've followed all the steps in the [Quickstart](quickstart/).
 
 2. Make sure that you're calling one of our API methods once the library is successfully installed—[`identify`](#identify), [`track`](#track), etc.

src/_includes/content/troubleshooting-server-debugger.md

@@ -36,8 +36,8 @@ You can use our [webhooks destination](/docs/connections/destinations/catalog/we
 
 #### Iron.io
 
-Another one of our destinations is [Iron.io](/docs/connections/destinations/catalog/iron.io/). They function similar to webhooks, but they will manage the message queue and allow you to run scripts on your data before routing it to another end point. Again this is similar to what Segment does for our business customers, but will require a decent amount of work from your team, however it will be much more reliable if your event volume gets high.
+Another one of our destinations is [Iron.io](/docs/connections/destinations/catalog/iron-io/). They function similar to webhooks, but they will manage the message queue and allow you to run scripts on your data before routing it to another end point. Again this is similar to what Segment does for our business customers, but will require a decent amount of work from your team, however it will be much more reliable if your event volume gets high.
 
 #### 3rd Party Reporting APIs
 
-This option is the most restrictive but might be the easiest if you need only basic basic data to be exported. A few examples would be to use the reporting APIs [Clicky](/docs/connections/destinations/catalog/clicky) or [Google Analytics](/docs/connections/destinations/catalog/google-analytics) provide (after turning those tools on in Segment and sending them data). Those APIs aren't super flexible and you won't see all the data from Segment, but for basic metrics they should work. One tool that's a bit more flexible when it comes to a reporting API is [Keen.io](/docs/connections/destinations/catalog/keen-io), which is also available on the Segment platform.
+This option is the most restrictive but might be the easiest if you need only basic basic data to be exported. A few examples would be to use the reporting APIs [Clicky](/docs/connections/destinations/catalog/clicky) or [Google Analytics](/docs/connections/destinations/catalog/google-analytics) provide (after turning those tools on in Segment and sending them data). Those APIs aren't super flexible and you won't see all the data from Segment, but for basic metrics they should work. One tool that's a bit more flexible when it comes to a reporting API is [Keen.io](/docs/connections/destinations/catalog/keen/), which is also available on the Segment platform.