DOC 499 Salesforce group (#2770)

* Add Vidora to allow list

* Remove section about actions

Author: markzegarelli

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

@@ -27,7 +27,7 @@ This destination supports the most important pain point for Salesforce users: ge
 
 ### Identifying a Lead
 
-Let's go through a quick javascript example of identifying a lead:
+The example below demonstrates identifying a lead:
 
 ```javascript
 analytics.identify('YOUR_USERS_ID', {
@@ -91,7 +91,7 @@ By default Segment does not send identify calls to Salesforce, given their stric
 
 ## Group
 
-`.group()` calls create or update **Account Objects** inside Salesforce. When Segment receives a group call, similar to the `.identify()` call, it first checks using the `groupId` to see if the Account Object already exists in your Salesforce account. Depending on the response, Segment updates that object or create a new one. Creating/updating Accounts is the default behavior of `group` events. If you would like to customize this you can do so using [Actions](#custom-actions)
+`.group()` calls create or update **Account Objects** inside Salesforce. When Segment receives a group call, similar to the `.identify()` call, it first checks using the `groupId` to see if the Account Object already exists in your Salesforce account. Depending on the response, Segment updates that object or create a new one. Creating/updating Accounts is the default behavior of `group` events.
 
 Take this sample `.group()` call that you might send to Segment: