svn commit: r42266 - head/en_US.ISO8859-1/books/handbook/security

Warren Block wblock at
Sat Jul 13 03:33:21 UTC 2013

Author: wblock
Date: Sat Jul 13 03:33:20 2013
New Revision: 42266

  Fix a wording bug: action to resource.  Also fix some title
  capitalization and redundancy issues.
  Submitted by:	MNIHKLOM (forum user, action/resource issue)


Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml
--- head/en_US.ISO8859-1/books/handbook/security/chapter.xml	Sat Jul 13 01:50:56 2013	(r42265)
+++ head/en_US.ISO8859-1/books/handbook/security/chapter.xml	Sat Jul 13 03:33:20 2013	(r42266)
@@ -2783,7 +2783,7 @@ racoon_enable="yes"</programlisting>
-      <title>Enabling The SSH Server</title>
+      <title>Enabling the SSH Server</title>
@@ -2918,8 +2918,8 @@ bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8
 	is stored in <filename>~/.ssh/</filename> or
 	<filename>~/.ssh/</filename>, respectively for the
 	<acronym>DSA</acronym> and <acronym>RSA</acronym> key types.
-	The public key must be placed in the
-	<filename>~/.ssh/authorized_keys</filename> file of the
+	The public key must be placed in
+	<filename>~/.ssh/authorized_keys</filename> on the
 	remote machine for both <acronym>RSA</acronym> or
 	<acronym>DSA</acronym> keys in order for the setup to
@@ -2960,7 +2960,7 @@ bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8
     <sect2 id="security-ssh-agent">
-      <title>Using SSH Agent To Cache Keys</title>
+      <title>Using SSH Agent to Cache Keys</title>
       <para>To load <acronym>SSH</acronym> keys into memory for use,
 	without needing to type the passphrase each time, use
@@ -2990,7 +2990,7 @@ Identity added: /home/user/.ssh/id_dsa (
 	needs to be placed in <filename>~/.xinitrc</filename>.  This
 	provides the &man.ssh-agent.1; services to all programs
 	launched in <application>&xorg;</application>.  An example
-	<filename>~/.xinitrc</filename> file might look like
+	<filename>~/.xinitrc</filename> might look like
       <programlisting>exec ssh-agent <replaceable>startxfce4</replaceable></programlisting>
@@ -3217,7 +3217,7 @@ user at's p
     <title>Filesystem Access Control Lists
-      (<acronym>ACL</acronym>s)</title>
+      (<acronym>ACL</acronym>)s</title>
@@ -3744,7 +3744,7 @@ VII. References <co id="co-ref"/></progr
       Potentially a single, more constrained user would require
       an additional label added, the resource database needs to be
       built using <command>cap_mkdb</command>, edits made to
-      the <filename>/etc/master.passwd</filename> file.  In
+      <filename>/etc/master.passwd</filename>.  In
       addition, the password database must be rebuilt using
       <command>pwd_mkdb</command>.  This multi-step process could be
       very time consuming depending on how many users must be
@@ -3782,7 +3782,7 @@ options         RCTL</programlisting>
     <para>This rule shows a basic premise of a rule, here the
       subject is <literal>user</literal> and the subject-id
       is <literal>trhodes</literal>.  The maxproc is, of course,
-      max number of processes, which is considered the action.
+      max number of processes, which is considered the resource.
       The action here is set to <literal>deny</literal>, which blocks
       any new processes from being created.  In the previous example,
       the user, <literal>trhodes</literal> will be constrained
@@ -3808,7 +3808,7 @@ eval: Cannot fork: Resource temporarily 
     <screen>&prompt.root; <userinput>rctl -a jail:httpd:memoryuse:deny=2G/jail</userinput></screen>
     <para>Rules may also persist across reboots if they have been
-      added to <filename>/etc/rctl.conf</filename> file.  The
+      added to <filename>/etc/rctl.conf</filename>.  The
       format is a rule, without the preceding command.  For example,
       the previous rule could be added like the following:</para>

More information about the svn-doc-all mailing list