Browse Source

github: cleanup typos in CONTRIBUTING.md

Nick Andrew 2 years ago
parent
commit
8dfdf48e6d
1 changed files with 4 additions and 4 deletions
  1. 4
    4
      .github/CONTRIBUTING.md

+ 4
- 4
.github/CONTRIBUTING.md View File

@@ -12,7 +12,7 @@ This means you care about the quality of your contributions.
12 12
   * Know how to create a commit (for details see below).
13 13
   * Know how to work with git history (rebasing your commits).
14 14
   * Know how to create Pull Requests.
15
-2. Have access to an Alpine Linux [development envirorment](https://wiki.alpinelinux.org/wiki/Developer_Documentation#Development).
15
+2. Have access to an Alpine Linux [development environment](https://wiki.alpinelinux.org/wiki/Developer_Documentation#Development).
16 16
 3. Please __do not__ submit PR's via Github's web interface. You should have a working [development envirorment](https://wiki.alpinelinux.org/wiki/Developer_Documentation#Development) available and submit your commits from your git client.
17 17
 
18 18
 ### Before you start making changes
@@ -36,10 +36,10 @@ This means you care about the quality of your contributions.
36 36
   * Begin the commit message with a single short line summarizing the changes, followed by a blank line and then a more thorough description. Examples of correctly formated summary lines are:
37 37
     * When adding a new aport: testing/apkname: new aport
38 38
     * When modifying an aport: testing/apkname: short description about changes
39
-  * If needed provide a proper formatted (line wrapped) description of what your patch will do. You can provide a description in the PR, but you must include a message for this specific commit in the commit description. If in the future we would like to distance ourselfs from Github the PR information could be lost.
39
+  * If needed provide a proper formatted (line wrapped) description of what your patch will do. You can provide a description in the PR, but you must include a message for this specific commit in the commit description. If in the future we would like to distance ourselves from Github the PR information could be lost.
40 40
 5. Open your copy of the aports repository at github.com and switch to your feature branch. You should now see an option to create your PR. [More info](https://help.github.com/articles/creating-a-pull-request/)
41 41
 6. Wait for an Alpine Linux developer to review your changes.
42
-7. If all is ok your PR will be merged but if a developer asks for changes please do as followed.
42
+7. If all is ok your PR will be merged but if a developer asks for changes please do as follows:
43 43
   * Make the requested changes.
44 44
   * Add your file(s) to git and commit (we will squash your commits if needed).
45 45
   * Push your changes `git push origin my_new_feature`.
@@ -53,5 +53,5 @@ Failing to include __new__ dependencies will fail the CI tests.
53 53
 
54 54
 ### Clean-up a Pull Request (PR)
55 55
 
56
-If by some mistake you end up with multiple commits in your PR and one of our developers asks you to squash you commits please do __NOT__ create a new pull request.
56
+If by some mistake you end up with multiple commits in your PR and one of our developers asks you to squash your commits please do __NOT__ create a new pull request.
57 57
 Instead please follow [this rebase tutorial](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages).