Apply suggestions from code review

Author: v-dihans

windows-365/business-enterprise-comparison.md

@@ -55,7 +55,7 @@ Windows 365 is available in two editions: [Windows 365 Business](./business/inde
 | Provisioning | Provisioning is simplified and uses default configurations.<br>Cloud PCs are automatically provisioned with a standard image after a Cloud PC license is assigned. | Provisioning is configurable and customizable to the needs of the organization.<br>Admins select the network, configure user permissions (local admin or not), and assign the policy to an Azure AD group.<br>Cloud PCs are then provisioned by using standard gallery images or custom images (admin choice). |
 | Policy management | Not Supported. | Group Policy Objects (GPO) and Intune MDM are supported. |
 | Application deployment | Supported only if you have Intune license. | Supported. |
-| Windows updates | Default Windows Update for Business settings are configured for users. With an Intune license, these settings an be edited. | Can be managed by using Microsoft Endpoint Manager. |
+| Windows updates | Default Windows Update for Business settings are configured for users. With an Intune license, these settings can be edited. | Can be managed by using Microsoft Endpoint Manager. |
 | Device management | Device management is limited to assigning and unassigning of Cloud PC licenses in the Microsoft Admin Center. Some device management is possible in Microsoft Endpoint Manager if you have an Intune license but Cloud PCs won't be visible in the Windows 365 blade. | Microsoft Endpoint Manager admin center options, including image management, link and access on-premises resources, granular targeting of policies, resizing Cloud PCs, other user experience settings, and all the policy-based management options available to physical devices. |
 | Monitoring | Not supported. | Endpoint Analytics reporting and monitoring, service health, and operational health alerts. |
 | Troubleshooting | Not supported | Microsoft Endpoint Manager troubleshooting including the Troubleshooting blade, device management actions, and reprovisioning of Cloud PCs to their initial state. |

windows-365/enterprise/on-premises-network-connections.md

@@ -129,5 +129,6 @@ For Azure AD Join OPNCs, the OPNC is used to route the authentication request to
 <!-- ########################## -->
 ## Next steps
 
-[Learn about device images](device-images.md).
+[Learn about device images](device-images.md)
+
 [Create an on-premises network connection](create-on-premises-network-connection.md)

windows-365/enterprise/overview.md

@@ -49,6 +49,7 @@ With the Windows 365 service, you can:
 - Manage your Cloud PCs like your organization’s other devices in [Microsoft Endpoint Manager](/intune/). Based on your configuration, Cloud PCs are either:
   - Joined to your enterprise Active Directory domain and synced to Azure AD.
   - Directly joined to Azure AD.
+  
   Regardless of the join type, your Cloud PCs are fully managed by Microsoft Endpoint Manager. Windows 365 is fully integrated into the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). Cloud PCs are seamlessly managed in Microsoft Endpoint Manager like any other supported device, including configuration, apps, and updates.
 - [Configure provisioning policies](create-provisioning-policy.md) to create custom Cloud PC configurations.
 - Use device groups, policies, and security baselines to customize your Cloud PC configurations to support different user needs.