Update src/connections/destinations/catalog/actions-cordial/index.md

VitalyStakhov · stayseesong · web-flow · commit ef39e13cc092 · 2022-05-16T14:47:33.000+03:00
Co-authored-by: stayseesong &lt;83784848+stayseesong@users.noreply.github.com&gt;
diff --git a/src/connections/destinations/catalog/actions-cordial/index.md b/src/connections/destinations/catalog/actions-cordial/index.md
@@ -52,4 +52,4 @@ To send events, define the `createContactactivity` destination action. In additi
 
 If you plan segmenting users in Cordial, make sure you define the `addContactToList` and `removeContactFromList` destination actions. Both actions require the Segment group ID. `addContactToList` optionally accepts a list name. 
 
-Although optional, list name should be considered a must have, because it will drastically simplify segmenting contacts in Cordial based on lists. Lists without a name are called following the `segment_[groupId]` pattern.
+Although optional, list name should be considered a must have, because it simplifies segmenting contacts in Cordial based on lists. Lists without a name are called following the `segment_[groupId]` pattern.

Original file line number	Diff line number	Diff line change
@@ -52,4 +52,4 @@ To send events, define the `createContactactivity` destination action. In additi
`52`	`52`
`53`	`53`	If you plan segmenting users in Cordial, make sure you define the `addContactToList` and `removeContactFromList` destination actions. Both actions require the Segment group ID. `addContactToList` optionally accepts a list name.
`54`	`54`
`55`		-Although optional, list name should be considered a must have, because it will drastically simplify segmenting contacts in Cordial based on lists. Lists without a name are called following the `segment_[groupId]` pattern.
	`55`	+Although optional, list name should be considered a must have, because it simplifies segmenting contacts in Cordial based on lists. Lists without a name are called following the `segment_[groupId]` pattern.