--- ms.date: 10/27/2026 --- # Overview ## Learn how to contribute Anyone who is interested can contribute to the articles. When you contribute, your work goes into the content set after it's been reviewed and merged. If you have more complex edits or edits to multiple files, follow the guidance in the [MSEC Docs Self-Serve Playbook](https://aka.ms/MSecDocsSelfServePlaybook). For simple edits to a single file, follow the steps in this article. ### Quickly update an article using GitHub.com Contributors who make infrequent or small updates can edit the file directly on GitHub.com without installing any software. > [!TIP] > To edit an article, you need to get to it on the GitHub.com backend. > > Your permissions in the repo determine what you see. People with no special privileges see the steps as described. People with permissions to approve their own pull requests see a similar experience with different button and page titles (for example, **Commit changes** instead of **Propose changes**), extra options for creating a new branch, and fewer confirmation pages. The point is: click any green buttons that are presented to you until there are no more. 1. Verify that you're signed in to GitHub.com with your GitHub account. 2. On github.com, find the article that you want to update. 3. Select **Edit** ![Edit icon](media/quick-update-learn-edit-icon.png) at the top right of the screen, then select **In place** in the drop-down. ![Screenshot of editing in place on GitHub.com.](media/quick-update-edit-button-on-learn-page.png) 4. On the next page that opens, select **Fork this repository**. ![Screenshot of the You need to fork this repository to propose changes page.](media/quick-update-fork-this-repository-page.png) 5. The article file opens in a line-numbered editor page where you can make updates. Articles on learn.microsoft.com are formatted using the Markdown language. For help on using Markdown, see [Mastering Markdown.](https://guides.github.com/features/mastering-markdown/). Select **Preview** to view your changes as you go. Select **Edit** to go back to making updates. When you're finished making changes, select the green **Commit changes** button. ![Screenshot of how to select the green Commit changes button on the article editor page.](media/quick-update-editor-page.png) 6. In the **Propose changes** dialog that opens, review and/or enter the following values: - **Commit message**: This value is required. You can accept the default value ("Update \") or you can change it. - **Extended description**: This value is optional. For example: - An explanation of the changes. - @ include the GitHub alias of someone to review and merge your changes. When you're finished on the **Propose changes** dialog, select the green **Propose changes** button. ![Screenshot of how to select the green Propose changes button in the Propose changes dialog.](media/quick-update-propose-changes-dialog.png) 7. On the **Comparing changes** page that opens, select the green **Create pull request** button. ![Screenshot of how to select the green Create pull request button on the Comparing changes page.](media/quick-update-comparing-changes-page.png) 8. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button. ![Screenshot of how to select the green Create pull request button on the Open a pull request page.](media/quick-update-open-a-pull-request-page.png) 9. That's it. There's nothing more for you to do. When you're ready to push your changes, comment #sign-off in the PR. Your changes will be reviewed, possibly edited, and then approved. After your pull request is merged, the article is updated on learn.microsoft.com. ## Microsoft Open Source Code of Conduct This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any questions or comments. ### Contributing This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit . When you submit a pull request, a CLA-bot automatically determines whether you need to provide a CLA and decorate the PR appropriately (for example, label, comment). Follow the instructions provided by the bot. You only need to do this step once across all repos using our CLA. ### Legal Notices Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the [LICENSE-CODE](LICENSE-CODE) file. Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries/regions. The licenses for this project don't grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at . Privacy information can be found at Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.