diff options
| author | Peter Inglesby <peter.inglesby@gmail.com> | 2015-02-07 16:57:37 +0000 |
|---|---|---|
| committer | Markus Holtermann <info@markusholtermann.eu> | 2015-02-07 18:47:17 +0100 |
| commit | b6323302e03a4bb3cd87ca6a14a951c74ab82046 (patch) | |
| tree | 27f3906e61fd162c67d6575f15ae70719eec8360 | |
| parent | fc8e1e0c107fe5fc8c82f01dfabfa9b7a196a67c (diff) | |
[1.8.x] Fixed docs typo
Backport of a8f1c70dce792831688588f271efb3a825dffef8 from master
| -rw-r--r-- | docs/internals/contributing/writing-code/submitting-patches.txt | 2 |
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. |