From 5c16ea27070ed3e11b5f2e4a1a5407ab23bc7293 Mon Sep 17 00:00:00 2001 From: "Simon L. B. Nielsen" Date: Sat, 19 Feb 2005 14:03:54 +0000 Subject: [PATCH] Remove some contractions. Submitted by: Joel Dahl PR: docs/77729 --- en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml | 4 ++-- en_US.ISO8859-1/books/handbook/ports/chapter.sgml | 2 +- en_US.ISO8859-1/books/handbook/security/chapter.sgml | 10 +++++----- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml b/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml index d7c0894f28..74a443417e 100644 --- a/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml @@ -258,7 +258,7 @@ PF is part of the base system. Do not use the security/pf 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. @@ -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 diff --git a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml index 51512f40d8..6b82d91c36 100644 --- a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml @@ -331,7 +331,7 @@ R-deps: string 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. In both of these cases, the search string is case-insensitive. diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml index 9375779afd..5a9d4914f3 100644 --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml @@ -2425,7 +2425,7 @@ Verifying password - Password: xxxxxxxx Now it is time to start up the KDC services. Run /etc/rc.d/kerberos start and /etc/rc.d/kadmind start 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 KDC 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 and reverse) in DNS (or /etc/hosts 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: Kerberos5 refuses authentication because Read req failed: Key table entry not found. @@ -3371,7 +3371,7 @@ options IPSEC_DEBUG #debug for IP security 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. @@ -3733,7 +3733,7 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00" 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. racoon's configuration is stored in