Update known issues and remediation steps for hotpatch

Clarified language regarding Windows Server hotpatching issues and updated instructions for registry modifications and PowerShell commands.

Author: pronichkin

WindowsServerDocs/get-started/enable-hotpatch-azure-arc-enabled-servers.md

@@ -142,11 +142,11 @@ You can optionally automate hotpatch installation using update management tools
 
 ### Multiple updates released in October 2025
 
-In October 2025, Microsoft had to release several updates, which might be offered to some Windows Server customers. If you enrolled in hotpatch or plan to enroll, and plan to install hotpatch updates in November and December 2025, please make sure your Windows Server instances are running **exactly** [October 14, 2025—KB5066835 (OS Build 26100.6899)](https://support.microsoft.com/topic/6cdcc1c3-cfbf-41a3-8f0d-0c4a9d2b7d1e).
+In October 2025, Microsoft had to release several updates, which might be offered to some Windows Server customers. If you enrolled in hotpatch or plan to enroll, and plan to install hotpatch updates in November and December 2025, please make sure your Windows Server machine(s) are running **exactly** [October 14, 2025—KB5066835 (OS Build 26100.6899)](https://support.microsoft.com/topic/6cdcc1c3-cfbf-41a3-8f0d-0c4a9d2b7d1e).
 
 Running a different build number (higher or lower than specified above) will result in regular (non-hotpatch) updates until (and including) the next baseline month, which is currently scheduled for January 2026. These updates will require a reboot each month.
 
-### Feature licensing issue in October 2025
+### Feature licensing issue in October 2025 updates
 
 An issue has been identified with October 2025 security updates for Windows Server 2025. This may impact customers running [October 14, 2025—KB5066835 (OS Build 26100.6899)](https://support.microsoft.com/topic/6cdcc1c3-cfbf-41a3-8f0d-0c4a9d2b7d1e) or later. Due to this issue, the following unexpected behavior can be observed.
 1.	Enabling Windows Server hotpatching via Azure Arc on new machines may fail or not complete as expected. Instead, feature enablement will remain in the “in progress” state until the issue is resolved.
@@ -167,11 +167,11 @@ Once either of the following workarounds is applied, subsequent hotpatches (in N
 ](/troubleshoot/windows-client/group-policy/use-group-policy-enable-update-disabled-by-default).
 3. Set the **KB5062660 251028_18301 Feature Preview** policy to **Enabled** state via either Local or Group Policy.
 4. Once the policy is applied, reboot the affected machine(s).
-5. Delete the **DeviceLicensingServiceCommandMutex** value found under **HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Subscriptions**.
+5. Delete the **DeviceLicensingServiceCommandMutex** value found under **HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Subscriptions** registry key.
 
 #### Option 2. Use a script to enable the remediation
 
-Run the following series of PowerShell commands on each of the affected machines. Note that the last command will prompt for a restart. The mitigation is not complete until the machine is rebooted, and we recommend that you restart immediately after the previous steps in the script are performed.
+Run the following series of PowerShell commands as administrator on each of the affected machines. Note that the last command will prompt for a restart. The mitigation is not complete until the machine is rebooted, and we recommend that you restart immediately after the previous commands are executed.
 ```PowerShell
 Stop-Service -Name 'himds'
 New-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides' -PropertyType 'dword' -Name '4264695439' -Value 1 -Force