summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorceri <ceri@FreeBSD.org>2004-02-18 18:52:09 +0000
committerceri <ceri@FreeBSD.org>2004-02-18 18:52:09 +0000
commite28335f600b7b4df63115018a8fdb0fb60df7e3e (patch)
treed3feb2fcbe67ac522c0f6e4f88e803d2d15ef136 /share
parent6730a7920d9439d6dafcdfa57e96ebcd9dba1c8e (diff)
downloadFreeBSD-src-e28335f600b7b4df63115018a8fdb0fb60df7e3e.zip
FreeBSD-src-e28335f600b7b4df63115018a8fdb0fb60df7e3e.tar.gz
Correct minor typos.
Diffstat (limited to 'share')
-rw-r--r--share/man/man7/security.74
1 files changed, 2 insertions, 2 deletions
diff --git a/share/man/man7/security.7 b/share/man/man7/security.7
index f0a63b0..3c1ad0e 100644
--- a/share/man/man7/security.7
+++ b/share/man/man7/security.7
@@ -218,7 +218,7 @@ servers.
.Pp
Using something like kerberos also gives you the ability to disable or
change the password for a staff account in one place and have it immediately
-effect all the machine the staff member may have an account on. If a staff
+effect all the machines the staff member may have an account on. If a staff
member's account gets compromised, the ability to instantly change his
password on all machines should not be underrated. With discrete passwords,
changing a password on N machines can be a mess. You can also impose
@@ -441,7 +441,7 @@ options
.Xr mount 8 )
are what you want to look into. I would scan them anyway at least once a
week, since the object of this layer is to detect a break-in whether or
-not the breakin is effective.
+not the break-in is effective.
.Pp
Process accounting
(see
OpenPOWER on IntegriCloud