summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/writing-code
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-01-29 08:45:40 -0700
committerTim Graham <timograham@gmail.com>2013-01-29 10:55:55 -0700
commitee26797cff6ef17817c58e6a2f86db81c21f9800 (patch)
tree1dc53e0553f1a5f99a4da950fddc4168960720a4 /docs/internals/contributing/writing-code
parentb99a4e1073e5504ec8f40447a8e9fd1066c76b7f (diff)
Fixed typos in docs and comments
Diffstat (limited to 'docs/internals/contributing/writing-code')
-rw-r--r--docs/internals/contributing/writing-code/working-with-git.txt4
1 files changed, 2 insertions, 2 deletions
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.