From 99acc3dc24a8b69e4599f1687c255f0ab2d51e7b Mon Sep 17 00:00:00 2001
From: VLG17 <41186174+VLG17@users.noreply.github.com>
Date: Mon, 12 Apr 2021 21:27:03 +0300
Subject: [PATCH] Update
 windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md

Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
---
 ...ogons-to-cache-in-case-domain-controller-is-not-available.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md b/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md
index 6ae308d67b..1e1a6c2d56 100644
--- a/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md
+++ b/windows/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available.md
@@ -43,7 +43,7 @@ Users who access the server console will have their logon credentials cached on
 encrypting the information and keeping the cached credentials in the system's registries, which are spread across numerous physical locations.
 
 > [!NOTE]
-> The cached account information does not expire, but can get overwritten, as described previously.
+> The cached account information does not expire, but can get overwritten, as previously described.
 
 ### Possible values