Skip to content

Commit 2d4ad6c

Browse files
committed
consistency fixes
1 parent 03e5fe3 commit 2d4ad6c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/standards/memo-22-09-multi-factor-authentication.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Consider the following approach to evaluating phishing-resistant MFA methods:
4141

4242
* Device types and capabilities that you want to support. Examples include kiosks, laptops, mobile phones, biometric readers, USB, Bluetooth, and near-field communication devices.
4343

44-
* User personas within your organization. Examples include front-line workers, remote workers with and without company-owned hardware, administrators with privileged access workstation, and business-to-business guest users.
44+
* User personas within your organization. Examples include front-line workers, remote workers with and without company-owned hardware, administrators with privileged access workstations, and business-to-business guest users.
4545

4646
* Logistics of distributing, configuring, and registering MFA methods such as FIDO2 security keys, smart cards, government-furnished equipment, or Windows devices with TPM chips.
4747

@@ -51,7 +51,7 @@ Consider the following approach to evaluating phishing-resistant MFA methods:
5151

5252
The following sections describe support for implementing phishing-resistant methods for both application and virtual device sign-in scenarios.
5353

54-
### Application sign-in scenarios from different clients
54+
### Application sign-in scenarios from various clients
5555

5656
The following table details the availability of phishing-resistant MFA scenarios, based on the device type that's used to sign in to the applications:
5757

@@ -102,7 +102,7 @@ The memo requires organizations to change password policies that are proven inef
102102

103103
* Use [Azure AD Identity Protection](..//identity-protection/concept-identity-protection-risks.md) to be alerted about compromised credentials so you can take immediate action.
104104

105-
While the memo isn't specific on which policies to use with passwords, consider the standard from [NIST 800-63B](https://pages.nist.gov/800-63-3/sp800-63b.html).
105+
Although the memo isn't specific on which policies to use with passwords, consider the standard from [NIST 800-63B](https://pages.nist.gov/800-63-3/sp800-63b.html).
106106

107107
## Next steps
108108

0 commit comments

Comments
 (0)