Feedback update - clarify migration API is for Replica Of migration status

Author: rrelledge

content/operate/rs/references/rest-api/requests/migrations/_index.md

@@ -5,7 +5,7 @@ categories:
 - docs
 - operate
 - rs
-description: REST API request to get the migration status of a database in the cluster.
+description: REST API request to get the migration status of a database in the cluster when using Replica Of.
 headerRange: '[1-2]'
 hideListLinks: true
 linkTitle: migrations
@@ -22,7 +22,7 @@ weight: $weight
 GET /v1/migrations/<uid>
 ```
 
-Gets the migration status of a database in the cluster.
+Gets the migration status of a database in the cluster when using Replica Of.
 
 #### Required permissions
 

content/operate/rs/release-notes/rs-7-22-releases/rs-7-22-0-28.md

@@ -88,7 +88,7 @@ This version offers:
 
     - `PUT /v1/bdbs/<uid>/actions/revamp?dry_run=true` replaces the deprecated request to [optimize shards placement]({{<relref "/operate/rs/references/rest-api/requests/bdbs/actions/optimize_shards_placement">}}).
 
-- [Migration status REST API request]({{<relref "/operate/rs/references/rest-api/requests/migrations">}}), which reports the migration status of a database in the cluster.
+- [Migration status REST API request]({{<relref "/operate/rs/references/rest-api/requests/migrations">}}), which reports the migration status of a database in the cluster when using Replica Of.
 
 - Added `secondary_rack_id` to bootstrap and node configuration to support [two-dimensional rack awareness]({{<relref "/operate/rs/clusters/configure/rack-zone-awareness#set-up-two-dimensional-rack-zone-awareness">}}).