os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix up whitespace and remove contractions.

Browse source
This commit is contained in:
Mark Linimon 2004-11-30 08:54:29 +00:00
parent 03af8e30f5
commit 428859b8c8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=23078
1 changed files with 7 additions and 7 deletions

14
en_US.ISO8859-1/articles/pr-guidelines/article.sgml
View file

@ -560,7 +560,7 @@
of the following reasons:</para>
<itemizedlist>
<listitem>
<listitem>
<para>A followup to an existing PR, sent through email, has
the wrong format on its <literal>Subject:</literal>
header.</para>
@ -653,7 +653,7 @@ from the body of this PR to kern/12345</programlisting>
change. Typically something like the following is ok:</para>
<programlisting>Followup to ports/45364 misfiled as a new PR.
This was misfiled because the subject didn't have the format:
This was misfiled because the subject did not have the format:
Re: ports/45364: ...</programlisting>
@ -678,7 +678,7 @@ This was misfiled because the subject didn't have the format:
issues is quoting, changes or removal of the
<command>send-pr</command> template, either by the user who
edits the template or by mailers which do strange things to
plain text messages. This doesn't happen a lot of the time,
plain text messages. This does not happen a lot of the time,
but it can be fixed with <command>edit-pr</command> too; it
does require a bit of work from the developer who refiles the
PR, but it is relatively easy to do most of the time.</para>
@ -761,10 +761,10 @@ This was misfiled because the subject didn't have the format:
<itemizedlist>
<listitem>
<para><ulink
url="&url.articles.problem-reports;/article.html">How to
Write FreeBSD Problem Reports</ulink>&mdash;guidelines
for PR originators.</para>
<para><ulink
url="&url.articles.problem-reports;/article.html">How to
Write FreeBSD Problem Reports</ulink>&mdash;guidelines
for PR originators.</para>
</listitem>
</itemizedlist>
</section>