Expand contractions.

This commit is contained in:
Joel Dahl 2006-02-07 21:32:42 +00:00
parent 8b6b3736bb
commit f361f5a935
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=27058
5 changed files with 9 additions and 9 deletions

View file

@ -145,7 +145,7 @@ ppp_profile="<replaceable>your_profile</replaceable>"</programlisting>
<title>The rule set for the firewall</title>
<para>This is the point where we define the firewall rules for your
system. The ruleset that we're about to describe is a generic
system. The ruleset that we are about to describe is a generic
template for most dialup users. While it will not suit the exact
needs of every user, it provides you with a basic idea of how IPFW
works and should be fairly easy to customize.</para>
@ -159,7 +159,7 @@ ppp_profile="<replaceable>your_profile</replaceable>"</programlisting>
and then everything else is automatically denied.</para>
<para>Following that, let's create the directory where we will store our
firewall rules. In this example, we'll use <filename
firewall rules. In this example, we will use <filename
class="directory">/etc/firewall</filename>. Change into the
directory and edit the file <filename>fwrules</filename> as we
specified in <filename>rc.conf</filename>. Please note that you

View file

@ -949,7 +949,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
So far to distinguish official mirrors.
Official mirrors are not necessarily <emphasis>Tier-1</emphasis>-mirrors.
However you probably won't find a <emphasis>Tier-1</emphasis>-mirror,
However you probably will not find a <emphasis>Tier-1</emphasis>-mirror,
that is not also official.
</para>
<sect2 id="mirror-official-requirements">

View file

@ -544,7 +544,7 @@ sshd password required pam_permit.so</programlisting>
modules.</para>
<para>Although &solaris; PAM modules commonly have a version
number, they're not truly versioned, because the number is a
number, they are not truly versioned, because the number is a
part of the module name and must be included in the
configuration.</para>
</section>
@ -1261,7 +1261,7 @@ sshd password required pam_permit.so</programlisting>
simplified version of OpenPAM's &man.openpam.ttyconv.3;. It is
fully functional, and should give the reader a good idea of how
a conversation function should behave, but it is far too simple
for real-world use. Even if you're not using OpenPAM, feel free
for real-world use. Even if you are not using OpenPAM, feel free
to download the source code and adapt &man.openpam.ttyconv.3; to
your uses; we believe it to be as robust as a tty-oriented
conversation function can reasonably get.</para>

View file

@ -503,7 +503,7 @@
<para>You should also make sure that mail delivery works fine.
&man.send-pr.1; uses mail messages for the submission and
tracking of problem reports. If you cannot post mail messages
from the machine you're running &man.send-pr.1; on, your
from the machine you are running &man.send-pr.1; on, your
problem report will not reach the GNATS database. For details
on the setup of mail on &os;, see the <quote>Electronic
Mail</quote> chapter of the &os; Handbook at

View file

@ -486,7 +486,7 @@ applicable.</para>
<para>Occasionally, a last minute fix may be required
<emphasis>after</emphasis> the final tags have been created.
In practice this isn't a problem, since <acronym>CVS</acronym>
In practice this is not a problem, since <acronym>CVS</acronym>
allows tags to be manipulated with <command>cvs
tag -d <replaceable>tagname filename</replaceable></command>.
It is very important that any last minute changes be tagged
@ -900,7 +900,7 @@ applicable.</para>
encourage you to document your enhancements! The FreeBSD community
can only help support users of the software we provide. We
certainly encourage innovation in the form of advanced
installation and administration tools, for example, but we can't
installation and administration tools, for example, but we cannot
be expected to answer questions about it.</para>
<sect2>
@ -1046,7 +1046,7 @@ applicable.</para>
opportunity to take on some of the release engineering
responsibilities for FreeBSD 4.4 and also for all of his work
throughout the years making FreeBSD what it is today. Of course
the release wouldn't have been possible without all of the
the release would not have been possible without all of the
release-related work done by &a.asami;, &a.steve;, &a.bmah;, &a.nik;,
&a.obrien;, &a.kris;, &a.jhb; and the rest of the FreeBSD development
community. I would also like to thank &a.rgrimes;, &a.phk;, and others