Fix a variety of English style nits and other issues found with igor.
Reviewed by: gabor Approved by: wblock
This commit is contained in:
parent
93da362636
commit
7d35fc35d6
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=38454
2 changed files with 17 additions and 17 deletions
en_US.ISO8859-1/books/handbook
|
@ -796,7 +796,7 @@
|
|||
page should contain all of the necessary subscription
|
||||
instructions.</para>
|
||||
|
||||
<para>To actually post to a given list you simply send mail to
|
||||
<para>To actually post to a given list, send mail to
|
||||
<email><replaceable>listname</replaceable>@FreeBSD.org</email>. It will then
|
||||
be redistributed to mailing list members world-wide.</para>
|
||||
|
||||
|
@ -831,7 +831,7 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>The topic of any posting should adhere to the basic charter of
|
||||
the list it is posted to, e.g. if the list is about technical
|
||||
the list it is posted to, e.g., if the list is about technical
|
||||
issues then your posting should contain technical discussion.
|
||||
Ongoing irrelevant chatter or flaming only detracts from the value
|
||||
of the mailing list for everyone on it and will not be tolerated.
|
||||
|
@ -1337,7 +1337,7 @@
|
|||
<para><emphasis>Jobs offered and sought</emphasis></para>
|
||||
|
||||
<para>This is a forum for posting employment notices and
|
||||
resumes specifically related to &os;, e.g. if you are
|
||||
resumes specifically related to &os;, e.g., if you are
|
||||
seeking &os;-related employment or have a job involving
|
||||
&os; to advertise then this is the right place. This is
|
||||
<emphasis>not</emphasis> a mailing list for general
|
||||
|
|
|
@ -236,7 +236,7 @@
|
|||
url="http://pf4freebsd.love2party.net/"></ulink>.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Using the PF loadable kernel modules</title>
|
||||
<title>Using the PF Loadable Kernel Modules</title>
|
||||
|
||||
<para>To load the PF Kernel Module add the following line to
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
@ -281,7 +281,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>PF kernel options</title>
|
||||
<title>PF Kernel Options</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>kernel options</primary>
|
||||
|
@ -334,7 +334,7 @@ device pfsync</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Available rc.conf Options</title>
|
||||
<title>Available <filename>rc.conf</filename> Options</title>
|
||||
|
||||
<para>The following &man.rc.conf.5; statements configure
|
||||
<acronym>PF</acronym> and &man.pflog.4; at boot:</para>
|
||||
|
@ -566,7 +566,7 @@ options ALTQ_NOPCC # Required for SMP build</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Kernel options</title>
|
||||
<title>Kernel Options</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>kernel options</primary>
|
||||
|
@ -624,7 +624,7 @@ options IPFILTER_DEFAULT_BLOCK</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Available rc.conf Options</title>
|
||||
<title>Available <filename>rc.conf</filename> Options</title>
|
||||
|
||||
<para>To activate IPF at boot time, the following statements need to
|
||||
be added to <filename>/etc/rc.conf</filename>:</para>
|
||||
|
@ -888,7 +888,7 @@ LOG_ERR - packets which have been logged and which can be considered short</scre
|
|||
|
||||
<listitem>
|
||||
<para>The name of the interface the packet was processed on,
|
||||
e.g. <devicename>dc0</devicename>.</para>
|
||||
e.g., <devicename>dc0</devicename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -936,7 +936,7 @@ LOG_ERR - packets which have been logged and which can be considered short</scre
|
|||
<para>If the packet is an ICMP packet, there will be two fields
|
||||
at the end, the first always being <quote>ICMP</quote>, and the
|
||||
next being the ICMP message and sub-message type, separated by
|
||||
a slash, e.g. ICMP 3/3 for a port unreachable message.</para>
|
||||
a slash, e.g., ICMP 3/3 for a port unreachable message.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="firewalls-ipf-rules-script">
|
||||
|
@ -1089,7 +1089,7 @@ sh /etc/ipf.rules.script</programlisting>
|
|||
lock you out</emphasis> of the server. To be on the safe
|
||||
side, you may wish to consider performing the initial
|
||||
firewall configuration from the local console rather than
|
||||
doing it remotely e.g. via
|
||||
doing it remotely e.g., via
|
||||
<application>ssh</application>.</para>
|
||||
</warning>
|
||||
</sect2>
|
||||
|
@ -1902,7 +1902,7 @@ block in log first quick on dc0 all
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title><acronym>NAT</acronym> for a very large LAN</title>
|
||||
<title><acronym>NAT</acronym> for a Large LAN</title>
|
||||
|
||||
<para>For networks that have large numbers of PC's on the LAN or
|
||||
networks with more than a single LAN, the process of funneling
|
||||
|
@ -2326,7 +2326,7 @@ ipfw add deny out</programlisting>
|
|||
<programlisting>net.inet.ip.fw.verbose_limit=5</programlisting>
|
||||
</warning>
|
||||
|
||||
<para>If your machine is acting as a gateway, i.e. providing
|
||||
<para>If your machine is acting as a gateway, i.e., providing
|
||||
Network Address Translation (NAT) via &man.natd.8;, please
|
||||
refer to <xref linkend="network-natd"> for information
|
||||
regarding the required <filename>/etc/rc.conf</filename>
|
||||
|
@ -2408,7 +2408,7 @@ ipfw add deny out</programlisting>
|
|||
port. Packets destined for a specific service, originate from the
|
||||
source address using an unprivileged (high order) port and target
|
||||
the specific service port on the destination address. All the above
|
||||
parameters (i.e. ports and addresses) can be used as selection
|
||||
parameters (i.e., ports and addresses) can be used as selection
|
||||
criteria to create rules which will pass or block services.</para>
|
||||
|
||||
<indexterm>
|
||||
|
@ -2875,7 +2875,7 @@ ks="keep-state" # just too lazy to key this each time
|
|||
rules for services that are not required. To avoid logging
|
||||
undesired messages, add a <literal>deny</literal> rule in the
|
||||
inbound section. The <devicename>dc0</devicename> interface will
|
||||
will have to be changed in every rule, with the actual name of the
|
||||
have to be changed in every rule, with the actual name of the
|
||||
interface (NIC) that connects your system to the public Internet.
|
||||
For user <acronym>PPP</acronym>, this would be
|
||||
<devicename>tun0</devicename>.</para>
|
||||
|
@ -2977,7 +2977,7 @@ pif="dc0" # public interface name of NIC
|
|||
# Allow out Time
|
||||
$cmd 00260 allow tcp from any to any 37 out via $pif setup keep-state
|
||||
|
||||
# Allow out nntp news (i.e. news groups)
|
||||
# Allow out nntp news (i.e., news groups)
|
||||
$cmd 00270 allow tcp from any to any 119 out via $pif setup keep-state
|
||||
|
||||
# Allow out secure FTP, Telnet, and SCP
|
||||
|
@ -3289,7 +3289,7 @@ pif="rl0" # public interface name of NIC
|
|||
# Allow out Time
|
||||
$cmd 090 $skip tcp from any to any 37 out via $pif setup keep-state
|
||||
|
||||
# Allow out nntp news (i.e. news groups)
|
||||
# Allow out nntp news (i.e., news groups)
|
||||
$cmd 100 $skip tcp from any to any 119 out via $pif setup keep-state
|
||||
|
||||
# Allow out secure FTP, Telnet, and SCP
|
||||
|
|
Loading…
Reference in a new issue