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

Co-authored-by: stayseesong <[email protected]>

Author: VitalyStakhov

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

@@ -15,7 +15,7 @@ hide-dossier: true
 
 Cordial (Actions) provides the following benefits over the classic Cordial destination:
 
-- **Transparent data mapping**. Classic Cordial destination receives data from Segment as is. Cordial backend then converts those Segment events to Cordial's format and clients have limited control over this conversion. Cordial (Actions) destination allows clients to fully define their own mappings of Segment events, making sure they receive data structured specifically for their needs. 
+- **Transparent data mapping**. The Classic Cordial destination receives data from Segment as is. The Cordial backend then converts those Segment events to Cordial's format and clients have limited control over this conversion. The Cordial (Actions) destination allows clients to fully define their own mappings of Segment events, making sure they receive data structured specifically for their needs. 
 - **Sending only the data you need**. With Cordial (Actions) you can define only those destination actions and mappings that make sense for your use cases, while Cordial Classic always sends four predefined API calls: identify, track, group, and page. 
 - **Sending Personas components to Cordial**. With Cordial (Actions) it is possible to define action mappings that will send audiences and user computed traits defined in Segment Personas platform to Cordial.