diff --git a/modules/nw-nodeport-service-range-edit.adoc b/modules/nw-nodeport-service-range-edit.adoc
index bb3112ce9f50..139adc63c47c 100644
--- a/modules/nw-nodeport-service-range-edit.adoc
+++ b/modules/nw-nodeport-service-range-edit.adoc
@@ -6,11 +6,11 @@
 [id="nw-nodeport-service-range-edit_{context}"]
 = Expanding the node port range
 
-You can expand the node port range for your cluster. However, after you install your {product-title} cluster, you cannot contract the node port range on either side.
+You can expand the node port range for your cluster. After you install your {product-title} cluster, you cannot shrink the node port range on either side of the currently configured range.
 
 [IMPORTANT]
 ====
-Before you expand a node port range, consider that Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify the expanding node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it. 
+Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify that expanding your node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it.
 ====
 
 .Prerequisites
@@ -21,17 +21,22 @@ Before you expand a node port range, consider that Red{nbsp}Hat has not performe
 
 .Procedure
 
-* Expand the range for the `serviceNodePortRange` parameter in the `network.config.openshift.io` object that your cluster uses to manage traffic for pods by entering the following command in your command-line interface (CLI):
+* To expand the range for the `serviceNodePortRange` parameter in the `network.config.openshift.io` object that your cluster uses to manage traffic for pods, enter the following command:
 +
 [source,terminal]
 ----
 $ oc patch network.config.openshift.io cluster --type=merge -p \
   '{
     "spec":
-      { "serviceNodePortRange": "<port_range>" } <1>
+      { "serviceNodePortRange": "<port_range>" }
   }'
 ----
-<1> Where `<port_range>` is your expanded range, such as `30000-32900`.
++
+--
+where:
+
+`<port_range>`:: specifies your expanded range, such as `30000-32900`.
+--
 +
 [TIP]
 ====
@@ -57,7 +62,7 @@ network.config.openshift.io/cluster patched
 
 .Verification
 
-* To confirm a successful configuration, enter the following command. The update can take several minutes to apply.
+* To confirm that the updated configuration is active, enter the following command. The update can take several minutes to apply.
 +
 [source,terminal]
 ----
diff --git a/networking/configuring_network_settings/configuring-node-port-service-range.adoc b/networking/configuring_network_settings/configuring-node-port-service-range.adoc
index aa35474f5eb7..bbc859923334 100644
--- a/networking/configuring_network_settings/configuring-node-port-service-range.adoc
+++ b/networking/configuring_network_settings/configuring-node-port-service-range.adoc
@@ -8,17 +8,18 @@ toc::[]
 
 During cluster installation, you can configure the node port range to meet the requirements of your cluster. After cluster installation, only a cluster administrator can expand the range as a postinstallation task. If your cluster uses a large number of node ports, consider increasing the available port range according to the requirements of your cluster.
 
-[IMPORTANT]
-====
-Before you expand a node port range, consider that Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify the expanding node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it.
-====
-
 If you do not set a node port range during cluster installation, the default range of `30000-32768` applies to your cluster. In this situation, you can expand the range on either side, but you must preserve `30000-32768` within your new port range.
 
 [IMPORTANT]
 ====
-If you expand the node port range and {oc-first} stops working because of a port conflict with the OpenShift API server, you must create a new cluster.
-Ensure that the new node port range does not overlap with any ports already in use by host processes or pods that are configured with host networking.
+Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify the expanding node port range does not impact your cluster. In particular, ensure that there is:
+
+- No overlap with any ports already in use by host processes
+- No overlap with any ports already in use by pods that are configured with host networking
+
+If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it.
+
+If you expand the node port range and {oc-first} stops working because of a port conflict with the {product-title} API server, you must create a new cluster.
 ====
 
 // Expanding the node port range