diff --git a/en_US.ISO8859-1/articles/dialup-firewall/article.sgml b/en_US.ISO8859-1/articles/dialup-firewall/article.sgml
index a31da47e90..c9a1d72c18 100644
--- a/en_US.ISO8859-1/articles/dialup-firewall/article.sgml
+++ b/en_US.ISO8859-1/articles/dialup-firewall/article.sgml
@@ -145,7 +145,7 @@ ppp_profile="your_profile"
The rule set for the firewall
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.
@@ -159,7 +159,7 @@ ppp_profile="your_profile"
and then everything else is automatically denied.
Following that, let's create the directory where we will store our
- firewall rules. In this example, we'll use /etc/firewall. Change into the
directory and edit the file fwrules as we
specified in rc.conf. Please note that you
diff --git a/en_US.ISO8859-1/articles/hubs/article.sgml b/en_US.ISO8859-1/articles/hubs/article.sgml
index 7156aec574..b7b165f4db 100644
--- a/en_US.ISO8859-1/articles/hubs/article.sgml
+++ b/en_US.ISO8859-1/articles/hubs/article.sgml
@@ -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 Tier-1-mirrors.
- However you probably won't find a Tier-1-mirror,
+ However you probably will not find a Tier-1-mirror,
that is not also official.
diff --git a/en_US.ISO8859-1/articles/pam/article.sgml b/en_US.ISO8859-1/articles/pam/article.sgml
index f5d4cb58ab..9398f7bc1b 100644
--- a/en_US.ISO8859-1/articles/pam/article.sgml
+++ b/en_US.ISO8859-1/articles/pam/article.sgml
@@ -544,7 +544,7 @@ sshd password required pam_permit.so
modules.
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.
@@ -1261,7 +1261,7 @@ sshd password required pam_permit.so
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.
diff --git a/en_US.ISO8859-1/articles/problem-reports/article.sgml b/en_US.ISO8859-1/articles/problem-reports/article.sgml
index 6427d9224a..03affef18e 100644
--- a/en_US.ISO8859-1/articles/problem-reports/article.sgml
+++ b/en_US.ISO8859-1/articles/problem-reports/article.sgml
@@ -503,7 +503,7 @@
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 Electronic
Mail
chapter of the &os; Handbook at
diff --git a/en_US.ISO8859-1/articles/releng/article.sgml b/en_US.ISO8859-1/articles/releng/article.sgml
index 23234fe132..3566413169 100644
--- a/en_US.ISO8859-1/articles/releng/article.sgml
+++ b/en_US.ISO8859-1/articles/releng/article.sgml
@@ -486,7 +486,7 @@ applicable.
Occasionally, a last minute fix may be required
after the final tags have been created.
- In practice this isn't a problem, since CVS
+ In practice this is not a problem, since CVS
allows tags to be manipulated with cvs
tag -d tagname filename.
It is very important that any last minute changes be tagged
@@ -900,7 +900,7 @@ applicable.
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.
@@ -1046,7 +1046,7 @@ applicable.
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