aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormoneromooo-monero <moneromooo-monero@users.noreply.github.com>2018-12-03 19:07:59 +0000
committermoneromooo-monero <moneromooo-monero@users.noreply.github.com>2018-12-03 20:07:47 +0000
commitea85de4f020e34264e8e5f7bb625126be87677d5 (patch)
tree3207451d68e87ff6496e48c961e105482ffe398d
parentMerge pull request #4821 (diff)
downloadmonero-ea85de4f020e34264e8e5f7bb625126be87677d5.tar.xz
CONTRIBUTING: mention not changing spelling/typoes in code
-rw-r--r--CONTRIBUTING.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3de9cd5ce..883d366aa 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -19,7 +19,8 @@ posted to #monero-dev on irc.freenode.net).
Patches should be self contained. A good rule of thumb is to have
one patch per separate issue, feature, or logical change. Also, no
-other changes, such as random whitespace changes or reindentation.
+other changes, such as random whitespace changes, reindentation,
+or fixing typoes, spelling, or wording, unless user visible.
Following the code style of the particular chunk of code you're
modifying is encouraged. Proper squashing should be done (eg, if
you're making a buggy patch, then a later patch to fix the bug,