Merge pull request #1597 from segmentio/update_cleanup

update cleanup

Author: markzegarelli

.vale.ini

@@ -3,4 +3,4 @@ StylesPath = vale-styles
 Vocab = Docs
 
 [*.md]
-BasedOnStyles = write-good, Segment
+BasedOnStyles = write-good, segment

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

@@ -15,10 +15,10 @@ Segment's **Optimizely Full Stack (previously Optimizely X)** destination suppor
 * [Optimizely Full Stack Android (Cloud-mode)](#android-cloud-mode-implementation)
 * [Optimizely Full Stack iOS (Cloud-mode)](#ios-cloud-mode-implementation)
 
-If you're interested in implementing Optimizely X Web or Optimizely Full Stack with the JavaScript SDK, see Segment's [**Optimizely Web** destination](https://segment.com/docs/connections/destinations/catalog/optimizely-web/), which supports:
+If you're interested in implementing Optimizely X Web or Optimizely Full Stack with the JavaScript SDK, see Segment's [**Optimizely Web** destination](/docs/connections/destinations/catalog/optimizely-web/), which supports:
 
-* [Optimizely X Web](https://segment.com/docs/connections/destinations/catalog/optimizely/#optimizely-x-web)
-* [Optimizely Full Stack (JavaScript)](https://segment.com/docs/connections/destinations/catalog/optimizely/#optimizely-full-stack-javascript-)
+* [Optimizely X Web](/docs/connections/destinations/catalog/optimizely/#optimizely-x-web)
+* [Optimizely Full Stack (JavaScript)](/docs/connections/destinations/catalog/optimizely/#optimizely-full-stack-javascript-)
 
 ## Implementation Prerequisite
 
@@ -50,7 +50,7 @@ For more details on how events are attributed on the Optimizely results page, re
 Upon invocation of a Segment `track` event, Segment maps the event to an Optimizely `track` event:
 * If the Segment event name matches exactly the name of an active experiment `metric` set up in the Optimizely dashboard;
 * If the experiment `metric` is associated with a running experiment;
-* If the current user has been assigned a `userId` using Segment's `identify` method (e.g. `analytics.identify('123')`);
+* If the current user has been assigned a `userId` using Segment's `identify` method (for example,  `analytics.identify('123')`);
 * If the current user is activated in a running experiment with the associated `metric`.
 
 Segment also handles the following mapping:
@@ -60,8 +60,8 @@ Segment also handles the following mapping:
 
 `revenue` values should be passed as a Segment `property`. The value should be an integer and represent the value in cents, so, for example, $1 should be represented by `100`.
 
-> note "Note:"
-> [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example, arrays).
+> note ""
+> **Note**: [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example, arrays).
 
 Segment defaults to identifying users with their `anonymousId`. Enabling the "Use User ID" setting in your Segment settings means that only `track` events triggered by identified users are passed downstream to Optimizely. You may optionally fall back to `anonymousId` when `userId` is unavailable by setting `fallbackToAnonymousId` to `true`.
 
@@ -80,7 +80,7 @@ Segment's server-side integration with Optimizely Full Stack does not support no
 When implementing Optimizely Full Stack using cloud-mode, Segment will map `track` events to Optimizely `track` events on our servers and deliver the data to your Optimizely project as usual.
 
 > note ""
-> **Note:** If you are using Optimizely SDKs v1.x or v2.x: if a visitor has any `activate` or `isFeatureEnabled` calls, their `attributes` object for these calls must match the `attributes` object passed to any `track` calls for that user id so that it can be correctly attributed on the Optimizely results page.
+> **Note:** If you are using Optimizely SDKs v1.x or v2.x: if a visitor has any `activate` or `isFeatureEnabled` calls, the `attributes` object for these calls must match the `attributes` object passed to any `track` calls for that user id so that it can be correctly attributed on the Optimizely results page.
 
 If you are using Optimizely SDKs v3+, [Easy Event Tracking](https://blog.optimizely.com/2019/02/26/introducing-easy-event-tracking-the-easier-way-to-understand-and-optimize-the-customer-journey/) is enabled by default for decision events. Set up does not require maintaining the attributes of a user as long as the user id stays the same between Optimizely `activate` and `isFeatureEnabled` calls and Segment `track` calls to have Optimizely `metrics` populated in the Optimizely results page. If you would like to segment your Optimizely results by user `attribute`, then make sure the `attributes` passed in for the `activate` and `isFeatureEnabled` calls match the `attributes` passed in for the `track` calls for that user id.
 
@@ -100,13 +100,13 @@ Segment also handles the following mapping:
 `revenue` values should be passed as a Segment `property`. The value should be an integer and represent the value in cents, so, for example, $1 should be represented by `100`.
 
 > note ""
-> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely will reject events with any other data types (e.g. arrays).
+> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example,  arrays).
 
 Segment defaults to identifying users with their `anonymousId`. Enabling "Use User ID" setting in your Segment dashboard means that only `track` events triggered by identified users are passed downstream to Optimizely. You may optionally fall back to `anonymousId` when `userId` is unavailable by setting `fallbackToAnonymousId` to `true`.
 
 ### Identify
 
-Invoking a Segment `identify` event sets Segment `traits` as Optimziely `attributes`. The `attributes` are sent downstream to Optimizely upon invocation of the next Segment `track` event.
+Invoking a Segment `identify` event sets Segment `traits` as Optimizely `attributes`. The `attributes` are sent downstream to Optimizely upon invocation of the next Segment `track` event.
 
 ## Reset
 
@@ -148,13 +148,13 @@ Segment also handles the following mapping:
 `revenue` values should be passed as a Segment `property`. The value should be an integer and represent the value in cents, so, for example, $1 should be represented by `100`.
 
 > note ""
-> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely will reject events with any other data types (e.g. arrays).
+> **Note:** [Custom Event Tags](https://docs.developers.optimizely.com/full-stack/docs/include-event-tags) in Optimizely, which include all Event Tags except `revenue` and `value`, are not displayed on the Optimizely results page, however they are available in a [Data Export](https://docs.developers.optimizely.com/web/docs/data-export) report. Event Tags can be strings, integers, floating point numbers, or boolean values. Optimizely rejects events with any other data types (for example,  arrays).
 
 Segment defaults to identifying users with their `anonymousId`. Enabling "Use User ID" setting in your Segment dashboard means that only `track` events triggered by identified users are passed downstream to Optimizely. You may optionally fall back to `anonymousId` when `userId` is unavailable by setting `fallbackToAnonymousId` to `true`.
 
 ### Identify
 
-Invoking a Segment `identify` event sets Segment `traits` as Optimziely `attributes`. The `attributes` are sent downstream to Optimizely upon invocation of the next Segment `track` event.
+Invoking a Segment `identify` event sets Segment `traits` as Optimizely `attributes`. The `attributes` are sent downstream to Optimizely upon invocation of the next Segment `track` event.
 
 ### Notification Listeners
 
@@ -167,4 +167,4 @@ Follow these instructions on how to set up Personas and Optimizely:
 * [Using Segment Personas and Optimizely Full Stack for Omnichannel Experiments](https://blog.optimizely.com/tag/segment-personas/)
 
 ## GDPR Support
-Segment supports deleting/suppressing users in Optimizely using the [Segment app](https://segment.com/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.
+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.

vale-styles/Vocab/Docs/accept.txt

@@ -37,3 +37,5 @@ ga
 Doubleclick
 (?:C|c)annonical
 (?:U|u)rls?\b
+Optimizely
+Omnichannel

vale-styles/segment/rubyliquid.yml

@@ -1,7 +1,4 @@
 extends: spelling
 message: "Did you really mean '%s'?"
 level: error
-filters:
-  # Ignore all contents in Ruby liquid tags.
-  - {% .* %}
-  - {{ .* }}
+filters: