Clarify the unique groups scheme by mentioning that the 002 umask

is instead of the usual 022 umask, and explain that what the scheme
still prevents is unwanted changes, not prying eyes.

While I'm here, mess with the phrasing and line-breaks a bit.

1 files changed, 5 insertions, 3 deletions

diff --git a/usr.sbin/adduser/adduser.8 b/usr.sbin/adduser/adduser.8
index 0f52c3b9956a..5d76ecad2347 100644
--- a/usr.sbin/adduser/adduser.8
+++ b/usr.sbin/adduser/adduser.8
@@ -99,9 +99,11 @@ If not empty, password is encoded with
 Perhaps you're missing what
 .Em can
 be done with this scheme that falls apart
-with most other schemes.  With each user in his/her own group the user can
-safely run with a umask of 002 and have files created in their home directory
-and not worry about others being able to read them.
+with most other schemes.
+With each user in his/her own group the user can
+safely run with a umask of 002 instead of the usual 022
+and create files in their home directory
+without worrying about others being able to change them.
 .Pp
 For a shared area you create a separate uid/gid (like cvs or ncvs on freefall),
 you place each person that should be able to access this area into that new