diff options
| author | Karthikeyan Singaravelan <tir.karthi@gmail.com> | 2020-01-06 20:41:32 +0530 |
|---|---|---|
| committer | Marcel Hellkamp <marc@gsites.de> | 2020-12-31 19:28:56 +0100 |
| commit | f48c9eb0dcb9ea7a2c230928ff0556e9e6586336 (patch) | |
| tree | e18da5a0f0cb7427f0ce67e18858eaa03cf8c657 /docs/development.rst | |
| parent | 57402ad01233b70370153d2360b7ef50d2a3fd2c (diff) | |
| download | bottle-f48c9eb0dcb9ea7a2c230928ff0556e9e6586336.tar.gz | |
Fix typos in documentation.
Diffstat (limited to 'docs/development.rst')
| -rw-r--r-- | docs/development.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/development.rst b/docs/development.rst index 1ea504c..54b681b 100644 --- a/docs/development.rst +++ b/docs/development.rst @@ -80,7 +80,7 @@ The best way to get your changes integrated into the main development branch is * **Documentation:** Tell us what your patch does. Comment your code. If you introduced a new feature, add to the documentation so others can learn about it. * **Test:** Write tests to prove that your code works as expected and does not break anything. If you fixed a bug, write at least one test-case that triggers the bug. Make sure that all tests pass before you submit a patch. -* **One patch at a time:** Only fix one bug or add one feature at a time. Design your patches so that they can be applyed as a whole. Keep your patches clean, small and focused. +* **One patch at a time:** Only fix one bug or add one feature at a time. Design your patches so that they can be applied as a whole. Keep your patches clean, small and focused. * **Sync with upstream:** If the ``upstream/master`` branch changed while you were working on your patch, rebase or pull to make sure that your patch still applies without conflicts. |