Merge pull request #1717 from segmentio/pwseg-sfmc-update

DOC-225 Update/Change to the SFMC Destination Docs

Author: markzegarelli

src/connections/destinations/catalog/salesforce-marketing-cloud/index.md

@@ -281,14 +281,12 @@ In order to do this, you must have access to **Personas**. To learn more, [conta
 > **Tip**: We recommend that you use [SFMC batching](#optional-set-up-sfmc-batching) with Personas to help reduce the number of API calls that you send to SFMC, but this is optional. If you choose to set up batching, do this _before_ you set up the SFMC destination in your Segment workspace.
 
 1. In your Personas space, add the SFMC destination to a computed trait or audience.
-2. You can either sync to an existing Data Extension or you can make the sync create a new Data Extension in SFMC.
-   - To **Create a new Data Extension** leave the Data Extension External Key blank. This creates a new Data Extension in the default location configured for your SFMC instance, with all the required columns.
-   - To **Sync to an existing Data Extension**: enter the Data Extension External Key for the existing Data Extension. When your audience syncs to it, Segment adds a new column which stores the computed trait or audience membership.
+2. Enter the Data Extension External Key for the existing Data Extension. When your audience syncs to it, Segment adds a new column which stores the computed trait or audience membership.
 
-If you sync to an existing Data Extension, there are additional requirements:
+When you sync to an existing Data Extension, note these additional requirements:
 - The table cannot have an existing **Primary Key**, unless it is the `Contact Key` field, and the field type is `Text`.
 - All fields in the Data Extension must be nullable (meaning optional, or not required), except the `Contact Key` field.
-- Any fields that you will send with Segment, and which already exist in the Data Extension must be of the correct data type. If they do not exist, Segment creates them for you. The standard identifiers Segment sends come from the [Context object](https://segment.com/docs/connections/spec/common/#context), and appear in the image below.
+- Any fields that you send with Segment, and which already exist in the Data Extension, must be of the correct data type. If they do not exist, Segment creates them for you. The standard identifiers Segment sends come from the [Context object](https://segment.com/docs/connections/spec/common/#context), and appear in the image below.
 
 ![](images/existing-dext-data-types.png)