Merge pull request #4584 from segmentio/sf-docs-update

[Salesforce Actions] - Updates docs with new delete action

Author: nick-Ag

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

@@ -50,9 +50,11 @@ When configuring a mapping, you must select the Operation that will be performed
 - **Update**. Updates fields on existing records in Salesforce. This operation is good for the following scenarios:
   - You have records in Salesforce that you want to add new information/fields to.
   - You want to update fields on existing records in Salesforce.
+- **Delete**. Deletes existing records in Salesforce. This operation is good for the following scenarios:
+  - You have records in Salesforce that you want to remove.
 
 ### Record Matchers
-When using the `update` and `upsert` operations, you must specify the match key(s) that will be used to query Salesforce for the record. You can do this within the Record Matchers object. Any field can be used as a record matcher, including:
+When using the `delete`, `update` and `upsert` operations, you must specify the match key(s) that will be used to query Salesforce for the record. You can do this within the Record Matchers object. Any field can be used as a record matcher, including:
 - **External IDs**. To map an External ID, the Salesforce API name should have `__c` appended to it.
 - **Record IDs**. To map a Record ID, the Salesforce API name is `Id`.
 - **Standard fields**. To map a standard field, the Salesforce API name should match what is in Salesforce for the given field, for example `Email`.
@@ -80,7 +82,7 @@ If you have more than one Salesforce instance connected to Segment, repeat these
 Keep the following in mind as you begin to use Salesforce (Actions):
 - Salesforce (Actions) supports batching. The workspace owner can edit the enabled-batching field manually for any of the mappings. This setting is disabled by default.
 - Salesforce (Actions) doesn’t support Delete CRUD operations on Custom Object. Custom Objects with CRUD the operation set to `delete` are not migrated.
-- Sending Identify events to Salesforce (Classic) results in a create or update operation for Leads, and maps properties from `event.traits` Salesforce (Actions) does not support this behavior. By default, the migration tool maps only a subset of the most used Lead properties as mentioned below. The workspace owner must map any additional Salesforce properties or Custom properties manually.
+- Sending Identify events to Salesforce (Classic) results in a create or update operation for Leads, and maps properties from `event.traits` Salesforce (Actions) does not support this behavior. By default, the automatic migration maps only a subset of the most used Lead properties as mentioned below. The workspace owner must map any additional Salesforce properties or Custom properties manually.
 
 Review the tables below to see how settings from Salesforce (Classic) were migrated to Salesforce (Actions).