Skip to content

Commit e5f6047

Browse files
authored
docs(contributing): fix spelling in contribution guide (#4192)
docs(contributing): fix spelling mistakes
1 parent 6752d38 commit e5f6047

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎CONTRIBUTING.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22

33
Thank you for your interest in contributing to Unity Multiplayer Networking!
44

5-
Here are our guidlines for contributing:
5+
Here are our guidelines for contributing:
66

77
* [Code of Conduct](#coc)
88
* [Ways to Contribute](#ways)
99
* [Issues and Bugs](#issue)
1010
* [Feature Requests](#feature)
1111
* [Improving Documentation](#docs)
1212
* [Unity Contribution Agreement](#cla)
13-
* [Pull Request Submission Guidlines](#submit-pr)
13+
* [Pull Request Submission Guidelines](#submit-pr)
1414

1515
## <a name="coc"></a> Code of Conduct
1616

@@ -46,7 +46,7 @@ When you open a pull request, you will be asked to enter into Unity's License Ag
4646

4747
## <a name="submit-pr"></a> Pull Request Submission Guidelines
4848

49-
We use the [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) for the development of the Netcode for GameObjects. This means development happens on the **develop-3.x.x branch** and Pull Requests should be submited to it.
49+
We use the [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) for the development of the Netcode for GameObjects. This means development happens on the **develop-3.x.x branch** and Pull Requests should be submitted to it.
5050

5151
### Commit Message Guidelines
5252
We have very precise rules over how our git commit messages can be formatted. This leads to **more

0 commit comments

Comments
 (0)