From badcd303c93f54c8a709000e5bebf0c6b9c19fd8 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Mon, 16 Jul 2018 16:06:53 -0700 Subject: [PATCH] removed success sentence --- .../threat-protection/auditing/audit-account-lockout.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/auditing/audit-account-lockout.md b/windows/security/threat-protection/auditing/audit-account-lockout.md index 3683fa438c..831cb9ee9c 100644 --- a/windows/security/threat-protection/auditing/audit-account-lockout.md +++ b/windows/security/threat-protection/auditing/audit-account-lockout.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library author: Mir0sh -ms.date: 04/19/2017 +ms.date: 07/16/2018 --- # Audit Account Lockout @@ -19,7 +19,7 @@ ms.date: 04/19/2017 Audit Account Lockout enables you to audit security events that are generated by a failed attempt to log on to an account that is locked out. -If you configure this policy setting, an audit event is generated when an account cannot log on to a computer because the account is locked out. Success audits record successful attempts and failure audits record unsuccessful attempts. +If you configure this policy setting, an audit event is generated when an account cannot log on to a computer because the account is locked out. Account lockout events are essential for understanding user activity and detecting potential attacks.