Skip to content

Commit 4222cba

Browse files
authored
Spelling, grammar and puctuation changes
Spelling:- line 25 indentifing -> identifying line 27 developement -> development line 36 retargetted -> retargeted Grammar:- line 36 a development branches -> development branches Punctuation:- line 8 new, -> new line 49 Also -> Also,
1 parent 0f14248 commit 4222cba

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ If you have any questions, please reach out on the [HoloLens forums](https://for
55

66
# Process
77

8-
1. [Make a proposal](https://github.com/Microsoft/HoloToolkit-Unity/issues) (either new, or for one of the elements in our backlog)
8+
1. [Make a proposal](https://github.com/Microsoft/HoloToolkit-Unity/issues) (either new or for one of the elements in our backlog)
99
2. Identify the appropriate development branch
1010
3. Implement the proposal and its tests.
1111
4. Ensure that your implementation meets the [coding guidelines](CodingGuidelines.md).
@@ -22,9 +22,9 @@ This will let us have a brief discussion about the problem and, hopefully, ident
2222

2323
Note: If you wish to work on something that already exists on our backlog, you can use that work item as your proposal.
2424

25-
# Identifing the development branch
25+
# Identifying the development branch
2626

27-
The master branch does not accept direct pull requests. Each change must be submitted through an appropriate developement branch. Each upcoming MRTK release has its own development branch (ex: may18_dev).
27+
The master branch does not accept direct pull requests. Each change must be submitted through an appropriate development branch. Each upcoming MRTK release has its own development branch (ex: may18_dev).
2828

2929
To identify the appropriate development branch:
3030

@@ -33,7 +33,7 @@ To identify the appropriate development branch:
3333
3. If the **Status** is not **Accepting changes**, select the next release
3434
4. Note the **Development branch** for Pull Request submission.
3535

36-
Any pull request made directly to master will be retargetted to a development branches by a project maintainer.
36+
Any pull request made directly to master will be retargeted to development branches by a project maintainer.
3737

3838
NOTE: A project maintainer may retarget your PR to a different development branch based on the release priorities.
3939

@@ -46,7 +46,7 @@ NOTE: A project maintainer may retarget your PR to a different development branc
4646
5. Make sure that all the tests continue to pass.
4747
6. Ensure the code is [WACK compliant](https://developer.microsoft.com/en-us/windows/develop/app-certification-kit). To do this, generate a Visual Studio solution, right click on project; Store -> Create App Packages. Follow the prompts and run WACK tests. Make sure they all succeed.
4848
7. Ensure you update the [README](https://github.com/Microsoft/HoloToolkit-Unity/blob/master/README.md) with additional documentation as needed.
49-
8. Also update the [HoloToolkit-Unity wiki](https://github.com/Microsoft/HoloToolkit-Unity/wiki) if you think it will be useful for other developers.
49+
8. Also, update the [HoloToolkit-Unity wiki](https://github.com/Microsoft/HoloToolkit-Unity/wiki) if you think it will be useful for other developers.
5050

5151
# Pull request
5252

0 commit comments

Comments
 (0)