Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix a few typos #1203

Open
wants to merge 1 commit into
base: public
Choose a base branch
from
Open

Conversation

Blake-Madden
Copy link

No description provided.

@officedocspr
Copy link
Collaborator

STOP Caution: Large pull request

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

  • Warning Warning message and ability to unblock PR using the Merge large pull request* label - 30
  • Block Block message and PR is blocked - 100

This pull request will change 33 files, which exceeds the warning limit of 33.

Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.

The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.

To merge this pull request

If you have determined that the changes in this pull request are correct, add the Merge large pull request* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request*.

Label UI screenshot

To reject this pull request

If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

* You must have write or triage access to this repo to add labels.

Copy link
Contributor

Learn Build status updates of commit 9545592:

⚠️ Validation status: warnings

File Status Preview URL Details
Viva/connections/viva-connections-analytics.md ⚠️Warning Details
Viva/glint/setup/advanced-config-uploads.md 💡Suggestion Details
Viva/connections/home-site-plan.md ✅Succeeded
Viva/connections/viva-connections-language.md ✅Succeeded
Viva/engage/configure-your-viva-engage-network/configure-viva-engage.md ✅Succeeded
Viva/engage/work-with-external-users/collaborate-guests-external-viva-engage-community.md ✅Succeeded
Viva/engage/work-with-external-users/external-messaging-faq.md ✅Succeeded
Viva/glint/people-science/managers-using-act-conversations.md ✅Succeeded
Viva/glint/reports/heat-map.md ✅Succeeded
Viva/glint/setup/360-report-access-timing.md ✅Succeeded
Viva/glint/setup/copilot-managers.md ✅Succeeded
Viva/glint/setup/create-onboarding-exit-surveys.md ✅Succeeded
Viva/glint/setup/diversity-inclusion.md ✅Succeeded
Viva/glint/setup/patient-safety-survey.md ✅Succeeded
Viva/glint/setup/program-summary-communications.md ✅Succeeded
Viva/glint/setup/question-library.md ✅Succeeded
Viva/glint/setup/questions-setup.md ✅Succeeded
Viva/glint/setup/quick-guide-confidentiality.md ✅Succeeded
Viva/glint/setup/reporting-setup.md ✅Succeeded
Viva/glint/setup/template-research.md ✅Succeeded
Viva/goals/check-in-reminders.md ✅Succeeded
Viva/goals/cloning-objectives.md ✅Succeeded
Viva/goals/domo-integration.md ✅Succeeded
Viva/goals/dynamics-365-integration.md ✅Succeeded
Viva/goals/ms-teams-messaging-extension.md ✅Succeeded

This comment lists only the first 25 files in the pull request.

Viva/connections/viva-connections-analytics.md

  • Line 37, Column 183: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#how-to-to-disable-analytics-features' in 'connections/viva-connections-analytics.md', did you mean '#how-to-disable-analytics-features'?

Viva/glint/setup/advanced-config-uploads.md

  • Line 15, Column 26: [Suggestion: ms-localizationpriority-invalid] Invalid value for 'ms.localizationpriority': 'high pri'. The ms.localizationpriority metadata must have one of the following values: high, medium, or low.

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.

For any questions, please:

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