From e99740d6ea41511e19f3648c31a3c2b3f856b47d Mon Sep 17 00:00:00 2001
From: hiromi-shindo <54097091+hiromi-shindo@users.noreply.github.com>
Date: Wed, 14 Aug 2019 16:49:42 +0900
Subject: [PATCH] Update domain-member-maximum-machine-account-password-age.md

The previous request modifies the value of MaximumPasswordAge, but docs still discuss value of 0.
---
 .../domain-member-maximum-machine-account-password-age.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/security-policy-settings/domain-member-maximum-machine-account-password-age.md b/windows/security/threat-protection/security-policy-settings/domain-member-maximum-machine-account-password-age.md
index b4f0324679..526925b58c 100644
--- a/windows/security/threat-protection/security-policy-settings/domain-member-maximum-machine-account-password-age.md
+++ b/windows/security/threat-protection/security-policy-settings/domain-member-maximum-machine-account-password-age.md
@@ -76,7 +76,7 @@ This section describes how an attacker might exploit a feature or its configurat
 
 ### Vulnerability
 
-By default, the domain members submit a password change every 30 days. If you increase this interval significantly, or set it to 0 so that the computers no longer submit a password change, an attacker has more time to undertake a brute-force attack to guess the password of one or more computer accounts.
+By default, the domain members submit a password change every 30 days. If you increase this interval significantly, or set it to 1 so that the computers no longer submit a password change, an attacker has more time to undertake a brute-force attack to guess the password of one or more computer accounts.
 
 ### Countermeasure