summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/writing-code
diff options
context:
space:
mode:
authorPeter Inglesby <peter.inglesby@gmail.com>2015-02-07 16:57:37 +0000
committerMarkus Holtermann <info@markusholtermann.eu>2015-02-07 18:46:04 +0100
commita8f1c70dce792831688588f271efb3a825dffef8 (patch)
treeb0895a6ba0a2797db302405ee2aeaafb36badb0a /docs/internals/contributing/writing-code
parent58afd30b593fbd1e3d17c1bba83597da07bdb5f5 (diff)
Fixed docs typo
Diffstat (limited to 'docs/internals/contributing/writing-code')
-rw-r--r--docs/internals/contributing/writing-code/submitting-patches.txt2
1 files changed, 1 insertions, 1 deletions
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.