diff --git a/windows/client-management/troubleshoot-tcpip-port-exhaust.md b/windows/client-management/troubleshoot-tcpip-port-exhaust.md
index 10fbfe6f45..a09a0c7ea4 100644
--- a/windows/client-management/troubleshoot-tcpip-port-exhaust.md
+++ b/windows/client-management/troubleshoot-tcpip-port-exhaust.md
@@ -82,13 +82,13 @@ If you suspect that the machine is in a state of port exhaustion:
 
 2. Open event viewer and under the system logs, look for the events which clearly indicate the current state: 
 
-    a.	**Event ID 4227**
+    1. **Event ID 4227**
 
-    ![Screenshot of event id 4227 in Event Viewer.](images/tcp-ts-18.png)
+       ![Screenshot of event id 4227 in Event Viewer.](images/tcp-ts-18.png)
 
-    b.	**Event ID 4231**
+    1. **Event ID 4231**
 
-    ![Screenshot of event id 4231 in Event Viewer.](images/tcp-ts-19.png)
+       ![Screenshot of event id 4231 in Event Viewer.](images/tcp-ts-19.png)
 
 3. Collect a `netstat -anob` output from the server. The netstat output will show you a huge number of entries for TIME_WAIT state for a single PID.