PFA the proposed fixes.
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reportbug depends on:
ii apt 184.108.40.206.1
ii python 2.7.9-1
ii python-reportbug 6.6.3
pn python:any <none>
reportbug recommends no packages.
Versions of packages reportbug suggests:
ii claws-mail 3.11.1-3
pn debconf-utils <none>
pn debsums <none>
pn dlocate <none>
pn emacs23-bin-common | emacs24-bin-common <none>
ii exim4 4.84-8
ii exim4-daemon-light [mail-transport-agent] 4.84-8
ii file 1:5.22+15-2
ii gnupg 1.4.18-7
ii python-gtk2 2.24.0-4
pn python-gtkspell <none>
pn python-urwid <none>
pn python-vte <none>
ii xdg-utils 1.1.0~rc1+git20111210-7.4
Versions of packages python-reportbug depends on:
ii apt 220.127.116.11.1
ii python-debian 0.1.27
ii python-debianbts 1.12
pn python:any <none>
python-reportbug suggests no packages.
-- no debconf information
diff --git a/doc/README.Users b/doc/README.Users
index 6e79aa3..1d342c3 100644
@@ -13,10 +13,10 @@ smtptls
Thanks to: Raphael Geissert <atom...@gmail.com>
-How to Usertags a Bug at Report Time
+How to add Usertags to a Bug at Report Time
-If you're filing a bug and you what to usertag it, you can add these
+If you're filing a bug and you want to usertag it, you can add these
lines (in the pseudo-header)
User: <user email address>
@@ -30,9 +30,9 @@ Severity: <severity>
lines in the bug body.
-Please note that if you specify more than 2 tag, then they will be
+Please note that if you specify more than 2 tags, then they will be
ordered alphabetically (so if you use usercategories, it will only
-appears in the first one).
+appear in the first one).
Thanks to: Sandro Tosi <mo...@debian.org>
@@ -73,7 +73,7 @@ Then a change to ~/.emacs file is needed, in order to add:
or else Emacs won't listen for connections from emacsclient (and a new
`emacs` instance is executed).
-With this changes, using the `gnus` MUA, the mail is opened in the
+With these changes, using the `gnus` MUA, the mail is opened in the
running `emacs`, or if there's none, a new instance is executed.
Thanks to: Håkon Stordahl <ha...@stordahl.org>
@@ -103,11 +103,11 @@ reportbug move it (or leave it) to the correct location (for example,
'X-Debbugs-Cc' if added to the pseudo-header is then moved to mail headers
section to be processed by debbugs engine).
-That said, please note that this two ways have now a different semantics: any
+That said, please note that these two ways have different semantics: any
pseudo-header passed on the command-line is preserved as a pseudo-header, and
not moved to the mail headers part of the email, while adding a header into the
-mail body still trigger the reportbug recognition code that will move the header
-to mail headers part if not a "common" pseudo-header (like 'Usertags',
+mail body still triggers the reportbug recognition code that will move the header
+to mail headers part if it is not a "common" pseudo-header (like 'Usertags',
'Severity', or 'Package' and so on).
Network Errors and Timeout
@@ -141,7 +141,7 @@ This host is useful in situations like:
Please keep in mind that this service has some limitations:
- only 5 reports per hour are allowed (technically, 5 connections to
- the server, even if they don't result in bugs submission);
+ the server, even if they don't result in bug submission);
- relay is not allowed.
The last rule, in particular, doesn't allow to send a carbon-copy of
@@ -150,5 +150,5 @@ the bug), and X-Debbugs-CC has to be used instead (that will send an
email after BTS processing).
Let us also clarify that this service is in no way controlled by
-reportbug maintainers, so in case any questions/complains/information
+reportbug maintainers, so in case any questions/complaints/information
requests you have to contact ow...@bugs.debian.org .
\ No newline at end of file
Reportbug-maint mailing list