Skip to content

Commit 3894616

Browse files
authored
Update device-management-overview.md
1 parent 6bf4137 commit 3894616

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

windows-365/enterprise/device-management-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,11 +81,11 @@ If a user has multiple Windows 365 SKUs assigned to them, they’ll get multiple
8181
If the grace period was triggered in error, you have seven days to resolve the breaking change to get the Cloud PC switched back to **Provisioned**.
8282

8383
You can manually end the grace period by using the [End grace period](end-grace-period.md) option.
84-
- **Pending**: A Cloud PC will marked Pending if there are not enough available licenses in your tenant to process the provisioning request.
84+
- **Pending**: If there are not enough available licenses in your tenant to process the provisioning request, new Cloud PCs are marked as **Pending**.
8585

86-
Your Windows 365 tenant can only have as many active Cloud PC's as the license allocation allows. An active Cloud PC can either be in a Provisioned or In grace period state.
86+
Your Windows 365 tenant can only have as many active Cloud PCs as the license allocation allows. An active Cloud PC can either be in a **Provisioned** or **In grace period state**.
8787

88-
To begin provisioning on Pending Cloud PC's, free up some Windows 365 licenses or end grace period on Cloud PC's in the grace period state.
88+
To begin provisioning on Pending Cloud PCs, free up some Windows 365 licenses or end grace period on Cloud PCs in the grace period state.
8989

9090
**User**: The user assigned to the Cloud PC.
9191

0 commit comments

Comments
 (0)