vale [netlify-ignore]

Author: markzegarelli

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

@@ -47,15 +47,15 @@ analytics.identify('user1234', {
 ```
 
 > info ""
-> HubSpot's device-mode integration has two conditions for Identify to create or update a contact. Identify calls must include a `traits.email` value and need to accompany a Page or Track call. You can read more from HubSpot's documentation [here](https://developers.hubspot.com/docs/methods/tracking_code_api/identify_visitor){:target="_blank"}. If you are using HubSpot's cloud-mode integration, an Identify call will update records without the need for a Page or Track call.
+> HubSpot's device-mode integration has two conditions for Identify to create or update a contact. Identify calls must include a `traits.email` value and need to go with a Page or Track call. You can read more from HubSpot's documentation [here](https://developers.hubspot.com/docs/methods/tracking_code_api/identify_visitor){:target="_blank"}. If you are using HubSpot's cloud-mode integration, an Identify call will update records without the need for a Page or Track call.
 
 HubSpot does not accept any trait keys that contain upper case letters or spaces. Segment converts any custom traits you send to lower case, and replaces spaces with an underscore.
 
-Any traits that aren't contact fields in HubSpot are removed from the request. To find out which fields you can set, check out the custom field names in **Contacts > Contact Settings**. Example field names are "firstname", "lastname", "company", "phone", etc.
+Hubspot removes from the request any traits that aren't contact fields in HubSpot. To find out which fields you can set, check out the custom field names in **Contacts > Contact Settings**. Example field names are `firstname`, `lastname`, `company`, and `phone`.
 
 If you specify a company name (using `traits.company.name`), it appears as a *property* of the contact (you can find it in HubSpot's UI using **About [contact] > View > View All Properties**), but it does not appear as the user's company under **[contact]'s Company**.
 
-The following traits are tagged as special fields in HubSpot:
+Hubspot tags the following fields as special fields:
 
 - address
 - city
@@ -78,13 +78,14 @@ analytics.track("Clicked Buy Now button", {
 })
 ```
 
-**IMPORTANT:** You must have a HubSpot Enterprise account for traits from an Identify call to be passed through to your Track call and be successfully sent as [a custom event to HubSpot](https://knowledge.hubspot.com/events-user-guide-v2/using-custom-events).
+> warning "Important"
+> You must have a HubSpot Enterprise account for Segment to pass traits from an Identify call through to your Track call and send them as[custom events to HubSpot](https://knowledge.hubspot.com/events-user-guide-v2/using-custom-events).
 
 The event will appear in your HubSpot UI but may take up to 60 minutes to appear in the graph visualization.
 
 ### Server
 
-When calling from any of our server-side sources you must provide the contact's email as `properties.email` so that HubSpot can tie the event to the appropriate contact. An example call in Python would look like:
+When calling from one of Segment's server-side sources, provide the contact's email as `properties.email` so that HubSpot can tie the event to the appropriate contact. An example call in Python would look like:
 
 ```python
 analytics.track(
@@ -101,7 +102,7 @@ In this case, your HubSpot `eventId` is 'Bought Item'. If you want to use an exi
 
 #### Setting Contact Properties on Track
 
-Segment recommends that you send `traits` with an [Identify](/docs/connections/spec/identify/) call. You can also set HubSpot properties on a track call sent from any server-side source, as allowed by their [events API](http://developers.hubspot.com/docs/methods/enterprise_events/http_api){:target="_blank"}. You might want to use this method if you're running out of API calls on the Identify requests.
+Segment recommends that you send `traits` with an [Identify](/docs/connections/spec/identify/) call. You can also set HubSpot properties on a track call sent from any server-side source, as allowed by Hubspot's [events API](http://developers.hubspot.com/docs/methods/enterprise_events/http_api){:target="_blank"}. You might want to use this method if you're running out of API calls on the Identify requests.
 
 Include HubSpot contact properties into the `context.traits` object:
 
@@ -122,7 +123,8 @@ analytics.track(
 
 ## Group
 
-__NOTE: Group calls are not compatible with our Analytics.js library.__
+> info ""
+> Group calls are not compatible with the Analytics.js library.
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like:
 
@@ -137,14 +139,14 @@ analytics.group({
 });
 ```
 
-Group calls map to the HubSpot [Companies API](https://developers.hubspot.com/docs/methods/companies/companies-overview){:target="_blank"}. Segment's integration is responsible for creating and updating company objects with whatever traits you set, as well as [associating individual contacts to a company](https://developers.hubspot.com/docs/methods/companies/add_contact_to_company){:target="_blank"}.
+Group calls map to the HubSpot [Companies API](https://developers.hubspot.com/docs/methods/companies/companies-overview){:target="_blank"}. Segment's integration creates and updates company objects with whatever traits are set, and [associates individual contacts to a company](https://developers.hubspot.com/docs/methods/companies/add_contact_to_company){:target="_blank"}.
+
+
+The three requirements to creating companies and associating contacts are:
 
-> warning "" 
-> There are three requirements to creating companies and associating contacts:
->
->1. Group calls only take effect when called using server-side libraries or mobile libraries, not using our client-side javascript library.
->2. Your contact must have been identified and created within HubSpot (called using analytics.identify for this userId first).
->3. You must include a `website` trait in your group call, and it must be a full, valid, and complete URL. HubSpot uses the domain of the website trait as a unique identifier for companies. To create a new company you must use the full URL and not just the subdomain.
+1. Group calls take effect when called using server-side libraries or mobile libraries, not the client-side javascript library.
+2. Your contact must be identified and created within HubSpot (called using `analytics.identify` for this `userId first`).
+3. You must include a `website` trait in your group call, and it must be a full, valid, and complete URL. HubSpot uses the domain of the website trait as a unique identifier for companies. To create a new company you must use the full URL and not just the subdomain.
 
 Segment can send the following group traits to HubSpot as special properties:
 
@@ -164,7 +166,7 @@ Segment can send the following group traits to HubSpot as special properties:
 
 ### API Call Limits
 
-HubSpot limits the total amount of hourly and daily requests we can make to their API on your behalf. Read more about these limits [here](https://developers.hubspot.com/apps/api_guidelines).
+HubSpot limits the total amount of hourly and daily requests Segment can make to their API on your behalf. Read more about these limits [here](https://developers.hubspot.com/apps/api_guidelines){target="_blank"}.
 
 HubSpot Plan: Free & Starter
 * Maximum Number of API Calls per 10 Seconds, per Key or Token: **100**
@@ -181,9 +183,9 @@ HubSpot Plan: API Add-On (Any Tier)
 
 ### Sending Dates as Property Values
 
-HubSpot's API has [specific requirements](http://developers.hubspot.com/docs/faq/how-should-timestamps-be-formatted-for-hubspots-apis) regarding how dates should be formatted before they are delivered as contact properties with date types.
+HubSpot's API has [specific requirements](http://developers.hubspot.com/docs/faq/how-should-timestamps-be-formatted-for-hubspots-apis) regarding you to format dates before they deliver as contact properties with date types.
 
-In order to ensure proper transformation of these properties, pass them to Segment as [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) formatted strings and **not** as UNIX timestamps. Here's a Javascript example:
+To ensure proper transformation of these properties, pass them to Segment as [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) formatted strings and **not** as UNIX timestamps. Here's a Javascript example:
 
 ```js
 analytics.identify('userid', {
@@ -193,14 +195,14 @@ analytics.identify('userid', {
 
 ### Invalid 'lifecyclestage'
 
-When using any of our server-side sources, our connector will infer `traits.lifecycle_stage` as `lifecyclestage`. If you're using a custom contact property for custom lifecycle stage's, you should give the property a distinct name, such as `custom_lifecycle_stage`.
+When using any of Segment's server-side sources, a connector infers `traits.lifecycle_stage` as `lifecyclestage`. If you're using a custom contact property for custom lifecycle stage's, you should give the property a distinct name, such as `custom_lifecycle_stage`.
 
 ### Loading Forms SDK
 
-Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options) alongside their tracking library. This can be done by enabling the **Load Forms SDK** setting when configuring your HubSpot integration.
+Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options) alongside their tracking library. Enable the **Load Forms SDK** setting when you your HubSpot integration.
 
 > info ""
-> The Forms SDK expects to be loaded synchronously but analytics.js is loaded asynchronously. Therefore, in order to interact with the API, you need to run your code inside an [analytics.ready](/docs/connections/sources/catalog/libraries/website/javascript/#ready) callback. Here's an example:
+> The Forms SDK expects to load synchronously but analytics.js loads asynchronously. To interact with the API, run code inside an [analytics.ready](/docs/connections/sources/catalog/libraries/website/javascript/#ready) callback. For example:
 
 ```js
 analytics.ready(function(){
@@ -228,7 +230,7 @@ HubSpot requires that you create and define any custom traits in the HubSpot UI
 
 ### How it works: User-Level Traits and Audiences
 
-Personas sends **User-Level data** to HubSpot to update properties on a user (or `contacts` in HubSpot) record, using an **Identify** call to add or update a standard  `Property` or when a trait is computed, and a **Track** call when an audience is entered or exited.
+Personas sends **User-Level data** to HubSpot to update properties on a user (or `contacts` in HubSpot) record, using an **Identify** call to add or update a standard  `Property` or when Segment computes a trait, and a **Track** call when the user enters or exits an audience.
 
 - **Computed Traits**: When the trait is first computed, Personas sends an **Identify** call to update the records of all users who are included in the computed trait. Each time the trait is computed after that, Personas sends a **Identify** call to HubSpot to update the values. For example, if a computed trait counts the number of times a user visits your pricing page, and the user visits your pricing page five times, Segment first sends an Identify call with the property `pricing_page_visits: 5`, then sends a Identify call when this number updates. This appears in HubSpot as a `Property` for the contact.
 

vale-styles/Vocab/Docs/accept.txt

@@ -51,4 +51,5 @@ gmail
 (?:U|u)nmaps?\b
 (?:U|u)nlinks?\b
 (?:P|p)ostgres
-Smartly
+Smartly
+Hubspot