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

Fixed typos and grammar bogons.

Browse source
This commit is contained in:
Jens Schweikhardt 2001-05-07 15:46:10 +00:00
parent 9ed2262232
commit e987a4430a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9376
2 changed files with 20 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
en_US.ISO8859-1/articles/committers-guide/article.sgml
View file

@ -19,7 +19,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.61 2001/04/27 10:07:52 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.62 2001/04/27 10:08:44 nik Exp $</pubdate>
<copyright>
<year>1999</year>
@ -168,7 +168,7 @@
<screen>&prompt.user; <userinput>cvs checkout shazam</userinput></screen>
<para>This checks out a copy of the <filename>shazam</filename> module. If
there is no <filename>shazam</filename> module in the modules file, looks for a
there is no <filename>shazam</filename> module in the modules file, it looks for a
top-level directory named <filename>shazam</filename> instead.</para>
<table frame="none">
@ -195,7 +195,7 @@
<row>
<entry><option>-D<replaceable>date</replaceable></option></entry>
<entry>Check out the sources as they were on date
<replaceable>data</replaceable></entry>
<replaceable>date</replaceable></entry>
</row>
</tbody>
</tgroup>
@ -516,11 +516,11 @@
</itemizedlist>
<para>You'll almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.62 2001-04-27 10:08:44 nik Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.63 2001-05-07 15:46:10 schweikh Exp $</literal> (or in FreeBSD's case,
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
the file to resolve the conflict (remove the marker lines and
the second <literal>$Id: article.sgml,v 1.62 2001-04-27 10:08:44 nik Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.62 2001-04-27 10:08:44 nik Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.63 2001-05-07 15:46:10 schweikh Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.63 2001-05-07 15:46:10 schweikh Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -732,7 +732,7 @@ checkout -P</programlisting>
<para><ulink url="http://people.FreeBSD.org/~eivind/cdiff">http://people.FreeBSD.org/~eivind/cdiff</ulink></para>
<para>Simply use instead of &man.more.1; or &man.less.1;:</para>
<para>Simply use it instead of &man.more.1; or &man.less.1;:</para>
<screen>&prompt.user; <userinput>cvs diff -Nu shazam | cdiff</userinput></screen>
@ -894,7 +894,7 @@ checkout -P</programlisting>
<command>edit-pr <replaceable>pr-number</replaceable></command>
on <hostid>freefall</hostid> to close it. It is also considered
nice if you take time to close any PRs associated with your
commits, if appropriate. Your can also make use of
commits, if appropriate. You can also make use of
&man.send-pr.1; yourself for proposing any change which you feel
should probably be made, pending a more extensive peer-review
first.</para>
@ -1645,7 +1645,7 @@ docs:Documentation Bug:nik:</programlisting>
<command>make lint</command>.</para>
<para>For all on-line manual pages, run <command>manck</command>
(from ports) over the man page to verify the all of the cross
(from ports) over the man page to verify all of the cross
references and file references are correct and that the man
page has all of the appropriate <makevar>MLINK</makevar>s
installed.</para>
@ -2172,7 +2172,7 @@ Reviewed by: -arch</programlisting>
<para>You want to commit a change to a section of the tree with a
MAINTAINER assigned. You have collaborated with the listed
MAINTAINER, who has told you to go ahead and commit. The </para>
MAINTAINER, who has told you to go ahead and commit.</para>
<programlisting>...

20
en_US.ISO_8859-1/articles/committers-guide/article.sgml
View file

@ -19,7 +19,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.61 2001/04/27 10:07:52 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.62 2001/04/27 10:08:44 nik Exp $</pubdate>
<copyright>
<year>1999</year>
@ -168,7 +168,7 @@
<screen>&prompt.user; <userinput>cvs checkout shazam</userinput></screen>
<para>This checks out a copy of the <filename>shazam</filename> module. If
there is no <filename>shazam</filename> module in the modules file, looks for a
there is no <filename>shazam</filename> module in the modules file, it looks for a
top-level directory named <filename>shazam</filename> instead.</para>
<table frame="none">
@ -195,7 +195,7 @@
<row>
<entry><option>-D<replaceable>date</replaceable></option></entry>
<entry>Check out the sources as they were on date
<replaceable>data</replaceable></entry>
<replaceable>date</replaceable></entry>
</row>
</tbody>
</tgroup>
@ -516,11 +516,11 @@
</itemizedlist>
<para>You'll almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.62 2001-04-27 10:08:44 nik Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.63 2001-05-07 15:46:10 schweikh Exp $</literal> (or in FreeBSD's case,
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
the file to resolve the conflict (remove the marker lines and
the second <literal>$Id: article.sgml,v 1.62 2001-04-27 10:08:44 nik Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.62 2001-04-27 10:08:44 nik Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.63 2001-05-07 15:46:10 schweikh Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.63 2001-05-07 15:46:10 schweikh Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -732,7 +732,7 @@ checkout -P</programlisting>
<para><ulink url="http://people.FreeBSD.org/~eivind/cdiff">http://people.FreeBSD.org/~eivind/cdiff</ulink></para>
<para>Simply use instead of &man.more.1; or &man.less.1;:</para>
<para>Simply use it instead of &man.more.1; or &man.less.1;:</para>
<screen>&prompt.user; <userinput>cvs diff -Nu shazam | cdiff</userinput></screen>
@ -894,7 +894,7 @@ checkout -P</programlisting>
<command>edit-pr <replaceable>pr-number</replaceable></command>
on <hostid>freefall</hostid> to close it. It is also considered
nice if you take time to close any PRs associated with your
commits, if appropriate. Your can also make use of
commits, if appropriate. You can also make use of
&man.send-pr.1; yourself for proposing any change which you feel
should probably be made, pending a more extensive peer-review
first.</para>
@ -1645,7 +1645,7 @@ docs:Documentation Bug:nik:</programlisting>
<command>make lint</command>.</para>
<para>For all on-line manual pages, run <command>manck</command>
(from ports) over the man page to verify the all of the cross
(from ports) over the man page to verify all of the cross
references and file references are correct and that the man
page has all of the appropriate <makevar>MLINK</makevar>s
installed.</para>
@ -2172,7 +2172,7 @@ Reviewed by: -arch</programlisting>
<para>You want to commit a change to a section of the tree with a
MAINTAINER assigned. You have collaborated with the listed
MAINTAINER, who has told you to go ahead and commit. The </para>
MAINTAINER, who has told you to go ahead and commit.</para>
<programlisting>...