update verbiage

Author: markzegarelli

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

@@ -14,16 +14,20 @@ This destination is maintained by Variance. For any issues with the destination,
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for "Variance" in the Destinations Catalog, and select the "Variance" destination.
 3. Choose which Source should send data to the "Variance" destination.
-4. Go to the [Variance Integrations page](http://app.variance.com/integrations) (you'll see it in the main nav under your company name).
+4. Go to the [Variance Integrations page](http://app.variance.com/integrations){:target="_blank"} (you'll see it in the main nav under your company name).
 5. Click **Add Connection**.
 6. Give your connection a name (descriptive is better as it can be used as an event filter in Variance).
 7. Choose a method for account matching. Details on these methods can be found in the [Account Mapping](#Account-Mapping) section at the bottom of this doc.
 8. Find and copy the "Secret" and "Webhook URL" fields associated with this project.
 9. Back in the Segment App, enter these as the "API Key" and "Webhook URL" fields in the "Variance" Destination settings.
 
-## Page
+## Supported methods
 
-If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like:
+Variance supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Page
+
+Send [Page](/docs/connections/spec/page) calls to *ADD WHAT PAGE CALLS ARE USED FOR HERE*. For example:
 
 ```js
 analytics.page()
@@ -32,9 +36,9 @@ analytics.page()
 Segment sends Page calls to Variance as a `Page` Event Type.
 
 
-## Screen
+### Screen
 
-If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like:
+Send [Screen](/docs/connections/spec/screen) calls to *ADD WHAT SCREEN CALLS ARE USED FOR HERE*. For example:
 
 ```obj-c
 [[SEGAnalytics sharedAnalytics] screen:@"Home"];
@@ -43,9 +47,9 @@ If you aren't familiar with the Segment Spec, take a look at the [Screen method
 Segment sends Screen calls to Variance as a `Screen` Event Type.
 
 
-## Identify
+### Identify
 
-If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
+Send [Identify](/docs/connections/spec/identify) calls to *ADD WHAT IDENTIFY CALLS ARE USED FOR HERE*. For example:
 
 ```js
 analytics.identify('userId123', {
@@ -56,9 +60,9 @@ analytics.identify('userId123', {
 Segment sends Identify calls to Variance as a `Contact`.
 
 
-## Track
+### Track
 
-If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like:
+Send [Track](/docs/connections/spec/track) calls to *ADD WHAT Track CALLS ARE USED FOR HERE*. For example:
 
 ```js
 analytics.track('Login Button Clicked')
@@ -67,9 +71,9 @@ analytics.track('Login Button Clicked')
 Segment sends Track calls to Variance as an `Action` Event Type.
 
 
-## Group
+### Group
 
-If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like:
+Send [Group](/docs/connections/spec/group) to Variance. For example:
 
 ```js
 analytics.group("groupId123", {
@@ -84,10 +88,11 @@ Segment sends Group calls to Variance as an `Account` if you've chosen the "Grou
 
 ## Account Mapping
 
-As mentioned in the setup instructions, Variance offers a few different ways of mapping your users to accounts/companies. Here's an overview:
+As mentioned in the setup instructions, Variance offers multiple ways to map your users to accounts or companies. Here's an overview:
 
-1. Group: if you already use the Group call to indicate the Account, then you don’t need to fill in anything. We will extract the Account automatically, and you’re good to go.
-1. Identify with custom traits (ex. `company.id` and `company.name`): choose this option if you include some information about the Account/Company/Organization as a trait in each Identify call. When you choose this option you'll need to let us know the name of the trait you use. For instance, if you do something like `{'company':{'id':1,'name':'Awesome Inc.'}}` you could add `company.id` as the Account ID trait and `company.name` as the Account Name trait.
-1. (Fallback) Identify email trait domain extraction: if you don't use either of the methods above, we can extract the domain from the `email` trait and use that as the Account name.
+1. Group: if you already use the Group call to indicate the Account, then you don’t need to fill in anything. Segment extracts the Account name automatically.
+2. Identify with custom traits (for example `company.id` and `company.name`): choose this option if you include some information about the Account, Company, or Organization as a trait in each Identify call. When you choose this option you'll need to add the name of the trait you use. For instance, if you configure the call with the data `{'company':{'id':1,'name':'Awesome Inc.'}}`, add `company.id` as the Account ID trait and `company.name` as the Account Name trait.
+3. (Fallback) Identify email trait domain extraction: if you don't use either of the methods above, Segment extracts the domain from the `email` trait and uses that value as the Account name.
 
-Note: if none of these work for your setup, [reach out to Variance support](mailto:[email protected]) and we can discuss alternatives.
+> info ""
+> If none of the above work for your setup, [contact Variance support](mailto:[email protected]) to discuss alternative configurations.