Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jan 2014 12:38:53 +0000 (UTC)
From:      Warren Block <wblock@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r43661 - head/en_US.ISO8859-1/books/handbook/firewalls
Message-ID:  <201401271238.s0RCcrwW098453@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: wblock
Date: Mon Jan 27 12:38:53 2014
New Revision: 43661
URL: http://svnweb.freebsd.org/changeset/doc/43661

Log:
  Expand a few contractions.

Modified:
  head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml	Mon Jan 27 12:36:13 2014	(r43660)
+++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml	Mon Jan 27 12:38:53 2014	(r43661)
@@ -1104,7 +1104,7 @@ pass inet proto icmp from any to $ext_if
 	    By default, Unix <command>traceroute</command> uses UDP
 	    connections according to a set formula based on
 	    destination.  The rule below works with
-	    <command>traceroute</command> on all unixes I've had
+	    <command>traceroute</command> on all Unixes I have had
 	    access to, including GNU/Linux:</para>
 
 	  <programlisting># allow out the default range for traceroute(8):
@@ -1125,7 +1125,7 @@ pass out on $ext_if inet proto udp from 
 	    details.</para>
 
 	  <para>Under any circumstances, this solution was lifted
-	    from an openbsd-misc post.  I've found that list, and
+	    from an openbsd-misc post.  I have found that list, and
 	    the searchable list archives (accessible among other
 	    places from <link xlink:href="http://marc.theaimsgroup.com/">http://marc.theaimsgroup.com/</link>),
 	    to be a very valuable resource whenever you need OpenBSD
@@ -1290,7 +1290,7 @@ Sep 26 03:12:44 skapet sshd[24703]: Fail
 	  solution.  Pass rules can be written so they maintain
 	  certain limits on what connecting hosts can do.  For good
 	  measure, violators can be banished to a table of addresses
-	  which are denied some or all access.  If desired, it's even
+	  which are denied some or all access.  If desired, it is even
 	  possible to drop all existing connections from machines
 	  which overreach the limits.  Here is how it is done:</para>
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201401271238.s0RCcrwW098453>