From 55d6af8834762bc5ea016c8e153d39bba95e5545 Mon Sep 17 00:00:00 2001
From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com>
Date: Fri, 21 Aug 2020 09:20:07 +0500
Subject: [PATCH] Update
 windows/security/threat-protection/security-policy-settings/accounts-administrator-account-status.md

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../accounts-administrator-account-status.md                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/security-policy-settings/accounts-administrator-account-status.md b/windows/security/threat-protection/security-policy-settings/accounts-administrator-account-status.md
index b9ee489d84..242f47b39f 100644
--- a/windows/security/threat-protection/security-policy-settings/accounts-administrator-account-status.md
+++ b/windows/security/threat-protection/security-policy-settings/accounts-administrator-account-status.md
@@ -87,7 +87,7 @@ When you start a device in safe mode, the disabled administrator account is enab
 
 You can use the following methods to access a disabled Administrator account:
 -   For non-domain joined computers: when all the local administrator accounts are disabled, start the device in safe mode (locally or over a network), and sign in by using the credentials for the default local administrator account on that computer. 
--   For domain joined computers: remotely run the command **net user administrator /active: yes** by using psexec to enable the default local administrator account.
+-   For domain-joined computers: remotely run the command **net user administrator /active: yes** by using psexec to enable the default local administrator account.
 
 ## Security considerations