vale edits

Author: markzegarelli

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

@@ -2,10 +2,11 @@
 title: Friendbuy Destination
 cmode-override: true
 ---
+Friendbuy is a referral marketing and campaign optimization platform.
 
 ## Getting Started
 
-Setting up Friendbuy is very simple!
+{% include content/connection-modes.md %}
 
 1. Log in to your Friendbuy account and go to **Integration Code**.
 2. Copy the **Site ID** above the snippet box.
@@ -16,31 +17,35 @@ Setting up Friendbuy is very simple!
 
 This destination allows you to:
 
-- Map your Page calls to facilitate [Widget Management](http://developers.friendbuy.com/#widget-management)
-- Map your Identify calls to facilitate [Customer Tracking](http://developers.friendbuy.com/#customer-tracking)
-- Map your Track calls to facilitate [Order Tracking](http://developers.friendbuy.com/#order-tracking) and [Product Tracking](http://developers.friendbuy.com/#product-tracking)
+- Map your Page calls to enable [Widget Management](http://developers.friendbuy.com/#widget-management)
+- Map your Identify calls to enable [Customer Tracking](http://developers.friendbuy.com/#customer-tracking)
+- Map your Track calls to enable [Order Tracking](http://developers.friendbuy.com/#order-tracking) and [Product Tracking](http://developers.friendbuy.com/#product-tracking)
 
 
 ## Page
 
 To load specific widgets on different web pages, you can configure your settings to map your _named_ Page call(s) to specific Friendbuy Widget(s). You can also configure a several optional [advanced widget configurations](http://developers.friendbuy.com/#widget-options) such as **auto delay** and **custom parameters**.
 
 
-There are two types of Widgets you can map to your Page calls:
+Friendbuy has two Widgets you can map to your Page calls:
 
-- Site Wide Widgets
-  - These types of widgets are recommended by Friendbuy to load on all your webpages. If you wish to use these types of widgets, you can add them under the *Side Wide Widgets* setting. _NOTE_: You are NOT required to map a site wide widget if the **Call To Action** type is a ribbon served by Friendbuy. This type of overlay widget will just load when we boot up Friendbuy's library.
+**Site Wide Widgets**
 
-- Other widgets
-  - All other widgets will fall under this category whereby you can map the `name` of a unique Segment `.page()` call to a widget ID.
+Friendbuy recommends you to load these widgets on all your web pages. To use these widgets, you can add them under the *Side Wide Widgets* setting. 
 
 > info ""
-> If you have mapped a site wide overlay widget loads on every `.page()` call, even if we have loaded a different widget on the page that you have explicitly mapped.
+> You don't need to map a site wide widget if the **Call To Action** type is a ribbon served by Friendbuy. This overlay widget loads when Segment loads the Friendbuy library.
 
+**Other widgets**
+
+All other widgets will fall under this category whereby you can map the `name` of a unique Segment `.page()` call to a widget ID.
+
+> info ""
+> If you have mapped a site wide overlay widget, it loads on every `.page()` call.
 
 ## Identify
 
-When you call `.identify()`, we will send the following mapped traits:
+When you call `.identify()`, Segment sends the following mapped traits:
 
 | **Segment Traits**    | **Friendbuy Standard Fields** |
 | --------------------- | ----------------------------- |
@@ -63,7 +68,7 @@ analytics.identify('2', {
 > Friendbuy does not accept custom traits.
 ### Stripe and Chargebee Customer ID
 
-If you are integrated with Stripe or Chargebee and would like to send those IDs to Friendbuy, you can pass them as integration specific options:
+If you integrate with Stripe or Chargebee and need send those IDs to Friendbuy, you can pass them as integration specific options:
 
 ```js
 analytics.identify('2', {
@@ -82,11 +87,11 @@ analytics.identify('2', {
 
 ## Track / Order Completed
 
-This Destination accepts only `Order Completed` events as decribed in our [ecommerce spec](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed).
+This Destination accepts `Order Completed` events as described in the Segment [ecommerce spec](/docs/connections/spec/ecommerce/v2/#order-completed).
 
 Friendbuy has a concept of [Order Tracking](http://developers.friendbuy.com/#order-tracking) and [Product Tracking](http://developers.friendbuy.com/#product-tracking) where the former describes how to send data about the top level order whereas the latter documents instructions on sending data about each of the product within that order.
 
-When sending the order details, we will make the following translation:
+When you send order details, Segment makes the following translation:
 
 | **Segment Properties**    | **Friendbuy Standard Fields** |
 | ------------------------- | ----------------------------- |
@@ -95,7 +100,7 @@ When sending the order details, we will make the following translation:
 | `revenue`                 | `amount`                      |
 | `coupon`                  | `coupon_code`                 |
 
-Then we will iterate over each item in your `properties.products` and send the following mapping:
+Then Segment iterates over each item in your `properties.products` and send the following mapping:
 
 
 | **Segment Properties**  | **Friendbuy Standard Fields** |

vale-styles/Vocab/Docs/accept.txt

@@ -52,4 +52,6 @@ gmail
 (?:U|u)nlinks?\b
 (?:P|p)ostgres
 Smartly
-Hubspot
+Hubspot
+Friendbuy
+Chargebee