From a8f1c70dce792831688588f271efb3a825dffef8 Mon Sep 17 00:00:00 2001
From: Peter Inglesby <peter.inglesby@gmail.com>
Date: Sat, 7 Feb 2015 16:57:37 +0000
Subject: [PATCH] Fixed docs typo

---
 docs/internals/contributing/writing-code/submitting-patches.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt
index 965ce45eaa..e5c01faca2 100644
--- a/docs/internals/contributing/writing-code/submitting-patches.txt
+++ b/docs/internals/contributing/writing-code/submitting-patches.txt
@@ -119,7 +119,7 @@ to publish your work. If you use the Git workflow, then you should
 announce your branch in the ticket by including a link to your branch.
 When you think your work is ready to be merged in create a pull request.
 
-See the :doc:`working-with-git` documentation for mode details.
+See the :doc:`working-with-git` documentation for more details.
 
 You can also use patches in Trac. When using this style, follow these
 guidelines.