Merge remote-tracking branch 'upstream/develop' into develop

Author: lopenchi

src/connections/destinations/add-destination.md

@@ -52,7 +52,7 @@ You can also add a destination directly from the source's settings page in the S
 
 #### Adding a destination using the Public API
 
-You can use the Segment Public API to add destinations to your workspace using the [Create Destination endpoint](https://docs.segmentapis.com/tag/Destinations#operation/createDestination){:target = "_blank"}. The API requires an authorization token, and uses the `name` field as a namespace that defines which _source_ the destination is connected to. You send the rest of the destination's configuration as a JSON blob. View the documentation page in the Segment Catalog, or query the [Segment Catalog API](https://docs.segmentapis.com/tag/Catalog){:target="_blank"}, for a destination to see the available settings.
+You can use the Segment Public API to add destinations to your workspace using the [Create Destination endpoint](https://docs.segmentapis.com/tag/Destinations#operation/createDestination){:target="_blank"}. The API requires an authorization token, and uses the `name` field as a namespace that defines which _source_ the destination is connected to. You send the rest of the destination's configuration as a JSON blob. View the documentation page in the Segment Catalog, or query the [Segment Catalog API](https://docs.segmentapis.com/tag/Catalog){:target="_blank"}, for a destination to see the available settings.
 
 > success ""
 > You must use an authorization token to access the Public API, and these tokens are tied to specific workspaces. If you use the Public API to access multiple workspaces, make sure you're using the token for the workspace you want to access before proceeding.
@@ -112,7 +112,7 @@ Multi-instance support is not available for most hybrid Actions destinations or
 
 Segment does not support connecting a single source to multiple instances of a [Data Lakes](/docs/connections/storage/data-lakes/) destination.
 
-> warning "Non-mobile sources can only connect to _one_ device-mode instance of a destination"
+> warning "Non-mobile sources can only connect to one device-mode instance of a destination"
 > You cannot connect a source to more than one instance of a destination that operates only in device-mode. For more information about device-mode restrictions, see the [Sending Segment data to Destinations](/docs/connections/destinations/add-destination/#connecting-one-source-to-multiple-instances-of-a-destination:~:text=Multi%2Dinstance%20destinations-,and,-Device%2Dmode) documentation.
 
 > success ""

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

@@ -14,7 +14,7 @@ To configure CommandBar as an Event Source to get data into your warehouse or ot
 1. From the Segment web app, navigate to **Connections > Catalog**, then select the **Destinations** tab at the top of the catalog.
 2. Search for *CommandBar* and select it.
 3. Click **Configure CommandBar**.
-4. Sign in to [CommandBar](app.commandbar.com/login){:target="_blank"}, click on your organization name in the top right, and copy the `Org ID` into **Organization ID** field.
+4. Sign in to [CommandBar](https://app.commandbar.com/login){:target="_blank"}, click on your organization name in the top right, and copy the `Org ID` into **Organization ID** field.
 5. If you want to deploy CommandBar to your users through Segment, check **Deploy via Segment**.
 6. Select an existing Source to connect to CommandBar.
 7. Once connected, remove the CommandBar snippet or `init` call from your code (if you have one).

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

@@ -12,7 +12,7 @@ This destination is maintained by Plotline. For any issues with the destination,
 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Plotline".
 2. Select and click **Add Destination**.
 3. Select an existing source to connect to.
-4. Go to [Plotline's dashboard](app.plotline.so){:target="_blank”}, navigate to "Credentials" and copy the API key.
+4. Go to [Plotline's dashboard](https://app.plotline.so){:target="_blank”}, navigate to "Credentials" and copy the API key.
 5. Enter the API Key in the destination settings in Segment.
 
 ## Supported methods

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

@@ -33,7 +33,7 @@ It takes only three steps to set everything up and start surveying your audience
 ### 3. Map survey campaign with Segment events
 
 1. In the Retently destination settings in the Segment app, go to the **Map Retently campaigns with Segment events** section.
-2. In the left input field, enter the ID of the survey campaign. [Learn how to configure the survey campaign.](hhttps://help.retently.com/en/articles/8217913-trigger-transactional-surveys-via-segment-events){:target="_blank"}
+2. In the left input field, enter the ID of the survey campaign. [Learn how to configure the survey campaign.](https://help.retently.com/en/articles/8217913-trigger-transactional-surveys-via-segment-events){:target="_blank"}
 3. In the right field, list the name of one or more Segment Track events that should trigger the survey in the specified campaign.
    Write the name of the event exactly as it's written in the `analytics.track` method (more details in the section below). You can enter multiple Track events by separating them with a comma symbol (for example Order Placed, Dashboard Visited).
 

src/connections/destinations/destination-filters.md

@@ -18,7 +18,7 @@ Common use cases for destination filters include:
 - Increasing data relevance in your destinations by removing unused or unwanted data
 - Preventing test or internally-generated events from reaching your production tools
 
-### Limitations
+## Limitations
 
 Keep the following limitations in mind when you use destination filters:
 

src/connections/functions/aws-apis.md

@@ -8,8 +8,8 @@ The [`aws-sdk`](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guid
 To set up your functions to call AWS APIs:
 1. Create an IAM role in your AWS account that your function will assume before making AWS API calls.
     1. Make sure you have these two values:
-      * **Principal account ID**: This is the ID number for the AWS account that your function runs in. For destination functions, this is `458175278816` and for source functions this is `300240842537`.
-      * **External ID**: This is the value your IAM role uses to ensure that only your functions have the ability to assume the role. Segment recommends you to choose a long string of at least 32 random characters and treat it as if it were an API key or a password.
+        * **Principal account ID**: This is the ID number for the AWS account that your function runs in. For destination functions, this is `458175278816` and for source functions this is `300240842537`.
+        * **External ID**: This is the value your IAM role uses to ensure that only your functions have the ability to assume the role. Segment recommends you to choose a long string of at least 32 random characters and treat it as if it were an API key or a password.
     2. Create an IAM role in your AWS account with the [minimum set of necessary permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege){:target="_blank"}.
     3. Add a trust relationship to your role with the following policy, filling in the principal account ID and external ID from step 1.1:
       ```json
@@ -33,11 +33,13 @@ To set up your functions to call AWS APIs:
       ```
 
 2. Create your function.
-  <br> Now that you have an IAM role in your AWS account, you can create your source or destination function. Segment recommends you to use function settings to make the IAM role configurable. This allows you to use different roles for different instances of your function and to securely store your external ID value by making it a "sensitive" setting. Here are the required settings:
-  * **IAM Role ARN**: A string setting that is the ARN for the IAM role above. For example, `arn:aws:iam::1234567890:role/my-secure-role`.
-  * **IAM Role External ID**: A sensitive string setting that is the external ID for your IAM role.
 
-    Below is an example destination function that uploads each event received to an S3 bucket (configured using additional "S3 Bucket" and "S3 Bucket Region" settings). It uses the built-in local cache to retain S3 clients between requests to minimize processing time and to allow different instances of the function to use different IAM roles.
+Now that you have an IAM role in your AWS account, you can create your source or destination function. Segment recommends you to use function settings to make the IAM role configurable. This allows you to use different roles for different instances of your function and to securely store your external ID value by making it a "sensitive" setting. Here are the required settings:
+
+* **IAM Role ARN**: A string setting that is the ARN for the IAM role above. For example, `arn:aws:iam::1234567890:role/my-secure-role`.
+* **IAM Role External ID**: A sensitive string setting that is the external ID for your IAM role.
+
+Below is an example destination function that uploads each event received to an S3 bucket (configured using additional "S3 Bucket" and "S3 Bucket Region" settings). It uses the built-in local cache to retain S3 clients between requests to minimize processing time and to allow different instances of the function to use different IAM roles.
 
     ```javascript
     async function getS3(settings) {

src/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup.md

@@ -61,11 +61,11 @@ To set up Db2 as your Reverse ETL source:
 4. Click **+ Add Reverse ETL source**.
 5. Select **Db2** and click **Add Source**.
 6. Fill in the following Db2 connection settings:
-  * Hostname: `<hostname>`
-  * Port: `<port>`
-  * Database: `<db_name>`
-  * Username: `<segment_db2_user>`
-  * Password: `<password>`
+    * Hostname: `<hostname>`
+    * Port: `<port>`
+    * Database: `<db_name>`
+    * Username: `<segment_db2_user>`
+    * Password: `<password>`
 7. Click **Test Connection** to validate the setup.
 8. If the connection is successful, click **Add source**.
 

src/connections/reverse-etl/setup.md

@@ -25,13 +25,13 @@ To add your warehouse as a source:
 2. Click **+ Add Reverse ETL source**.
 3. Select the source you want to add. 
 4. Follow the corresponding guide to set up the required permissions for your Reverse ETL source:
-  - [Azure Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup)
-  - [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup)
-  - [Databricks Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup)
-  - [Db2 Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup)
-  - [Postgres Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup)
-  - [Redshift Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup)
-  - [Snowflake Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup)
+    - [Azure Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup)
+    - [BigQuery Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup)
+    - [Databricks Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup)
+    - [Db2 Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/db2-setup)
+    - [Postgres Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup)
+    - [Redshift Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup)
+    - [Snowflake Reverse ETL setup guide](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup)
 
 ## Step 2: Add a model
 Models define sets of data you want to sync to your Reverse ETL destinations. A source can have multiple models. Segment supports [SQL models](/docs/connections/reverse-etl/setup/#step-4-create-mappings) and [dbt models](/docs/segment-app/extensions/dbt/).

src/connections/reverse-etl/system.md

@@ -31,7 +31,7 @@ The records table helps in determining new and updated rows by comparing the che
 
 ### Checkpoint table
 
-The `checkpoints_<subscription_id>` tables are located within the __segment_reverse_etl schema.
+The `checkpoints_<subscription_id>` tables are located within the `__segment_reverse_etl` schema.
 
 This table contains the following columns:
 

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

@@ -9,11 +9,11 @@ Cloud-App Sources (often shortened to Cloud Sources) allow you to pull in data f
 
 As in the basic tracking API, _objects_ usually contain information about a person or group which is updated over time, while _event_ data happens once, and is appended to a list.
 
-### Event Cloud-App Sources
+## Event Cloud-App Sources
 
 Event Cloud Sources can export their data both into Segment warehouses, and into other enabled Segment integrations that work with event data.
 
-### Object Cloud-App Sources
+## Object Cloud-App Sources
 
 Object Cloud App Sources can export data and import it directly into a Segment warehouse. You *must* have a Segment warehouse enabled before you enable these. From the warehouse, you can analyze your data with SQL, use [Reverse ETL](/docs/connections/reverse-etl) to extract data, or use Engage SQL Traits to build audiences. Some examples of Object Cloud sources are Salesforce (account information), Zendesk (support cases), and Stripe (payments information).