From nobody@FreeBSD.org  Mon May 10 02:28:36 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1DAF016A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 10 May 2004 02:28:36 -0700 (PDT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CFFE843D48
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 10 May 2004 02:28:35 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i4A9ST0m041985
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 10 May 2004 02:28:29 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i4A9STqI041982;
	Mon, 10 May 2004 02:28:29 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200405100928.i4A9STqI041982@www.freebsd.org>
Date: Mon, 10 May 2004 02:28:29 -0700 (PDT)
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: freebsd-gnats-submit@FreeBSD.org
Subject: [PATCH] proposed dialup-firewall article wording change
X-Send-Pr-Version: www-2.3

>Number:         66442
>Category:       docs
>Synopsis:       [PATCH] proposed dialup-firewall article wording change
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    josef
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon May 10 02:30:16 PDT 2004
>Closed-Date:    Mon May 10 02:57:23 PDT 2004
>Last-Modified:  Mon May 10 02:57:23 PDT 2004
>Originator:     Giorgos Keramidas
>Release:        5-CURRENT
>Organization:
>Environment:
>Description:
Both paragraphs listed in the diff below start with "First".  Surely one of them must be "second" :-)

The rewording is probably suboptimal, but if anyone has a better idea about a way to keep the changes minimal and avoid repeatedly using the same word (First), go for it.
>How-To-Repeat:

>Fix:
%%
--- article.sgml.orig   2004-05-10 10:34:03.000000000 +0300
+++ article.sgml.new    2004-05-10 10:33:54.000000000 +0300
@@ -161,17 +161,17 @@
     <para>First, let's start with the basics of closed firewalling.
       Closed firewalling is based on the idea that everything is denied
       by default.  The system administrator may then explicitly add
       rules for traffic that he or she would like to allow.  Rules
       should be in the order of allow first, and then deny.  The premise
       is that you add the rules for everything you would like to allow,
       and then everything else is automatically denied.</para>

-    <para>First off, let's create the directory where we will store our
+    <para>Following that, let's create the directory where we will store our
       firewall rules.  In this example, we'll 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
       can change this filename to anything you wish.  This guide merely
       gives an example of a filename you may want to use.</para>

     <para>Now, let's look at a nicely commented sample firewall
%%
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-doc->josef 
Responsible-Changed-By: josef 
Responsible-Changed-When: Mon May 10 02:37:18 PDT 2004 
Responsible-Changed-Why:  
i'll handle this one. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=66442 
State-Changed-From-To: open->closed 
State-Changed-By: josef 
State-Changed-When: Mon May 10 02:57:14 PDT 2004 
State-Changed-Why:  
Committed, thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=66442 
>Unformatted:
