Date: Mon, 24 Sep 2001 14:15:53 +0300 (EEST) From: Giorgos Keramidas <charon@labs.gr> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/30785: replace inline text capitalization with proper use of <emphasis> tags in articles/dialup-firewall Message-ID: <200109241115.f8OBFrU08223@hades.hell.gr>
next in thread | raw e-mail | index | archive | help
>Number: 30785
>Category: docs
>Synopsis: replace inline text capitalization with proper use of <emphasis> tags in articles/dialup-firewall
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Sep 24 04:20:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Giorgos Keramidas
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD hades.hell.gr 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Tue Sep 4
19:49:44 EEST 2001 root@hades.hell.gr:/usr/obj/usr/src/sys/CHARON i386
>Description:
In a few places, the dialup-firewall article uses capitalization
of words like ``NOT'' to indicate emphasis. The attached patch
lowercases these and wraps them in <emphasis> tags.
>How-To-Repeat:
>Fix:
--- patch-aa begins here ---
Index: article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/dialup-firewall/article.sgml,v
retrieving revision 1.15
diff -u -r1.15 article.sgml
--- article.sgml 2 Sep 2001 10:37:26 -0000 1.15
+++ article.sgml 24 Sep 2001 11:11:55 -0000
@@ -94,7 +94,7 @@
</varlistentry>
</variablelist>
- <para>There are some other OPTIONAL items that you can compile
+ <para>There are some other <emphasis>optional</emphasis> items that you can compile
into the kernel for some added security. These are not required in
order to get firewalling to work, but some more paranoid users may
want to use them.</para>
@@ -107,7 +107,7 @@
<para>This option ignores TCP packets with SYN and FIN. This
prevents tools such as nmap etc from identifying the TCP/IP
stack of the machine, but breaks support for RFC1644
- extensions. This is NOT recommended if the machine will be
+ extensions. This is <emphasis>not</emphasis> recommended if the machine will be
running a web server.</para>
</listitem>
</varlistentry>
@@ -299,7 +299,7 @@
<emphasis>anything</emphasis> being diverted through the
<devicename>tun0</devicename> device. As far as it's
concerned incoming packets will speak only to the
- dynamically assigned IP address and NOT to the internal
+ dynamically assigned IP address and <emphasis>not</emphasis> to the internal
network. Note though that you can add a rule like
<literal>$fwcmd add deny all from 192.168.0.4:255.255.0.0
to any via tun0</literal> which would limit a host on your
--- patch-aa ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109241115.f8OBFrU08223>