Updates from writer

Author: v-lianna

support/windows-server/windows-security/kerberos-event-4-access-denied.md

@@ -1,18 +1,17 @@
 ---
 title: Kerberos SPN is on wrong account
 description: Fixes an issue where users fail to access a resource and a System event log shows Kerberos event 4.
-ms.date: 12/26/2023
+ms.date: 01/03/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
-ms.reviewer: kaushika
+ms.reviewer: kaushika, kupatel
 ms.custom: sap:Windows Security Technologies\Kerberos authentication, csstroubleshoot
 ---
 # Kerberos Service Principal Name on Wrong Account
 
 This article provides help to solve an issue where users fail to access a resource and a System event log shows Kerberos event 4.
 
-_Applies to:_   *Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025*  
 _Original KB number:_   2706695
 
 ## Symptoms
@@ -33,7 +32,7 @@ To resolve this issue, the service principal name must be searched for and remov
 
 1. At an elevated command prompt and using Enterprise Administrator credentials, run the command `setspn -Q <SPN>`. This will return a computer name. SetSPN.exe is installed with the Active Directory Directory Services role or with RSAT.
 2. Remove the incorrectly registered SPN by going to the command prompt and running the command `setspn -D <SPN> <computername>`.
-1. Add the SPN to the correct account at the command prompt by running the command `setspn -S <SPN> <computername of computer which had the System event 4>`.
+3. Add the SPN to the correct account at the command prompt by running the command `setspn -S <SPN> <computername of computer which had the System event 4>`.
 
 ## More information