os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove some contractions.

Browse source 
Submitted by:	Joel Dahl <joel@automatvapen.se>
PR:		docs/77729
This commit is contained in:
Simon L. B. Nielsen 2005-02-19 14:03:54 +00:00
parent aa6f2cff76
commit 5c16ea2707
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=23820
3 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml
View file

@ -258,7 +258,7 @@
<entry>PF is part of the base system.
Do <emphasis>not</emphasis> use the
<filename role="package">security/pf</filename> port
on these versions of &os;. It won't work.
on these versions of &os;. It will not work.
Use the &man.pf.4; support of the base system instead.</entry>
</row>
</tbody>
@ -2587,7 +2587,7 @@ ks="keep-state" # just too lazy to key this each time
may be allowed in by the later authorized service rules.
Second reason is that by having a rule that explicitly
blocks selected packets that I receive on an infrequent
bases and don't want to see in the log, this keeps them from
bases and do not want to see in the log, this keeps them from
being caught by the last rule in the section which blocks
and logs all packets which have fallen through the rules.
The last rule in the section which blocks and logs all

2
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -331,7 +331,7 @@ R-deps: </screen>
<replaceable>string</replaceable> is some text to search for.
This searches port names, comments, descriptions and
dependencies and can be used to find ports which relate to a
particular subject if you don't know the name of the program
particular subject if you do not know the name of the program
you are looking for.</para>
<para>In both of these cases, the search string is case-insensitive.

10
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -2425,7 +2425,7 @@ Verifying password - Password: <userinput>xxxxxxxx</userinput></screen>
<para>Now it is time to start up the <acronym>KDC</acronym> services.
Run <command>/etc/rc.d/kerberos start</command> and
<command>/etc/rc.d/kadmind start</command> to bring up the
services. Note that you won't have any kerberized daemons running
services. Note that you will not have any kerberized daemons running
at this point but you should be able to confirm the that the
<acronym>KDC</acronym> is functioning by obtaining and listing a
ticket for the principal (user) that you just created from the
@ -2697,7 +2697,7 @@ jdoe@example.org</screen>
and reverse) in <acronym>DNS</acronym> (or
<filename>/etc/hosts</filename> as a minimum). CNAMEs
will work, but the A and PTR records must be correct and in
place. The error message isn't very intuitive:
place. The error message is not very intuitive:
<errorname>Kerberos5 refuses authentication because Read req
failed: Key table entry not found</errorname>.</para>
</listitem>
@ -3371,7 +3371,7 @@ options IPSEC_DEBUG #debug for IP security
</listitem>
<listitem>
<para>The internal addresses of the two networks can be
public or private IP addresses, it doesn't matter. You can
public or private IP addresses, it does not matter. You can
be running NAT on the gateway machine if necessary.</para>
</listitem>
<listitem>
@ -3733,7 +3733,7 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
</listitem>
<listitem>
<para>There must be a mechanism for specifying which traffic
should be encrypted. Obviously, you don't want to encrypt
should be encrypted. Obviously, you do not want to encrypt
all your outgoing traffic -- you only want to encrypt the
traffic that is part of the VPN. The rules that you put in
place to determine what traffic will be encrypted are called
@ -3811,7 +3811,7 @@ options IPSEC_ESP
this to encrypt the traffic over the VPN. They periodically
change this secret, so that even if an attacker were to crack one
of the keys (which is as theoretically close to unfeasible as it
gets) it won't do them much good -- by the time they've cracked
gets) it will not do them much good -- by the time they have cracked
the key the two daemons have chosen another one.</para>
<para>racoon's configuration is stored in