Merge pull request #155 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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

@@ -6,15 +6,15 @@ redirect_from: '/connections/destinations/catalog/supervised-ai/'
 
 [DataBrain](https://usedatabrain.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) provides a proactive customer success tool for hyper-growth startups. DataBrain is fully data driven. It ingests data from Segment and leverage smachine learning techniques to send users automated alerts, and predict churn, conversion, retention or any event you need to track.
 
-This destination is maintained by DataBrain. For any issues with the destination, [contact the DataBrain Support team](mailto:support@supervisedai.com).
+This destination is maintained by DataBrain. For any issues with the destination, [contact the DataBrain Support team](mailto:support@usedatabrain.com).
 
 ## Getting Started
 
 {% include content/connection-modes.md %}
 
 1. From the Segment App's Destinations catalog page, click **Add Destination**.
 2. Search for "DataBrain" in the Destinations Catalog, and select the DataBrain destination.
-3. Go to your [DataBrain dashboard](https://usedatabrain.com/integrations), and copy your "API Key".
+3. Go to your [DataBrain dashboard](https://api.usedatabrain.com/integrations), and copy your "API Key".
 4. Back in the Segment app, paste the API key into the settings for the DataBrain destination.
 
 > info ""

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

@@ -33,7 +33,9 @@ By default, your `identify` calls will not be sent through to Slack unless you h
 ### Identify Template
 Once you've saved your whitelisted traits, you can now use them alongside [Handlebars expressions](http://handlebarsjs.com/expressions.html) syntax within a template. Make sure you reference the spec for the [Identify method](/docs/connections/spec/identify/) and [common object](/docs/connections/spec/common/). `Identify` events that contain the whitelisted `traits` will appear as a Slack message with the following default template:
 ```
-Identified user \{{name}}. \n\{{traits}}
+{% raw %}
+Identified user {{name}}. \n\{{traits}}
+{% endraw %}
 ```
 where "name" is the first found of the following:
 * `context.traits.name`
@@ -77,9 +79,13 @@ If you would like to have specific events be sent to a particular channel (#chan
 ### Event Templates
 Event templates also use [Handlebars expressions](https://handlebarsjs.com/guide/expressions.html) syntax. Make sure you reference the spec for the [Track method](/docs/connections/spec/track/) and [common object](/docs/connections/spec/common/). `Track` events will trigger a Slack message with the following default template:
 
-`'\{{name}} did \{{event}}.'`
+```
+{% raw %}
+{{name}} did {{event}}.
+{% endraw %}
+```
 
-where "event" is the event name and "name" is found with the same logic as that of the "name" in the [Identify template](/docs/connections/destinations/catalog/slack/#identify-template).
+"event" is the event name and "name" is found with the same logic as that of the "name" in the [Identify template](/docs/connections/destinations/catalog/slack/#identify-template).
 
 The basic Track structure:
 
@@ -127,5 +133,5 @@ The Slack Destination does not support `page` or `group` calls. Only `track` eve
 
 In order for `identify` events to work, make sure you [whitelist the traits](/docs/connections/destinations/catalog/slack/#whitelisted-traits).
 
-### I'm seeing [object Object] in my Slack message
-If you try to print an object (eg., `\{{properties}}`), you will see [object Object] in Slack. Drill down to a primitive type value (eg., `properties.plan`).
+### I see [object Object] in my Slack message
+If you try to print an object (for example, {% raw %} `{{properties}}` {% endraw %} ), you will see [object Object] in Slack. Drill down to a primitive type value (for example, `properties.plan`).

src/protocols/tracking-plan/create.md

@@ -37,7 +37,7 @@ The Tracking Plan editor is organized as a spreadsheet to help you  add new even
 | Name         | Specify the name of your event or property.   |
 | Description  | Enter a description for your event or property. These descriptions are helpful for both engineers instrumenting Segment and consumers of the data. |
 | Status       | Specify whether a property is required or optional. You can't require a `.track()` call because Segment is unable to verify when a `.track()` call should be fired. |
-| Data Type    | Specify the data type of the property. Data type options include `any, array, object, boolean, integer, number, string`. |
+| Data Type    | Specify the data type of the property. Data type options include `any, array, object, boolean, integer, number, string, Date time`. Note: Date time is required to be in ISO-8601 format |
 | Permitted Values | Enter simple regular expressions to validate property values. This works when a property data type is set to `string`. For example, you can add pipe delimited strings to the regex column to generate violations when a property value does not match fall, winter or spring. |
 
 > info ""