6591 resource_controls(5) should talk about project.cpu-cap not project.cpu-caps

@@ -5,11 +5,10 @@
 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
 .TH RESOURCE_CONTROLS 5 "Jul 19, 2013"
 .SH NAME
 resource_controls \- resource controls available through project database
 .SH DESCRIPTION
-.sp
 .LP
 The resource controls facility is configured through the project database. See
 \fBproject\fR(4). You can set and modify resource controls through the
 following utilities:
 .RS +4

@@ -190,11 +189,11 @@
 .RE
 
 .sp
 .ne 2
 .na
-\fB\fBproject.cpu-caps\fR\fR
+\fB\fBproject.cpu-cap\fR\fR
 .ad
 .sp .6
 .RS 4n
 Maximum amount of CPU resources that a project can use. The unit used is the
 percentage of a single CPU that can be used by all user threads in a project.

@@ -475,11 +474,10 @@
 
 .sp
 .LP
 See \fBzones\fR(5).
 .SS "Units Used in Resource Controls"
-.sp
 .LP
 Resource controls can be expressed as in units of size (bytes), time (seconds),
 or as a count (integer). These units use the strings specified below.
 .sp
 .in +2

@@ -561,11 +559,10 @@
 .LP
 Note that unit modifiers (for example, \fB5G\fR) are accepted by the
 \fBprctl\fR(1), \fBprojadd\fR(1M), and \fBprojmod\fR(1M) commands. You cannot
 use unit modifiers in the project database itself.
 .SS "Resource Control Values and Privilege Levels"
-.sp
 .LP
 A threshold value on a resource control constitutes a point at which local
 actions can be triggered or global actions, such as logging, can occur.
 .sp
 .LP

@@ -630,11 +627,10 @@
 task.max-lwps=(priv,1K,deny)
 .fi
 .in -2
 
 .SS "Global and Local Actions on Resource Control Values"
-.sp
 .LP
 There are two categories of actions on resource control values: global and
 local.
 .sp
 .LP

@@ -856,11 +852,10 @@
 controls with the \fBRCTL_GLOBAL_CPUTIME\fR property
 (\fBprocess.max-cpu-time\fR). See \fBrctlblk_set_value\fR(3C).
 .RE
 
 .SS "Resource Control Flags and Properties"
-.sp
 .LP
 Each resource control on the system has a certain set of associated properties.
 This set of properties is defined as a set of flags, which are associated with
 all controlled instances of that resource. Global flags cannot be modified, but
 the flags can be retrieved by using either \fBrctladm\fR(1M) or the

@@ -961,20 +956,18 @@
 and the \fBinf\fR (\fBRCTL_GLOBAL_INFINITE\fR) flag is defined for this
 resource control. An \fBinf\fR value has an infinite quantity. The value is
 never enforced. Hence, as configured, both threshold quantities represent
 infinite values that are never exceeded.
 .SS "Resource Control Enforcement"
-.sp
 .LP
 More than one resource control can exist on a resource. A resource control can
 exist at each containment level in the process model. If resource controls are
 active on the same resource at different container levels, the smallest
 container's control is enforced first. Thus, action is taken on
 \fBprocess.max-cpu-time\fR before \fBtask.max-cpu-time\fR if both controls are
 encountered simultaneously.
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for a description of the following attributes:
 .sp
 
 .sp

@@ -986,11 +979,10 @@
 _
 Interface Stability     Evolving
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBprctl\fR(1), \fBpooladm\fR(1M), \fBpoolcfg\fR(1M), \fBprojadd\fR(1M),
 \fBprojmod\fR(1M), \fBrctladm\fR(1M), \fBsetrctl\fR(2),
 \fBrctlblk_set_value\fR(3C), \fBlibpool\fR(3LIB), \fBproject\fR(4),
 \fBattributes\fR(5), \fBFSS\fR(7)