Apply suggestions from code review

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

Author: mstieranka

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

@@ -19,19 +19,19 @@ This destination is maintained by Recombee. For any issues with the destination,
 
 Recombee (Actions) provides the following benefits over the classic Recombee destination:
 
-- **Streamlined Configuration**. You can now create mappings in a dedicated tab in the Segment web app, as opposed to needing to edit this in the settings. This allows you to configure the mappings on a per-event basis and makes it easier to verify that they work as intended.
-- **Removing Bookmarks is now possible**. You can now configure a mapping to send a *Delete Bookmark* Action, which will remove the bookmark interaction from the Recombee database.
+- **Streamlined Configuration**: You can now create mappings in a dedicated tab in the Segment web app, as opposed to needing to edit this in the settings. This allows you to configure the mappings on a per-event basis and makes it easier to verify that your mappings work as intended.
+- **Removable Bookmarks**: You can now configure a mapping to send a *Delete Bookmark* Action, which removes the bookmark interaction from the Recombee database.
 
 ## Migration from the classic Recombee AI destination
 
-It is recommended that for each source, the Recombee (Actions) destination and the classic Recombee AI destination are not enabled at the same time in order to prevent errors.
+Recombee recommends ensuring that a Recombee (Actions) destination and a classic Recombee AI destination connected to the same source are not enabled at the same time in order to prevent errors.
 
 ### Configuration changes
 
-Compared to the classic Recombee AI destination, the following changes were made with regards to the configuration:
+Compared to the classic Recombee AI destination, the following configuration changes were made:
 
-- In the destination settings, the **API Key** setting has been renamed to **Private Token** to better reflect the type of token used.
-- The **Track Events Mapping** setting has been removed. If you want to map custom events to Recombee interactions, make sure to create your own mappings in the Mappings tab in the Segment web app.
+- In the destination settings, the **API Key** setting was renamed **Private Token** to better reflect the type of token used.
+- The **Track Events Mapping** setting has been removed. If you want to map custom events to Recombee interactions, create your own mappings in the Mappings tab in the Segment app.
 - The **Item ID Property Name** setting is now no longer available, as this functionality is now available in Segment's native Mappings tab. Ensure that your mappings use the desired property for the **Item ID** action field.
 - *The following change only affects users that were relying on the `name` property to set their **Item ID**:* In presets, the **Item ID** property is now determined differently - in the default settings, the `asset_id` property (or `sku` for Ecommerce events) is now used as the fallback instead of `name`. The `name` property is never used by default, as it may not conform to the required **Item ID** format. Additionally, the property `content_asset_id` (or the first ID in `content_asset_ids`) is now the default **Item ID** only in Video events, where they are always present. 
 
@@ -49,7 +49,7 @@ Compared to the classic Recombee AI destination, the following changes were made
   - Copy the **Database ID** from the Recombee Admin UI and paste it into the **Database ID** field in the destination settings.
   - Copy the **Private Token** from the Recombee Admin UI and paste it into the **Private Token** field in the destination settings.
 
-Once you send the data from Segment to the Recombee destination you can:
+Once you send the data from Segment to the Recombee destination, you can:
   - Open the KPI console of the [Recombee Admin UI](https://admin.recombee.com){:target="_blank"} to see the numbers of the ingested interactions (updated in realtime).
   - Select the ID of an Item (or User) in the Items (or Users) catalog section in the Admin UI to view a specific ingested interaction.