Skip to content

Fix typos and improve wording in documentation#1891

Open
yves-steve wants to merge 3 commits intoMicrosoftDocs:mainfrom
yves-steve:patch-1
Open

Fix typos and improve wording in documentation#1891
yves-steve wants to merge 3 commits intoMicrosoftDocs:mainfrom
yves-steve:patch-1

Conversation

@yves-steve
Copy link
Copy Markdown

This pull request makes several improvements to the documentation for deploying phishing-resistant passwordless authentication, focusing primarily on clarity, grammar, and consistency. The changes aim to enhance readability and ensure the guidance is accurate and easy to follow.

Improvements to clarity and grammar:

  • Improved phrasing and corrected grammar throughout the document, such as changing "communicating to users" to "communicating with users," and clarifying report descriptions for registration and sign-in activities.
  • Updated section titles and descriptions for enforcement steps and Conditional Access policies to use consistent terminology and correct spelling errors. [1] [2]

Consistency and accuracy enhancements:

  • Standardized language for risk descriptions and policy recommendations, including correcting "high risk users" to "high-risk users**" and improving descriptions of activities detected by Microsoft Entra ID Protection. [1] [2]

Copilot AI review requested due to automatic review settings February 21, 2026 12:41
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request makes minor documentation improvements to fix typos, grammar issues, and improve clarity in the phishing-resistant passwordless authentication deployment guide. The changes enhance readability and ensure consistent terminology throughout the document.

Changes:

  • Fixed spelling errors (e.g., "resistence" → "resistance", "crednetials" → "credentials", "Microsfot" → "Microsoft")
  • Improved grammar and phrasing (e.g., "communicating to users" → "communicating with users", added proper articles)
  • Standardized terminology and hyphenation (e.g., "sign in" → "sign-in" in adjective contexts, "high risk users" → "high-risk users")

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 8178f90:

⚠️ Validation status: warnings

File Status Preview URL Details
docs/identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md ⚠️Warning Details

docs/identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md

  • Line 28, Column 52: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#step-4-enforcement-of-phishing-resistence-on-resources' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#step-4-enforcement-of-phishing-resistance-on-resources'?
  • Line 66, Column 342: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#step-4-enforcement-of-phishing-resistence-on-resources' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#step-4-enforcement-of-phishing-resistance-on-resources'?
  • Line 236, Column 194: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#recommended-enforcement-conditional-access-policies' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#recommended-enforcement-of-conditional-access-policies'?

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@ttorble
Copy link
Copy Markdown
Contributor

ttorble commented Feb 23, 2026

@yves-steve Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!

@yves-steve
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@prmerger-automator
Copy link
Copy Markdown
Contributor

@yves-steve : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 425c0a6:

⚠️ Validation status: warnings

File Status Preview URL Details
docs/identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md ⚠️Warning Details

docs/identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md

  • Line 28, Column 52: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#step-4-enforcement-of-phishing-resistence-on-resources' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#step-4-enforcement-of-phishing-resistance-on-resources'?
  • Line 66, Column 342: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#step-4-enforcement-of-phishing-resistence-on-resources' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#step-4-enforcement-of-phishing-resistance-on-resources'?
  • Line 236, Column 194: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#recommended-enforcement-conditional-access-policies' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#recommended-enforcement-of-conditional-access-policies'?

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 1952800:

⚠️ Validation status: warnings

File Status Preview URL Details
docs/identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md ⚠️Warning Details

docs/identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md

  • Line 28, Column 52: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#step-4-enforcement-of-phishing-resistence-on-resources' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#step-4-enforcement-of-phishing-resistance-on-resources'?
  • Line 66, Column 342: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#step-4-enforcement-of-phishing-resistence-on-resources' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#step-4-enforcement-of-phishing-resistance-on-resources'?
  • Line 236, Column 194: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#recommended-enforcement-conditional-access-policies' in 'identity/authentication/how-to-deploy-phishing-resistant-passwordless-authentication.md', did you mean '#recommended-enforcement-of-conditional-access-policies'?

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@ttorble
Copy link
Copy Markdown
Contributor

ttorble commented Mar 2, 2026

@Sipower

Can you review the proposed changes? Note that the bookmark warnings will need to be resolved before the PR can be merged. Thanks!

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants