Merge pull request #2643 from segmentio/tlalfano-patch-1

Updating migration guide

Author: stayseesong

src/_redirects

@@ -1,2 +1,2 @@
-/docs/* /:splat 200
-/docs/assets/docs.bundle.js /assets/docs.bundle.js 200
+/docs/* /:splat 301
+/docs/assets/docs.bundle.js /assets/docs.bundle.js 301

src/connections/destinations/catalog/tiktok-conversions/index.md

@@ -8,8 +8,6 @@ id: 615cae349d109d6b7496a131
 
 The TikTok Conversions destination is a server-to-server integration with the TikTok Events API that allows advertisers to share website visitor events from Segment directly to TikTok. Data shared through the Events API is processed similarly to information shared through the TikTok pixel and TikTok SDK business tools. Advertisers can use events data to power solutions like dynamic showcase ads (DSA), custom targeting, campaign optimization and attribution. Advertisers can see their event data in TikTok Events Manager.
 
-The TikTok Conversions destination is owned and maintained by the TikTok team.
-
 ## Benefits of TikTok Conversions
 The TikTok Conversions destination provides the following benefits:
 
@@ -78,5 +76,7 @@ You can check whether the integration is working, test events in real-time, and
 
 ## Support
 
+The TikTok Conversions destination is owned and maintained by the TikTok team.
+
 - For general Segment questions, including issues with event data not being sent to TikTok Events Manager, please contact [Segment support](https://segment.com/help/){:target="_blank"}.
 - For questions regarding campaign setup and performance, web tracking, or additional API functionality, please contact your TikTok representative.

src/connections/sources/catalog/libraries/mobile/react-native/migration.md

@@ -9,7 +9,7 @@ To migrate to React Native 2.0:
 
 1. Update the existing package:
     ```js
-    yarn upgrade @segment/analytics-react-native@2.2.0
+    yarn upgrade @segment/analytics-react-native
     ```
 2. Install additional dependencies:
     ```js
@@ -88,7 +88,7 @@ PODS:
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-### Example client configuration for `analytics-react-native 2.2.0`
+### Example client configuration for `analytics-react-native 2.0`
 
 {% codeexample %}
 {% codeexampletab App.tsx (or .js) %}
@@ -126,7 +126,7 @@ const App = () => {
  "nanoid": "^3.1.30",
  "@react-native-async-storage/async-storage": "^1.15.11",
  "@segment/analytics-react-native": "2.2.0",
- "@segment/analytics-react-native-plugin-firebase": "2.2.0",
+ "@segment/analytics-react-native-plugin-firebase": "2.0",
  "@segment/sovran-react-native": "0.2.6",
 }
 ```
@@ -165,7 +165,7 @@ onSendEvent = async() => {
 }
 ```
 
-### Example tracking implementation for `analytics-react-native 2.2.0`
+### Example tracking implementation for `analytics-react-native 2.0`
 Home.tsx
 
 ```js

src/connections/storage/warehouses/redshift-useful-sql.md

@@ -8,12 +8,19 @@ Below you'll find a library of some of the most useful SQL queries customers use
 
 You can use SQL queries for the following tasks:
 - [Tracking events](#tracking-events)
-- [Defining sessions](#defining-sessions)
-- [Identifying users](#identifying-users)
+  - [Grouping events by day](#grouping-events-by-day)
+- [Define sessions](#define-sessions)
+  - [How to define user sessions using SQL](#how-to-define-user-sessions-using-sql)
+- [Identify users](#identify-users)
+  - [Historical traits](#historical-traits)
+  - [Convert the identifies table into a users table](#convert-the-identifies-table-into-a-users-table)
+  - [Counts of user traits](#counts-of-user-traits)
 - [Groups to accounts](#groups-to-accounts)
+  - [Historical Traits](#historical-traits-1)
+  - [Converting the Groups Table into an Organizations Table](#converting-the-groups-table-into-an-organizations-table)
 
 > note " "
-> If you're looking for SQL queries for warehouses other than Redshift, check out some of Segment's [Analyzing with SQL guides](/docs/connections/storage/warehouses/index/#analyzing-with-sql).
+> If you're looking for SQL queries for warehouses other than Redshift, check out some of Segment's [Analyzing with SQL guides](/docs/connections/storage/warehouses#analyzing-with-sql).
 
 ## Tracking events
 

src/protocols/apis-and-extensions/index.md

@@ -4,18 +4,19 @@ title: 'Protocols: APIs and Extensions'
 
 {% include content/plan-grid.md name="protocols" %}
 
+Built from the ground up, Protocols addresses a wide range of customer needs.
 
-Protocols was developed from the ground up to support a wide range of customer needs. Whether you're interested in helping your engineers reduce tracking errors, or want to get notified when an issue arises, or want to use a Tracking Plan you already have, we have a suite of features and API support to get it done. We've captured many of those resources below.
+With Protocols, you can help engineers reduce tracking errors, create issue notifications, and get the most out of your Tracking Plan. Below, learn about several Protocols resources that can help you address these and other common use cases.
 
 ## Anomaly detection
 
-If you’re using Protocols, you might want to get notifications when an anomaly in event volumes or Protocols violation counts occurs. [This document](/docs/protocols/apis-and-extensions/anomaly_detection/) clarifies what we mean by anomaly detection, gives examples of anomalies that might be relevant to your business, and provides some example solutions of how to monitor and alert on anomalies using some standard tools available today.
-
-[Read more about Anomaly Detection here](/docs/protocols/apis-and-extensions/anomaly_detection/)
+If you’re using Protocols, you might want to get notifications when event volume anomalies or Protocols violation counts occur. Read Segment's [anomaly detection documentation](/docs/protocols/apis-and-extensions/anomaly_detection/) to learn about common anomalies, as well as monitoring and alerting solutions you can implement using standard tools.
 
 ## Config API
 
-Protocols customers get access to the Segment Config API, which enables programmatic creation, configuration, and fetching of core Segment platform resources such as Sources, Destinations, and now Tracking Plans. The Config API represents Segment's commitment to developers, enabling customers to extend their workflows around customer data collection and activation. The Config API will be generally available to customers in coming months and will be evolving with more features throughout next year.
+Protocols customers can access [Segment's Config API](/docs/config-api/), which enables programmatic creation, configuration, and fetching of core Segment platform resources like Sources, Destinations, and Tracking Plans.
+
+The Config API represents Segment's commitment to developers, helping you extend your workflow around customer data collection and activation.
 
 ### Supported Operations
 
@@ -25,22 +26,10 @@ Protocols customers get access to the Segment Config API, which enables programm
 - **Update Tracking Plan**
 - **Delete Tracking Plan**
 
-[Learn more about the Config API here](https://segment.com/docs/config-api/)
-
 ## Typewriter
 
-Typewriter is a tool for generating strongly-typed Segment analytics libraries based on your pre-defined Tracking Plan spec. [Head over to the docs](/docs/protocols/apis-and-extensions/typewriter/) to get started with Typewriter.
-
-## Google Sheets Tracking Plan Uploader
-
-Thousands of Segment customers have used Google Sheets to build Tracking Plans. We created the following template to help you draft a Tracking Plan and easily upload that Tracking Plan to Segment. Keep in mind that uploading changes from Google Sheets will overwrite any changes made in the Segment UI.
-
-[View the Google Sheets Tracking Plan template here](https://docs.google.com/spreadsheets/u/1/d/1TA6qTcDHoZzsG7-C6p5yHGximDxqoNtizguKs7Z0av4/copy). Feel free to make a copy!
-
-To upload your Tracking Plan directly from Google Sheets, follow these steps:
+Typewriter is a tool for generating strongly-typed Segment analytics libraries based on your pre-defined Tracking Plan spec. View Segment's [Typewriter documentation](/docs/protocols/apis-and-extensions/typewriter/) to get started.
 
-1. Generate a Personal Access Token following the steps [here](/docs/config-api/authentication/)
-2. Copy your Personal Access Token, your Workspace's slug and your tracking plan's `rs_` id (found in the URL path of your Tracking Plan) to the Importer Settings worksheet. Then click on the Segment > Send to Segment menu item to upload your Tracking Plan to Segment.
 
 <!--
 Removed on 3/18/2020 per PROT-2279