summaryrefslogtreecommitdiff
path: root/admin/notes/bug-triage
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2016-01-30 20:17:56 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2016-01-30 20:18:21 -0800
commit802e6df70b588ae37ebebfffbdbd9d80ec3a9e60 (patch)
tree0660c148aa8eb067e948937b79028c6aa6504837 /admin/notes/bug-triage
parent113c9a95aef00f514749b1453ff6117103cc59d8 (diff)
downloademacs-802e6df70b588ae37ebebfffbdbd9d80ec3a9e60.tar.gz
emacs-802e6df70b588ae37ebebfffbdbd9d80ec3a9e60.tar.bz2
emacs-802e6df70b588ae37ebebfffbdbd9d80ec3a9e60.zip
Spelling fixes
Diffstat (limited to 'admin/notes/bug-triage')
-rw-r--r--admin/notes/bug-triage2
1 files changed, 1 insertions, 1 deletions
diff --git a/admin/notes/bug-triage b/admin/notes/bug-triage
index 7392fb96985..648ada4acbf 100644
--- a/admin/notes/bug-triage
+++ b/admin/notes/bug-triage
@@ -20,7 +20,7 @@ the ones that are not reproducible on the current release.
reproducible. A bug can and should stay open as long as it is
still a bug and no one has fixed it. The following is a
suggested checklist to follow for handling these bugs, along with
- example replies. The various closings, taggings, etc, are done
+ example replies. Closing, tagging, etc., are done
with debbugs control messages, which in debbugs-gnu is initiated
with a "C".
[ ] Read the mail thread for the bug. Find out if anyone has