Minor fixes

Author: pwseg

src/connections/destinations/catalog/actions-pipedrive/index.md

@@ -9,7 +9,7 @@ hidden: true
 
 {% include content/plan-grid.md name="actions" %}
 
-The Actions Pipedrive destination allows customers to share Segment event data with to Pipedrive. Segment events sent to Pipedrive will either create new Entities or update existing Entities in Pipedrive. 
+The Actions Pipedrive destination allows customers to share Segment event data with Pipedrive. Segment events sent to Pipedrive will either create new Entities or update existing Entities in Pipedrive. 
 
 ## Benefits of Actions Pipedrive
 
@@ -23,22 +23,22 @@ Actions Pipedrive provides the following benefits:
 1. Sign in to your Segment Workspace
 2. Click to the **Catalog** tab. 
 3. Click on the **Destinations** tab.
-2. Use the search field to find the 'Pipedrive' Destination. Click on the **Actions Pipedrive** tile. 
+2. Use the search field to find the 'Pipedrive' destination. Click on the **Actions Pipedrive** tile. 
 3. Click **Add Destination**.
-4. Select a Source to connect to and click the **Next** button.
-5. Provide a name for your Pipedrive Destination and click the **Create Destination** button.
+4. Select a source to connect to and click the **Next** button.
+5. Provide a name for your Pipedrive destination and click the **Create Destination** button.
 6. On the Settings tab, provide values in the **Domain** and **API Token** settings fields, then click the **Save Changes** button. 
 7. Navigate to the **Mappings** tab to configure how Segment events will be mapped to Pipedrive Entities. By default, mappings to upsert to Pipedrive's Person, Organization and Activity Entities will already be enabled. You can configure new Mappings by clicking on the **New Mapping** button. 
-8. When you have configured and enabled your Mappings, click back to the **Settings** tab and enable the integration using the **Enable Destination** toggle. Segment should now start sending event data to Pipedrive.  
+8. After you've configured and enabled your Mappings, click back to the **Settings** tab and enable the integration using the **Enable Destination** toggle. Segment should now start sending event data to Pipedrive.  
 
-## Inserting new Entities Vs updating existing Entities
+## Inserting new Entities compared to updating existing Entities
 
-Segment uses the **Match value** field value as a key when creating or updating an Entity in Pipedrive. By default the **Match value** will be mapped to the **id** field for the corresponding Entity. You can specify which Pipedrive field to use as a key using the **Match field** field. 
+Segment uses the **Match value** field value as a key when creating or updating an Entity in Pipedrive. By default, the **Match value** will be mapped to the **id** field for the corresponding Entity. You can specify which Pipedrive field to use as a key using the **Match field** field. 
 
 **Match field** fields are dynamic and will populate with data from your Pipedrive account. 
 ![Match value and and fields can be used to specify how Segment should update Pipedrive Entities](images/match_field.png)
 
-In the example below Segment is configured to create or update Person entities using the email field. 
+In the following example, Segment is configured to create or update Person entities using the email field. 
 ![Using email to upsert to the Person Entity](images/match_field.png)
 
 ## Associating Entities with other Entities
@@ -51,4 +51,3 @@ Entities such as the **Deal** Entity can be configured to be associated with oth
 
 {% include components/actions-fields.html %}
 
-