diff --git a/modules/hcp-ts-nodes-stuck.adoc b/modules/hcp-ts-nodes-stuck.adoc
index 9fe6e6ec3d..bc53549eb5 100644
--- a/modules/hcp-ts-nodes-stuck.adoc
+++ b/modules/hcp-ts-nodes-stuck.adoc
@@ -1,26 +1,24 @@
 // Module included in the following assemblies:
 //
 // * hosted_control_planes/hcp-troubleshooting.adoc
-
 :_mod-docs-content-type: PROCEDURE
 [id="hcp-ts-nodes-stuck_{context}"]
 = Worker nodes are stuck in the NotReady state
 
-During cluster creation, nodes enter the `NotReady` state temporarily while the networking stack is rolled out. This part of the process is normal. However, if this part of the process takes longer than 15 minutes, an issue might have occurred.
+During cluster creation, nodes enter the `NotReady` state temporarily while the networking stack is rolled out. This part of the process is normal. However, if this part of the process takes longer than 15 minutes, identify the problem by investigating the node object and pods.
 
 .Procedure
 
-Identify the problem by investigating the node object and pods:
-
-* Enter the following command to view the conditions on the node object and determine why the node is not ready:
+. Enter the following command to view the conditions on the node object and determine why the node is not ready:
 +
 [source,terminal]
 ----
 $ oc get nodes -o yaml
 ----
-* Enter the following command to look for failing pods within the cluster:
+
+. Enter the following command to look for failing pods within the cluster:
 +
 [source,terminal]
 ----
 $ oc get pods -A --field-selector=status.phase!=Running,status,phase!=Succeeded
-----
\ No newline at end of file
+----