Apply suggestions from code review

Co-authored-by: Rosario Pulella <Rosariopulella@gmail.com>
This commit is contained in:
Michael Hawker MSFT (XAML Llama) 2021-05-19 13:49:22 -07:00 коммит произвёл GitHub
Родитель 7ab5877e46
Коммит f6ab90ffb3
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -6,11 +6,11 @@ Currently, all the Windows Community Toolkit Docs are being hosted on [WindowsCo
When opening a Pull Request, start by forking [Windows Community Toolkit Docs](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs) repository. Then, based on the type of change you're making you'll need to create a new branch from either the `master` or `dev` branches:
If you have a typo or existing document improvement to an already shipped feature, please base your change off of the [Master branch](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/tree/master). This will allow us to get the change to the published documentation between releases.
If you have a typo or existing document improvement to an already shipped feature, please base your branch off of the [Master branch](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/tree/master). This will allow us to get the change to the published documentation between releases.
For documentation regarding any new features, please base your fork off the last updated dev branch. For example: 'dev/7.1.0'
We will merge updates from the current dev branch to 'master' to keep master in-sync with the live branch. When we make a new release, we will push the live branch in order to publish documentation for new features.
We will merge updates from the current main branch to the latest dev branch to keep it in-sync with any updated changes. We will periodically sync the main branch automatically with the live branch to pick up any changes made over time. When we make a new release, we will integrate the dev branch into the main branch in order to publish documentation for new features.
After following the process above, submit the PR, and depending on the improvement you are proposing the changes will eventually appear in these links.