* Clarified that the 500 devices is per tenant and not on the service level (it's called out later on the page as well but this was the first occurrence which is the most important, assuming customers read the article from top to bottom)
* The statement "crashes and freezes" is used 3 times and "crashes or freezes" one time. I changed the "or" to "and" for consistency.
* The word "issue" is overly negative in this context, we don't want customers to think we have issues with Autopatch. I changed it to "limitation".
Added some explicit detail around what "manually" adding devices to the Test ring means. I.E follow the moving devices between rings process and not manually editing the AD group.
Regarding autopatch, adding the devices directly to the autopatch groups are unsupported and might cause unexpected impact to the service. But system allows to do so. Hence updating the docs accordingly.
Removing "Windows Autopatch deployment rings only apply to Windows quality updates" from the Important Note as we also deploy feature update policies to the same deployment ring groups @tiaraquan
Section edit for Servicing Profile. Re-labeled section to point out compatibility. Added links to Servicing Profile resources. Added intro statement for readers that are not familiar with Servicing Profiles.
Correct typo.
Original text: "Since Windows quality updates are bundled together into a single release in the Monthly Enterprise Channel, we can't roll back only a portion of the update for Microsoft 365 Apps for enterprise."
Corrected text: "Since quality updates are bundled together into a single release in the Monthly Enterprise Channel, we can't roll back only a portion of the update for Microsoft 365 Apps for enterprise."
Reason: We are talking about Office updates, not Windows updates.
