Vero fix table, Vale fixes

Author: forstisabella

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

@@ -2,7 +2,7 @@
 title: Vero Destination
 id: 54521fdc25e721e32a72ef03
 ---
-Our Vero destination code is all open-source on GitHub if you want to check it out: [JavaScript](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/vero), [Server](https://github.com/segmentio/integration-vero).
+The Vero destination code is all open-source on GitHub if you want to check it out: [JavaScript](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/vero){:target="_blank"}, [Server](https://github.com/segmentio/integration-vero){:target="_blank"}.
 
 ## Getting Started
 
@@ -13,42 +13,40 @@ When you enable Vero in the Segment web app, your changes appear in the Segment
 
 Vero is supported on the client-side, server-side and mobile.
 
-- - -
-
 
 ## Identify
 
 
 ### Client Side
 
-When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we augment `traits` to have `traits.id` set to the `userId`, and then call Vero's `user` with the augmented traits object. You should provide both a `traits.email` and a `userId` for Vero to work best.
+When you call [Identify](/docs/connections/spec/identify/) on analytics.js, Segment augments `traits` to have `traits.id` set to the `userId`, and then call Vero's `user` with the augmented traits object. You should provide both a `traits.email` and a `userId` for Vero to work best.
 
 If no `email` is attached, the user is created in Vero but cannot be emailed. If you send omit the `userId`, Vero will use the email as the ID, which is is not recommended. Check out the [Vero docs](https://help.getvero.com/workflows/articles/creating-and-matching-vero-customer-ids/){:target="_blank"} for more information.
 
-A `userId` is a required value for all types of calls. Be sure you call `identify` with a `userId` for subsequent `track` calls to populate into Vero correctly. For server side calls, you will have to manually pass in the `userId` at the top level.
+A `userId` is a required value for all types of calls. Be sure you call Identify with a `userId` for subsequent `track` calls to populate into Vero correctly. For server side calls, you will have to manually pass in the `userId` at the top level.
 
 ### Server Side
 
-When you call [`identify`](/docs/connections/spec/identify/) from one of our server-side languages, we'll  call Vero's REST API and update the traits for the customer with that `userId`. If your `userId` is an email, we'll also set the trait `email` as your `userId` in the update call.
+When you call [Identify](/docs/connections/spec/identify/) from one of Segment's server-side languages, Segment calls Vero's REST API and update the traits for the customer with that `userId`. If your `userId` is an email, Segment sets the trait `email` as your `userId` in the update call.
 
 
 ## Track
 
-When you call [`track`](/docs/connections/spec/track/), we'll send the event to Vero with the event `name` and `properties` you provide. Events will be matched to the current user.
+When you call [Track](/docs/connections/spec/track/), Segment sends the event to Vero with the event `name` and `properties` you provide. Events will be matched to the current user.
 
-You can also unsubscribe users by sending a `track` event, passing in the user's ID as a `property`, like so:
+You can also unsubscribe users by sending a Track event, passing in the user's ID as a `property`, like so:
 
 ```javascript
 analytics.track('Unsubscribe', {
   id: '12345'
 });
 ```
 
-Note: If you'd like to explicitly specify a user's email with track events that is not an event metadata, you can send that under `context.traits.email`!
+Note: If you'd like to explicitly specify a user's email with track events that is not an event metadata, you can send that under `context.traits.email`.
 
 ## Sending Data from Vero
 
-Vero supports sending [email events](/docs/connections/spec/email) to other tools on the Segment platform. These events will be sent as `track` calls to the other destinations you've turned on.
+Vero supports sending [email events](/docs/connections/spec/email) to other tools on the Segment platform. These events will be sent as Track calls to the other destinations you've turned on.
 
 To enable this feature,
 
@@ -62,17 +60,17 @@ To enable this feature,
 
 ## Group
 
-When you call [`group`](/docs/connections/spec/group/), the `traits` included in the call will be set to the current user's **Group** property in Vero.
+When you call [Group](/docs/connections/spec/group/), the `traits` included in the call will be set to the current user's **Group** property in Vero.
 
 ## Alias
 
-Our [`alias`](/docs/connections/spec/alias/) method can be used from your server to "re-identify" an existing user identity to a new one.
+Segment's [Alias](/docs/connections/spec/alias/) method can be used from your server to "re-identify" an existing user identity to a new one.
 
 Most of the time this happens when you identify a visitor by their email address after they opt in, then later re-identify with a database ID when they become registered users.
 
-To connect the two identities you'll need to [`alias`](/docs/connections/spec/alias/) their current identity to their new one.
+To connect the two identities you'll need to [Alias](/docs/connections/spec/alias/) their current identity to their new one.
 
-Here's a python example of using [`alias`](/docs/connections/spec/alias/) to update the identity from an email address to a database ID:
+Here's a python example of using [Alias](/docs/connections/spec/alias/) to update the identity from an email address to a database ID:
 
 ```python
 analytics.alias('[email protected]', '8765309')
@@ -82,29 +80,17 @@ analytics.alias('[email protected]', '8765309')
 
 ### Tags
 
-The destination is capable of both adding and removing tags in Vero for a given user. Because `tags` is not a common property of events, this functionality is invoked using an [destination specific option](/docs/connections/sources/catalog/libraries/website/javascript/#selecting-destinations-with-the-integrations-object).
+The destination is capable of both adding and removing tags in Vero for a given user. Because `tags` is not a common property of events, this functionality is invoked using an [destination specific option](/docs/connections/sources/catalog/libraries/website/javascript/#managing-data-flow-with-the-integrations-object).
 
 To start using this feature, pass an object called `tags` with the following properties:
 
-<table>
-  <tr>
-    <td>`id` optional</td>
-    <td>String</td>
-    <td>The user Id to associate tags with. If this is not specified, the destination will simply use the userId from the event itself.</td>
-  </tr>
-  <tr>
-    <td>`action` required</td>
-    <td>String</td>
-    <td>Must be either 'add' or 'remove'. Indicates whether you would like to add or remove the tags for the given user.</td>
-  </tr>
-  <tr>
-    <td>`values` required</td>
-    <td>Array</td>
-    <td>An array of strings representing the tags to either add or remove.<td>
-  </tr>
-</table>
-
-Here is an example using our Node.js library:
+| Field    |             | Type   | Description                                                                                                                     |
+| -------- | ----------- | ------ | ------------------------------------------------------------------------------------------------------------------------------- | 
+| `id`     | _optional_  | String | The user Id to associate tags with. If this is not specified, the destination will simply use the userId from the event itself. |
+| `action` | _required_  | String | Must be either 'add' or 'remove'. Indicates whether you would like to add or remove the tags for the given user.                |
+| `values` | _required_  | Array  | An array of strings representing the tags to either add or remove.                                                              |
+
+Here is an example using Segment's Node.js library:
 
 ```javascript
 analytics.identify('324LKJF', {