first group of additions to the Vale linter, first pass of cleanup (#1106)

* first group of additions to the Vale linter, first pass of cleanup

* add one more fix

Signed-off-by: sanscontext <[email protected]>

* small cleanup, add some names

* more cleanup

* apparently we don't like keeping it simple stupid, so decap

* add blocklist/allowlist

* added segment style and started a substitution list.

* add we're, test, move some rejects into subs

* hide lorem from vale, fix message

* some legibility cleanup

* add eg/ie subs

* yay!

Co-authored-by: markzegarelli <[email protected]>

Author: sanscontext

.vale.ini

@@ -1,6 +1,6 @@
 StylesPath = vale-styles
 
-Vocab = blog
+Vocab = Docs
 
 [*.md]
-BasedOnStyles = Vale, write-good
+BasedOnStyles = write-good, Segment

src/_data/catalog/destinations.yml

@@ -11445,7 +11445,7 @@ items:
       server: true
   previous_names:
   - Iterable
-- display_name: KISSmetrics
+- display_name: Kissmetrics
   slug: kissmetrics
   name: catalog/destinations/kissmetrics
   description: >-
@@ -11520,7 +11520,7 @@ items:
       mobile: true
       server: true
   previous_names:
-  - KISSmetrics
+  - Kissmetrics
 - display_name: Kahuna
   slug: kahuna
   name: catalog/destinations/kahuna

src/_includes/components/code-example.md

@@ -2,7 +2,7 @@
 layout: code-example
 ---
 
-{:title="JavaScript"}
+{:title="Javascript"}
 ```js
 var example = document.querySelectorAll('.example');
 ```

src/_includes/content/whats-a-destination.md

@@ -1,4 +1,4 @@
-Destinations are business tools or apps that you can connect to the data flowing through Segment. Some of our most popular destinations are Google Analytics, Mixpanel, KISSmetrics, Customer.io, Intercom, and KeenIO.
+Destinations are business tools or apps that you can connect to the data flowing through Segment. Some of our most popular destinations are Google Analytics, Mixpanel, Kissmetrics, Customer.io, Intercom, and KeenIO.
 
 All of these tools run on the same data: who are your customers and what are they doing? But each tool requires that you send that data in a slightly different format, which means that you'd have to write code to track all of this information, again and again, for each tool, on each page of your app or website.
 

src/_includes/content/whats-a-source.md

@@ -3,7 +3,7 @@ In Segment, you create a source (or more than one!) for each website or app you
 Sources belong to a workspace, and the URL for a source looks something like this:
 `https://segment.com/<my-workspace>/sources/<my-source-name>/`
 
-You can create new sources using the button in the workspace view. Each source you create has a write key, which is used to send data to that source. For example, to load [`analytics.js`, the Segment JavaScript library](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) on your page, the snippet on the [Quickstart Guide](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) includes:
+You can create new sources using the button in the workspace view. Each source you create has a write key, which is used to send data to that source. For example, to load [`analytics.js`, the Segment Javascript library](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) on your page, the snippet on the [Quickstart Guide](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) includes:
 
 ```js
 analytics.load("YOUR_WRITE_KEY");

src/connections/destinations/catalog/adobe-analytics/index.md

@@ -64,7 +64,7 @@ Adobe Analytics has a real-time reporting feature which displays web page traffi
 
 Device-mode web data is sent using Analytics.js, with Analytics.js either serving as a wrapper/bundle around the Adobe Analytics code, or sending directly to Segment servers where the data is then sent on to the Adobe destination.
 
-Our Adobe Analytics device-mode destination code is open sourced on Github. Feel free to check it out:
+Our Adobe Analytics device-mode destination code is open sourced on GitHub. Feel free to check it out:
 [iOS](https://github.com/segment-integrations/analytics-ios-integration-adobe-analytics),
 [Android](https://github.com/segment-integrations/analytics-android-integration-adobe-analytics) and
 [JS](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/adobe-analytics).

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

@@ -8,7 +8,7 @@ platform for your web and mobile apps. By analyzing the actions your users
 perform, you can gain a better understanding to drive retention, engagement,
 and conversion.
 
-Our Amplitude destination code is open sourced on Github. Feel free to check it
+Our Amplitude destination code is open sourced on GitHub. Feel free to check it
 out:
 [iOS](https://github.com/segment-integrations/analytics-ios-integration-amplitude),
 [Android](https://github.com/segment-integrations/analytics-android-integration-amplitude) and

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

@@ -13,7 +13,7 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat
   1. From your Segment UI's Destinations page click on "Add Destination".
   2. Search for "AppsFlyer" within the Destinations Catalog and confirm the Source you'd like to connect to.
   3. Drop in your `AppsFlyer Dev Key`, which can be retrieved from the App Settings section of your AppsFlyer account.
-  4. Follow the instructions in the Github repos: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
+  4. Follow the instructions in the GitHub repos: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
   5. After you build and release to the app store, we start translating and sending your data to AppsFlyer automatically.
 
 **Important:** If you plan on using the server-side destination for an Android project, make sure to enter your **Android App ID**. If you are using only the mobile SDK, Android projects only require the **AppsFlyer Dev Key**. iOS projects always require both the **AppsFlyer Dev Key** and the **Apple App ID**. Also, note that if you do use the server-side destination, you will not be able to selectively disable calls sent to AppsFlyer using your Segment dashboard.

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

@@ -3,7 +3,7 @@ title: Batch Destination
 beta: true
 ---
 
-The Batch.com integration code is open sourced on Github. Feel free to check it out: [iOS](https://github.com/BatchLabs/ios-segment-integration), [Android](https://github.com/BatchLabs/android-segment-integration).
+The Batch.com integration code is open sourced on GitHub. Feel free to check it out: [iOS](https://github.com/BatchLabs/ios-segment-integration), [Android](https://github.com/BatchLabs/android-segment-integration).
 
 ## Getting Started
 

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

@@ -5,7 +5,7 @@ beta: true
 
 Boomtrain is a predictive intelligence platform for marketers that uses machine learning to drive increased clicks, engagement and revenue through customer communications. [Visit Website](http://boomtrain.com).
 
-The Boomtrain destination with Segment supports the `identify`, `track` and `page` methods.  Our Javascript destination code is open sourced on Github. [Feel free to check it out](https://github.com/boomtrain/segmentio_integration).
+The Boomtrain destination with Segment supports the `identify`, `track` and `page` methods.  Our Javascript destination code is open sourced on GitHub. [Feel free to check it out](https://github.com/boomtrain/segmentio_integration).
 
 ## Getting Started