Merge main to live - 11/2/23 #864
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In this commit, the ‘What’s in it for me?’ section has been revised for better clarity and engagement. The changes highlight the benefits users receive when they contribute to Microsoft Learn. These include recognition of their contributions, enhancement of their tech passion, and portfolio building. The update also emphasizes the digital rewards some products offer. The aim is to encourage more users to contribute and enjoy the benefits.
Modified the ‘What’s in it for me?’ section for clarity and engagement.
carlyrevier
requested review from
Jim-Parker,
jehchow and
Kiranchandratrey
as code owners
|
#sign-off |
jehchow
approved these changes
Nov 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributor guide pull request
Thanks for contributing to the Microsoft Learn contributor guide. Please read these instructions for processing your pull request (PR). Once you've read this text, delete it and write a brief description of the changes you're proposing.
Quality control
1. Successful build with no warnings: Review the build status to make sure all checks are green (Succeeded).
2. #Sign-off: Once the PR is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the PR. Signing off means the document is ready for review and can be published at any time.Merge and publish
Need help?
@carlyrevier, @jehchow