Merge pull request #1828 from segmentio/08-30-21_weekly

08 30 21 weekly [netlify-ignore]

Author: markzegarelli

.vscode/yml.code-snippets

@@ -0,0 +1,24 @@
+{
+	// Place your segment-docs workspace snippets here. Each snippet is defined under a snippet name and has a scope, prefix, body and 
+	// description. Add comma separated ids of the languages where the snippet is applicable in the scope field. If scope 
+	// is left empty or omitted, the snippet gets applied to all languages. The prefix is what is 
+	// used to trigger the snippet and the body will be expanded and inserted. Possible variables are: 
+	// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders. 
+	// Placeholders with the same ids are connected.
+	// Example:
+	// "Print to console": {
+	// 	"scope": "javascript,typescript",
+	// 	"prefix": "log",
+	// 	"body": [
+	// 		"console.log('$1');",
+	// 		"$2"
+	// 	],
+	// 	"description": "Log output to console"
+	// }
+
+	"yml": {
+		"prefix": ["- name"],
+		"body":["- name: ${1:name}\r\tdescription: ${2:description}\r\tdefault: ${3}"],
+		"description": "Yaml settings"
+	}
+}

src/connections/destinations/catalog/optimizely-full-stack/index.md

@@ -164,7 +164,8 @@ Notification listeners are not available for Segment `track` events when impleme
 
 Follow these instructions on how to set up Personas and Optimizely:
 
-* [Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://www.optimizely.com/insights/blog/segment-personas-optimizely-full-stack-omnichannel-experiments/)
+* [Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://www.optimizely.com/insights/blog/segment-personas-optimizely-full-stack-omnichannel-experiments/){:target="_blank"}
+
 
 ## GDPR Support
 Segment supports deleting/suppressing users in Optimizely using the [Segment app](/docs/privacy/user-deletion-and-suppression/). In order to do this however, you will need to create a [Personal Access Token](https://developers.optimizely.com/x/authentication/personal-token/) in Optimizely and provide it as the value of the Access Token setting.

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

@@ -35,7 +35,7 @@ Once a source moves to Analytics.js 2.0, you can follow the steps above in [Manu
 
 ## Cases that require additional intervention
 
-There are two cases where upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
+In some cases, upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.  
 
 ### When using in-domain instrumentation CDN aliasing
 

src/connections/sources/sources-compare.md

@@ -43,7 +43,7 @@ Cloud-App Sources allow you to pull in data from third-party tools so you can us
     <th width="30%"> Categories </th>
     <th> Data Type </th>
   </tr>
-  {% assign integrations = site.data.catalog.sources.items %}
+  {% assign integrations = site.data.catalog.sources_capi.items %}
   {% for integration in integrations %}
     {% unless integration.categories contains promoted_categories[0] or integration.categories contains promoted_categories[1] or integration.categories contains promoted_categories[2] or integration.categories contains promoted_categories[3]%}
     {% unless integration.display_name == "Project"%}