diff --git a/modules/hcp-np-capacity-blocks-destroy.adoc b/modules/hcp-np-capacity-blocks-destroy.adoc
index edf26d177fa3..dbab9637ea55 100644
--- a/modules/hcp-np-capacity-blocks-destroy.adoc
+++ b/modules/hcp-np-capacity-blocks-destroy.adoc
@@ -3,13 +3,14 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="hcp-np-capacity-blocks-destroy_{context}"]
-= Destroying a hosted cluster after configuring node pool capacity blocks
+= Deleting a hosted cluster after configuring node pool capacity blocks
 
-After you configured node pool capacity blocks, you can optionally destroy a hosted cluster and uninstall the HyperShift Operator.
+[role="_abstract"]
+After you configured node pool capacity blocks, you can optionally delete a hosted cluster and uninstall the HyperShift Operator.
 
 .Procedure
 
-. To destroy a hosted cluster, run the following example command:
+. To delete a hosted cluster, run the following example command:
 +
 [source,terminal]
 ----
diff --git a/modules/hcp-np-capacity-blocks.adoc b/modules/hcp-np-capacity-blocks.adoc
index 2d5acea4a8dd..eb10a54921cb 100644
--- a/modules/hcp-np-capacity-blocks.adoc
+++ b/modules/hcp-np-capacity-blocks.adoc
@@ -5,7 +5,8 @@
 [id="hcp-np-capacity-blocks_{context}"]
 = Configuring node pool capacity blocks on {aws-short}
 
-After creating a hosted cluster, you can configure node pool capacity blocks for graphics processing unit (GPU) reservations on {aws-first}.
+[role="_abstract"]
+After you create a hosted cluster, you can configure node pool capacity blocks for graphics processing unit (GPU) reservations on {aws-first}.
 
 .Procedure
 
@@ -19,32 +20,34 @@ The zone of the GPU reservation must match your hosted cluster zone.
 [source,terminal]
 ----
 $ aws ec2 describe-capacity-block-offerings \
-      --instance-type "p4d.24xlarge"\ #<1>
-      --instance-count  "1" \ #<2>
-      --start-date-range "$(date -u +"%Y-%m-%dT%H:%M:%SZ")"  \ #<3>
-      --end-date-range "$(date -u -d "2 day" +"%Y-%m-%dT%H:%M:%SZ")" \ #<4>
-      --capacity-duration-hours 24 \ #<5>
+      --instance-type "p4d.24xlarge"\
+      --instance-count  "1" \
+      --start-date-range "$(date -u +"%Y-%m-%dT%H:%M:%SZ")"  \
+      --end-date-range "$(date -u -d "2 day" +"%Y-%m-%dT%H:%M:%SZ")" \
+      --capacity-duration-hours 24 \
       --output json
 ----
-<1> Defines the type of your {aws-short} instance, for example, `p4d.24xlarge`.
-<2> Defines your instance purchase quantity, for example, `1`. Valid values are integers ranging from `1` to `64`.
-<3> Defines the start date range, for example, `2025-07-21T10:14:39Z`.
-<4> Defines the end date range, for example, `2025-07-22T10:16:36Z`.
-<5> Defines the duration of capacity blocks in hours, for example, `24`.
++
+* `--instance-type` defines the type of your {aws-short} instance, for example, `p4d.24xlarge`.
+* `--instance-count` defines your instance purchase quantity, for example, `1`. Valid values are integers ranging from `1` to `64`.
+* `--start-date-range` defines the start date range, for example, `2025-07-21T10:14:39Z`.
+* `--end-date-range` defines the end date range, for example, `2025-07-22T10:16:36Z`.
+* `--capacity-duration-hours` defines the duration of capacity blocks in hours, for example, `24`.
 
 . Purchase the minimum fee capacity block by running the following command:
 +
 [source,terminal]
 ----
 $ aws ec2 purchase-capacity-block \
-      --capacity-block-offering-id "${MIN_FEE_ID}" \ #<1>
-      --instance-platform "Linux/UNIX"\ #<2>
-      --tag-specifications 'ResourceType=capacity-reservation,Tags=[{Key=usage-cluster-type,Value=hypershift-hosted}]' \ #<3>
+      --capacity-block-offering-id "${MIN_FEE_ID}" \
+      --instance-platform "Linux/UNIX"\
+      --tag-specifications 'ResourceType=capacity-reservation,Tags=[{Key=usage-cluster-type,Value=hypershift-hosted}]' \
       --output json   > "${CR_OUTPUT_FILE}"
 ----
-<1> Defines the ID of the capacity block offering.
-<2> Defines the platform of your instance.
-<3> Defines the tag for your instance.
++
+* `--capacity-block-offering-id` defines the ID of the capacity block offering.
+* `--instance-platform` defines the platform of your instance.
+* `--tag-specifications` defines the tag for your instance.
 
 . Create an environment variable to set the capacity reservation ID by running the following command:
 +
@@ -60,20 +63,21 @@ Wait for a couple of minutes for the GPU reservation to become available.
 [source,terminal]
 ----
 $ hcp create nodepool aws \
-  --cluster-name <hosted_cluster_name> \ #<1>
-  --name <node_pool_name> \ #<2>
-  --node-count 1 \ #<3>
-  --instance-type p4d.24xlarge \ #<4>
-  --arch amd64 \ #<5>
-  --release-image <release_image> \ #<6>
+  --cluster-name <hosted_cluster_name> \
+  --name <node_pool_name> \
+  --node-count 1 \
+  --instance-type p4d.24xlarge \
+  --arch amd64 \
+  --release-image <release_image> \
   --render > /tmp/np.yaml
 ----
-<1> Replace `<hosted_cluster_name>` with the name of your hosted cluster.
-<2> Replace `<node_pool_name>` with the name of your node pool.
-<3> Defines the node pool count, for example, `1`.
-<4> Defines the instance type, for example, `p4d.24xlarge`.
-<5> Defines an architecture type, for example, `amd64`.
-<6> Replace `<release_image>` with the release image you want to use.
++
+* `--cluster-name` specifies the name of your hosted cluster.
+* `--name` specifies the name of your node pool.
+* `--node-count` defines the node pool count, for example, `1`.
+* `--instance-type` defines the instance type, for example, `p4d.24xlarge`.
+* `--arch` defines an architecture type, for example, `amd64`.
+* `--release-image` specifies the release image you want to use.
 
 . Add the `capacityReservation` setting in your `NodePool` resource by using the following example configuration:
 +