Apply suggestions from code review

Review items added.

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

Author: cmastr

src/connections/destinations/actions.md

@@ -82,14 +82,17 @@ Moving from a classic destination to an actions-based destination is a manual pr
 5. Verify that data is flowing from the development or test source to the partner tool.
 6. Repeat the steps above with your production source.
 
-For a more comprehensive migration from a classic destination to an actions-based destination, please follow the steps outlined below. This implementation strategy is only available for customers on a Segment Business Tier plan with access to Destination Filters. To remove the possibility of duplicate events or dropped events, adding an additional line of defense with Destination Filters will ensure that events sent before/after a specified `received_at` timestamp will be sent to each destination.
+### Migrate to an actions-based destination using Destination Filters
+For a more comprehensive migration from a classic destination to an actions-based destination, follow the steps outlined below. This implementation strategy is only available for customers on a Segment Business Tier plan with access to [Destination Filters](/docs/connections/destinations/destination-filters/). By adding additional line of defense with Destination Filters, you remove the possibility of duplicate events or dropped events and ensure that events sent before/after a specified `received_at` timestamp are sent to each destination.
 
-This migration strategy involves configuring a destination filter on both the Classic destination as well as the Actions destination. The Classic destination filter will be configured to block events by the `received_at` field with a certain value, and the Actions destination to drop events until the `received_at` timestamp field reaches that same value. Destination Filters within the UI have a limitation where they cannot access any top-level fields, but this is not a limitation for [Destination Filters]([url](https://docs.segmentapis.com/tag/Destination-Filters/)) created by the [Public API]([url](https://segment.com/docs/api/public-api/)) using [FQL]([url](https://segment.com/docs/api/public-api/fql/)). Since the `received_at` is a top-level field in the payload, you'll need to create a destination filter with the Public API, and submit the request with that FQL information described below.
+This migration strategy involves configuring a destination filter on both the Classic destination and the Actions destination. Configure the classic destination filter to block events by the `received_at` field with a certain value, and the Actions destination to drop events until the `received_at` timestamp field reaches that same value. Destination Filters within the UI have a limitation where they cannot access any top-level fields, but this is not a limitation for [Destination Filters](https://docs.segmentapis.com/tag/Destination-Filters/){:target="_blank”} created by the [Public API](https://segment.com/docs/api/public-api/){:target="_blank”} using [FQL](https://segment.com/docs/api/public-api/fql/){:target="_blank”}. Because the `received_at` is a top-level field in the payload, you'll need to create a destination filter with the Public API and submit the request with that FQL information described below.
 
-The idea behind combining these Filters is that events will send through the Classic integration up until a specified time, and then they’ll be blocked after that time. Then the Actions integration will block events until that specified time, and only allow events beginning at that specified time.
+By combining these Filters, Segment sends events through the Classic integration up until a specified time and then blocks events after that time. Then the Actions integration blocks events until that specified time, and only allows events beginning at that specified time.
 
-Classic Destination's Destination Filter : Public API - [Create Filter for Destination]([url](https://docs.segmentapis.com/tag/Destination-Filters#operation/createFilterForDestination))
-ENDPOINT : `POST` `https://api.segmentapis.com/destination/classic_destination_id_from_url/filters`
+The following code samples show you how you can create filters for your destinations using the [Create Filter for Destination](https://docs.segmentapis.com/tag/Destination-Filters#operation/createFilterForDestination){:target="_blank”} Public API operation.
+
+#### Classic destination
+_Endpoint_: `POST` `https://api.segmentapis.com/destination/classic_destination_id_from_url/filters`
 ``` 
 // JSON BODY : 
 {
@@ -107,8 +110,8 @@ ENDPOINT : `POST` `https://api.segmentapis.com/destination/classic_destination_i
 }
 ```
 
-Actions Destination's Destination Filter : Public API - [Create Filter for Destination]([url](https://docs.segmentapis.com/tag/Destination-Filters#operation/createFilterForDestination))
-ENDPOINT : `POST` `https://api.segmentapis.com/destination/actions_destination_id_from_url/filters`
+#### Actions destination
+_Endpoint_: `POST` `https://api.segmentapis.com/destination/actions_destination_id_from_url/filters`
 ```
 // JSON BODY :
 {
@@ -126,7 +129,7 @@ ENDPOINT : `POST` `https://api.segmentapis.com/destination/actions_destination_i
 }
 ```
 
-Once the Destination Filter is configured on both the Classic and Actions destination, visit each destination's Filter's tab and enable the filters. Once the migration is complete, you can disable the Classic destination on its Settings page, and remove each of the filters from both destinations.
+After configuring the Destination Filter on both the Classic and Actions destination, see each destination's Filters tab and enable the filters. After completing the migration, you can disable the Classic destination on the Settings page, and remove each of the filters from both destinations.
 
 ## Edit a destination action
 You can add or remove, disable and re-enable, and rename individual actions from the Actions tab on the destination's information page in the Segment app. Click an individual action to edit it.