diff --git a/memdocs/configmgr/comanage/how-to-switch-workloads.md b/memdocs/configmgr/comanage/how-to-switch-workloads.md
index 80e8e8e1c4f..253ae71d1be 100644
--- a/memdocs/configmgr/comanage/how-to-switch-workloads.md
+++ b/memdocs/configmgr/comanage/how-to-switch-workloads.md
@@ -33,10 +33,11 @@ You can configure different pilot collections for each of the co-management work
     ![Screenshot of Workloads tab on co-management properties page](media/3555750-co-management-workloads-tab.png)
 
     - **Configuration Manager**: Configuration Manager continues to manage this workload.  
+    - **Pilot Intune**: Switch this workload only for the devices in the pilot collection. You can change the **Pilot collections** on the **Staging** tab of the co-management properties page.
+    - **Intune**: Switch this workload for all Windows devices enrolled in co-management.
 
-    - **Pilot Intune**: Switch this workload only for the devices in the pilot collection. You can change the **Pilot collections** on the **Staging** tab of the co-management properties page.  
-[!NOTE] When pilot Intune is selected for Endpoint Protection and Device Configuration Policies, Intune will only deploy the policies and will not perform policy removal unpon unassignment. For policy removal from the device when the policy is unassigned, the workload must be switched to Intune.
-    - **Intune**: Switch this workload for all Windows devices enrolled in co-management.  
+> [!NOTE]
+> When Pilot Intune is selected for Endpoint Protection and Device Configuration Policies, Intune will only deploy the policies and will not perform policy removal upon unassignment. For policy removal from the device when the policy is unassigned, the workload must be switched to Intune.
 
 4. Go to the **Staging** tab and change the **Pilot collection** for any of the workloads if needed.