Update service-fabric-patch-orchestration-application.md

Author: damabe

articles/service-fabric/service-fabric-patch-orchestration-application.md

@@ -273,8 +273,11 @@ The NodeAgentNTService creates [repair tasks](https://docs.microsoft.com/dotnet/
 
     [![Image of Cluster patching status](media/service-fabric-patch-orchestration-application/clusterpatchingstatus.png)](media/service-fabric-patch-orchestration-application/clusterpatchingstatus.png#lightbox)
 
+4. Once the node is disabled, the repair task is moved to Executing state.
+   
    >[!NOTE]
    > A node stuck in a disabled state can block a new repair task, which will halt the patching operation on the cluster.
+
 5. Once repair task is in executing state, the patch installation on that node begins. Here on, once the patch is installed, the node may or may not be restarted depending on the patch. Post that the repair task is moved to restoring state, which enables back the node again and then it is marked as completed.
 
    In v1.4.0 and above versions of the application, status of the update can be found by looking at the health events on NodeAgentService with property "WUOperationStatus-[NodeName]". The highlighted sections in the images below show the status of windows update on node 'poanode_0' and 'poanode_2':
@@ -482,4 +485,4 @@ An administrator must intervene and determine why the application or cluster bec
 - Changing default value of InstallWindowsOSOnlyUpdates to False.
 
 ### Version 1.3.2
-- Fixing an issue which effected the patching lifecycle on a node in case there are nodes with name which is subset of the current node name. For such nodes, its possible, patching is missed or reboot is pending. 
+- Fixing an issue which effected the patching lifecycle on a node in case there are nodes with name which is subset of the current node name. For such nodes, its possible, patching is missed or reboot is pending.