diff options
| author | Tim Graham <timograham@gmail.com> | 2013-01-29 08:45:40 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-01-29 10:58:24 -0700 |
| commit | 5da6ce11edb60319c014c07c40b03674ea89de4c (patch) | |
| tree | c59913f7b566f07a9e0ce26e3f2d5ed677507a3a /docs/internals | |
| parent | f6075b0596e20951bd8232f09d97fb7fac08308c (diff) | |
[1.5.x] Fixed typos in docs and comments
Backport of ee26797cff from master
Diffstat (limited to 'docs/internals')
| -rw-r--r-- | docs/internals/contributing/committing-code.txt | 2 | ||||
| -rw-r--r-- | docs/internals/contributing/writing-code/working-with-git.txt | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt index 67dda02f8b..bc2f97a485 100644 --- a/docs/internals/contributing/committing-code.txt +++ b/docs/internals/contributing/committing-code.txt @@ -116,7 +116,7 @@ Practicality beats purity, so it is up to each committer to decide how much history mangling to do for a pull request. The main points are engaging the community, getting work done, and having a usable commit history. -.. _committing-guidlines: +.. _committing-guidelines: Committing guidelines --------------------- diff --git a/docs/internals/contributing/writing-code/working-with-git.txt b/docs/internals/contributing/writing-code/working-with-git.txt index d4a95ae45a..dcfdd9e85b 100644 --- a/docs/internals/contributing/writing-code/working-with-git.txt +++ b/docs/internals/contributing/writing-code/working-with-git.txt @@ -81,7 +81,7 @@ commit them:: git commit When writing the commit message, follow the :ref:`commit message -guidelines <committing-guidlines>` to ease the work of the committer. If +guidelines <committing-guidelines>` to ease the work of the committer. If you're uncomfortable with English, try at least to describe precisely what the commit does. @@ -121,7 +121,7 @@ a pull request at GitHub. A good pull request means: * well-formed messages for each commit: a summary line and then paragraphs wrapped at 72 characters thereafter -- see the :ref:`committing guidelines - <committing-guidlines>` for more details, + <committing-guidelines>` for more details, * documentation and tests, if needed -- actually tests are always needed, except for documentation changes. |