diff options
| author | Ramax Lo <ramaxlo@gmail.com> | 2019-09-30 15:10:56 +0800 |
|---|---|---|
| committer | Ramax Lo <ramaxlo@gmail.com> | 2019-09-30 16:15:34 +0800 |
| commit | cfcd0f040b3dfd2457fbe7f88c4df3f3c5683249 (patch) | |
| tree | 2ceaa6a906d997a59d6b34609e94771db1d4c8e6 /docs/contributing/development.rst | |
| parent | 076f0f139d6b1b63def3c3234a839eb82ca7306d (diff) | |
| download | vyos-documentation-cfcd0f040b3dfd2457fbe7f88c4df3f3c5683249.tar.gz vyos-documentation-cfcd0f040b3dfd2457fbe7f88c4df3f3c5683249.zip | |
Fix typos in pages
Diffstat (limited to 'docs/contributing/development.rst')
| -rw-r--r-- | docs/contributing/development.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/contributing/development.rst b/docs/contributing/development.rst index 4b762051..9e99ece8 100644 --- a/docs/contributing/development.rst +++ b/docs/contributing/development.rst @@ -31,7 +31,7 @@ This information is used in two ways: * Keep track of the progress (what we've already done in this branch and what we still need to do). * Prepare release notes. -To make this approach work, every change must be associated with a bug number and componant. +To make this approach work, every change must be associated with a bug number and component. If there is no bug/enhancement request for the changes you are going to make, you must create a `bugtracker`_ entry first. Once there is a `bugtracker`_ entry about it, you should reference in your commit message, as in: |