Spelling fixes, courtesy of ispell.
This commit is contained in:
parent
52bc052be8
commit
6888441d55
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=15360
4 changed files with 12 additions and 12 deletions
|
@ -592,11 +592,11 @@
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>You will almost certainly get a conflict because
|
<para>You will almost certainly get a conflict because
|
||||||
of the <literal>$Id: article.sgml,v 1.142 2002-11-02 16:48:43 rwatson Exp $</literal> (or in FreeBSD's case,
|
of the <literal>$Id: article.sgml,v 1.143 2002-12-15 22:19:01 ceri Exp $</literal> (or in FreeBSD's case,
|
||||||
<literal>$<!-- stop expansion -->FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
|
<literal>$<!-- stop expansion -->FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
|
||||||
the file to resolve the conflict (remove the marker lines and
|
the file to resolve the conflict (remove the marker lines and
|
||||||
the second <literal>$Id: article.sgml,v 1.142 2002-11-02 16:48:43 rwatson Exp $</literal> line, leaving the original
|
the second <literal>$Id: article.sgml,v 1.143 2002-12-15 22:19:01 ceri Exp $</literal> line, leaving the original
|
||||||
<literal>$Id: article.sgml,v 1.142 2002-11-02 16:48:43 rwatson Exp $</literal> line intact).</para>
|
<literal>$Id: article.sgml,v 1.143 2002-12-15 22:19:01 ceri Exp $</literal> line intact).</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
@ -1360,7 +1360,7 @@ docs:Documentation Bug:nik:</programlisting>
|
||||||
the &a.developers; and CC:/BCC: another FreeBSD list</emphasis>.
|
the &a.developers; and CC:/BCC: another FreeBSD list</emphasis>.
|
||||||
Never, ever email another FreeBSD email list and CC:/BCC:
|
Never, ever email another FreeBSD email list and CC:/BCC:
|
||||||
the &a.developers;. Doing so can greatly diminish the benefits
|
the &a.developers;. Doing so can greatly diminish the benefits
|
||||||
of this list. Also, never publically post or forward emails sent
|
of this list. Also, never publicly post or forward emails sent
|
||||||
to the &a.developers;. The act of sending to
|
to the &a.developers;. The act of sending to
|
||||||
the &a.developers; vs. a public list means the information in
|
the &a.developers; vs. a public list means the information in
|
||||||
the email is not for public consumption.
|
the email is not for public consumption.
|
||||||
|
@ -1883,7 +1883,7 @@ docs:Documentation Bug:nik:</programlisting>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
|
|
||||||
<para>The i386 and sparc64 platforms were chosen due to being more
|
<para>The i386 and sparc64 platforms were chosen due to being more
|
||||||
readily availabile to developers and as representatives of more
|
readily available to developers and as representatives of more
|
||||||
diverse processor and system designs - big vs little endian,
|
diverse processor and system designs - big vs little endian,
|
||||||
register file vs register stack, different DMA and cache
|
register file vs register stack, different DMA and cache
|
||||||
implementations, hardware page tables vs software TLB management
|
implementations, hardware page tables vs software TLB management
|
||||||
|
@ -2049,7 +2049,7 @@ docs:Documentation Bug:nik:</programlisting>
|
||||||
under development by hardware vendors, but not yet available to
|
under development by hardware vendors, but not yet available to
|
||||||
the project.</para>
|
the project.</para>
|
||||||
|
|
||||||
<para>Tier 2 architectures are usually systems targetted at Tier 1
|
<para>Tier 2 architectures are usually systems targeted at Tier 1
|
||||||
support, but that are still under development. Architectures
|
support, but that are still under development. Architectures
|
||||||
reaching end of life may also be moved from Tier 1 status to Tier
|
reaching end of life may also be moved from Tier 1 status to Tier
|
||||||
2 status as the availability of resources to continue to maintain
|
2 status as the availability of resources to continue to maintain
|
||||||
|
@ -2094,7 +2094,7 @@ docs:Documentation Bug:nik:</programlisting>
|
||||||
<para>Systems may only be moved from one tier to another tier by
|
<para>Systems may only be moved from one tier to another tier by
|
||||||
approval of the FreeBSD Core Team, which shall make that
|
approval of the FreeBSD Core Team, which shall make that
|
||||||
decision in collaboration with the Security Officer, Release
|
decision in collaboration with the Security Officer, Release
|
||||||
Enginering, and toolchain maintenance teams.</para>
|
Engineering, and toolchain maintenance teams.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
|
|
@ -525,7 +525,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||||
<para>The FreeBSD Project happily accepts donations of
|
<para>The FreeBSD Project happily accepts donations of
|
||||||
hardware that it can find good use for. If you are
|
hardware that it can find good use for. If you are
|
||||||
interested in donating hardware, please contact the <ulink
|
interested in donating hardware, please contact the <ulink
|
||||||
url="http://www.FreeBSD.org/donations/">Donations Liason
|
url="http://www.FreeBSD.org/donations/">Donations Liaison
|
||||||
Office</ulink>.</para>
|
Office</ulink>.</para>
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
|
|
|
@ -30,7 +30,7 @@
|
||||||
level (Ethernet addresses) of the devices connected to each of its
|
level (Ethernet addresses) of the devices connected to each of its
|
||||||
network interfaces and then forwarding the traffic between the two
|
network interfaces and then forwarding the traffic between the two
|
||||||
networks only if the source and the destination are on different
|
networks only if the source and the destination are on different
|
||||||
segments. Under many points of view a brigde is similar to an Ethernet
|
segments. Under many points of view a bridge is similar to an Ethernet
|
||||||
switch with only two ports.</para>
|
switch with only two ports.</para>
|
||||||
</abstract>
|
</abstract>
|
||||||
</articleinfo>
|
</articleinfo>
|
||||||
|
@ -106,7 +106,7 @@ options IPFIREWALL_VERBOSE</programlisting>
|
||||||
<sect2 id="filtering-bridges-modules">
|
<sect2 id="filtering-bridges-modules">
|
||||||
<title>Modules Loading</title>
|
<title>Modules Loading</title>
|
||||||
|
|
||||||
<para>If you have choosen to use the new and simpler installation
|
<para>If you have chosen to use the new and simpler installation
|
||||||
method, the only thing to do now is add the following row to
|
method, the only thing to do now is add the following row to
|
||||||
<filename>/boot/loader.conf</filename>:</para>
|
<filename>/boot/loader.conf</filename>:</para>
|
||||||
|
|
||||||
|
@ -125,7 +125,7 @@ options IPFIREWALL_VERBOSE</programlisting>
|
||||||
<title>Final Preparation</title>
|
<title>Final Preparation</title>
|
||||||
|
|
||||||
<para>Before rebooting in order to load the new kernel or the required
|
<para>Before rebooting in order to load the new kernel or the required
|
||||||
modules (according to the previously choosen installation method), you
|
modules (according to the previously chosen installation method), you
|
||||||
have to make some changes to the <filename>/etc/rc.conf</filename>
|
have to make some changes to the <filename>/etc/rc.conf</filename>
|
||||||
configuration file. The default rule of the firewall is to reject all IP
|
configuration file. The default rule of the firewall is to reject all IP
|
||||||
packets. Initially we will set up an <option>open</option> firewall, in order to verify
|
packets. Initially we will set up an <option>open</option> firewall, in order to verify
|
||||||
|
|
Loading…
Reference in a new issue