summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Jonathan Reed <jdreed@mit.edu>2014-02-14 12:29:39 -0500
committerGravatar Jonathan Reed <jdreed@mit.edu>2014-02-14 12:29:39 -0500
commitfc004553b0245d850fbe4d77162086dd025e65a2 (patch)
treee272d2b541262fa2e2c827edfb9bc81acd8dbb2d
parent6cd2e8286f7c9a27ce174d52c9867b3d26821cba (diff)
Wordsmith apology paragraph
Add suggestion from dwilson to change wording to "...qualify your apology" to clarify that it's not the literal phrasing that's important, but rather avoiding "#sorry #notsorry"
-rw-r--r--code-of-conduct.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/code-of-conduct.txt b/code-of-conduct.txt
index 60621be..2c915a8 100644
--- a/code-of-conduct.txt
+++ b/code-of-conduct.txt
@@ -104,13 +104,13 @@ member of the EC to discuss the incident further.
The most sincere apologies consist of "I'm sorry"
-An apology should be a sincere expression of sadness for the sadness
-of others. If you violate one of the principles in this document, but
-follow your apology with "...that", "...if", "..but", you're implying
-that the other person shares some of the blame for the incident.
-Since they're the one who's upset, that's not true. You may not have
-intended to make them feel bad, but you did, and saying "I'm sorry"
-shows that you regret that they feel bad (which, hopefully, you do.)
+An apology should be a sincere expression of sadness for the sadness of
+others. If you violate one of the principles in this document, but then
+qualify your apology with "...that", "...if", "..but", you're implying
+that the other person shares some of the blame for the incident. Since
+they're the one who's upset, that's not true. You may not have intended
+to make them feel bad, but you did, and saying "I'm sorry" shows that
+you regret that they feel bad (which, hopefully, you do.)
Sometimes, people are tempted to say "I'm sorry, but" (etc.) because
they don't want to concede their point in a discussion. But this sort