Apply code review suggestions

Author: dwdougherty

content/commands/cluster-countkeysinslot.md

@@ -34,7 +34,8 @@ command only queries the local data set, so contacting a node
 that is not serving the specified hash slot will always result in a count of
 zero being returned.
 
-**Note:** During atomic slot migration operations (available since Redis 8.4.0), keys being imported or trimmed may be filtered out from the results.
+{{< note>}}During atomic slot migration operations (available since Redis 8.4.0), keys being imported or trimmed may be filtered out from the results.
+{{< /note >}}
 
 ```
 > CLUSTER COUNTKEYSINSLOT 7000

content/commands/cluster-getkeysinslot.md

@@ -44,7 +44,8 @@ node to another. The way the rehashing is performed is exposed in the Redis
 Cluster specification, or in a more simple to digest form, as an appendix
 of the [`CLUSTER SETSLOT`]({{< relref "/commands/cluster-setslot" >}}) command documentation.
 
-**Note:** During atomic slot migration operations (available since Redis 8.4.0), keys being imported or trimmed may be filtered out from the results.
+{{< note >}}During atomic slot migration operations (available since Redis 8.4.0), keys being imported or trimmed may be filtered out from the results.
+{{< /note >}}
 
 ```
 > CLUSTER GETKEYSINSLOT 7000 3

content/commands/cluster-migration.md

@@ -81,7 +81,7 @@ The `CLUSTER MIGRATION` command provides atomic slot migration functionality for
 
 The subcommand specifies the operation to perform:
 
-- `IMPORT <start-slot> <end-slot> [<start-slot> <end-slot> ...]`: Executes on the destination master. Accepts multiple slot ranges and triggers atomic migration for the specified ranges. Returns a task ID that can be used to monitor the status of the task.
+- `IMPORT <start-slot> <end-slot> [<start-slot> <end-slot> ...]`: Executes on the destination master. Accepts multiple slot ranges and triggers atomic migration for the specified ranges. Returns a task ID that you can use to monitor the status of the task.
 
 - `CANCEL [ID <task-id> | ALL]`: Cancels an ongoing migration task by its ID or cancels all tasks if `ALL` is specified. Note: Cancelling a task on the source node does not stop the migration on the destination node, which will continue retrying until it is also cancelled there.