From 5da6ce11edb60319c014c07c40b03674ea89de4c Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 29 Jan 2013 08:45:40 -0700 Subject: [1.5.x] Fixed typos in docs and comments Backport of ee26797cff from master --- docs/internals/contributing/writing-code/working-with-git.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/internals/contributing/writing-code') 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 ` to ease the work of the committer. If +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 - ` for more details, + ` for more details, * documentation and tests, if needed -- actually tests are always needed, except for documentation changes. -- cgit v1.3