mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00
Code Issues 32 Releases Wiki Activity

[1.5.x] Fixed typos in docs and comments

Browse Source 
Backport of ee26797cff from master
This commit is contained in:
Tim Graham
2013-01-29 08:45:40 -07:00
parent f6075b0596
commit 5da6ce11ed
15 changed files with 20 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/contributing/committing-code.txt
View File

@@ -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
---------------------

4
docs/internals/contributing/writing-code/working-with-git.txt
View File

@@ -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.