Expand contractions.
This commit is contained in:
parent
687c734ca1
commit
52ce212a52
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=14138
1 changed files with 5 additions and 5 deletions
|
@ -105,13 +105,13 @@
|
|||
upgrading and trying to reproduce the problem on an up-to-date
|
||||
system before submitting a problem report. There are few things
|
||||
that will annoy a developer more than receiving a problem report
|
||||
about a bug she's already fixed.</para>
|
||||
about a bug she has already fixed.</para>
|
||||
|
||||
<para>Finally, a bug that can not be reproduced can rarely be
|
||||
fixed. If the bug only occurred once and you can not reproduce
|
||||
it, and it does not seem to happen to anybody else, chances are
|
||||
none of the developers will be able to reproduce it or figure
|
||||
out what's wrong. That does not mean it did not happen, but it
|
||||
out what is wrong. That does not mean it did not happen, but it
|
||||
does mean that the chances of your problem report ever leading
|
||||
to a bug fix are very slim, and you should consider letting the
|
||||
matter drop.</para>
|
||||
|
@ -137,7 +137,7 @@
|
|||
<para>The
|
||||
<ulink
|
||||
URL="../../books/handbook/eresources.html#ERESOURCES-MAIL">mailing
|
||||
lists</ulink>—if you're not subscribed, use
|
||||
lists</ulink>—if you are not subscribed, use
|
||||
<ulink
|
||||
URL="http://www.FreeBSD.org/search/search.html#mailinglists">the
|
||||
searchable archives</ulink> on the FreeBSD web site. If your
|
||||
|
@ -204,7 +204,7 @@
|
|||
|
||||
<screen>&prompt.user; <userinput>send-pr -a /var/run/dmesg -a /tmp/errors</userinput></screen>
|
||||
|
||||
<para>Don't worry about binary files, they will be automatically
|
||||
<para>Do not worry about binary files, they will be automatically
|
||||
encoded so as not to upset your mail agent.</para>
|
||||
|
||||
<para>If you attach a patch, make sure you use the
|
||||
|
@ -462,7 +462,7 @@
|
|||
least a workaround (which not only helps other people with
|
||||
the same problem work around it, but may also help a
|
||||
developer understand the cause for the problem), but if
|
||||
you do not have any firm ideas for either, it's better to
|
||||
you do not have any firm ideas for either, it is better to
|
||||
leave this field blank than to speculate.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
Loading…
Reference in a new issue