diff --git a/doc/man/man5/slurm.conf.5 b/doc/man/man5/slurm.conf.5
index d634ca5ba01675618ebb96c147f3f4eb965e45eb..04f5b0b9ae57dc15517625f209cf38c6e9813a15 100644
--- a/doc/man/man5/slurm.conf.5
+++ b/doc/man/man5/slurm.conf.5
@@ -136,7 +136,7 @@ Name that \fBBackupController\fR should be referred to in
 establishing a communications path. This name will 
 be used as an argument to the gethostbyname() function for 
 identification. For example, "elx0000" might be used to designate 
-the ethernet address for node "lx0000". 
+the Ethernet address for node "lx0000". 
 By default the \fBBackupAddr\fR will be identical in value to 
 \fBBackupController\fR.
 
@@ -182,7 +182,7 @@ Name that \fBControlMachine\fR should be referred to in
 establishing a communications path. This name will 
 be used as an argument to the gethostbyname() function for 
 identification. For example, "elx0000" might be used to designate 
-the ethernet address for node "lx0000". 
+the Ethernet address for node "lx0000". 
 By default the \fBControlAddr\fR will be identical in value to 
 \fBControlMachine\fR.
 
@@ -449,7 +449,7 @@ Acceptable values at present include "jobcomp/none", "jobcomp/filetxt",
 The default value is "jobcomp/none", which means that upon job completion 
 the record of the job is purged from the system.  If using the accounting 
 infrastructure this plugin may not be of interest since the information 
-here is reduntant.
+here is redundant.
 The value "jobcomp/filetxt" indicates that a record of the job should be 
 written to a text file specified by the \fBJobCompLoc\fR parameter.
 The value "jobcomp/mysql" indicates that a record of the job should be 
@@ -1446,7 +1446,16 @@ memory nodes if either will satisfy a job's requirements.
 The units of weight are arbitrary, but larger weights 
 should be assigned to nodes with more processors, memory, 
 disk space, higher processor speed, etc.
-Weight is an integer value with a default value of 1.
+Note that if a job allocation request can not be satisfied
+using the nodes with the lowest weight, the set of nodes
+with the next lowest weight is added to the set of nodes
+under consideration for use (repeat as needed for higher 
+weight values). If you absolutely want to minimize the number 
+of higher weight nodes allocated to a job (at a cost of higher 
+scheduling overhead), give each node a distinct \fBWeight\fR 
+value and they will be added to the pool of nodes being 
+considered for scheduling individually.
+The default value is 1.
 .LP
 The "DownNodes=" configuration permits you to mark certain nodes as in a 
 DOWN, DRAIN, FAIL, or FAILING state without altering the permanent 
@@ -1616,7 +1625,7 @@ Possible values for \fBShared\fR are "EXCLUSIVE", "FORCE", "YES", and "NO".
 .RS
 .TP 12
 \fBEXCLUSIVE\fR
-Aallocates entire nodes to jobs even with select/cons_res configured.
+Allocates entire nodes to jobs even with select/cons_res configured.
 This can be used to allocate whole nodes in some partitions 
 and individual processors in other partitions.
 .TP 
@@ -1633,7 +1642,7 @@ with gang scheduling (\fBSchedulerType=sched/gang\fR).
 .TP
 \fBYES\fR
 Make nodes in the partition available for sharing, but provides
-the user with a means of getting dediated resources.
+the user with a means of getting dedicated resources.
 If \fBSelectType=select/cons_res\fR, then resources will be 
 over\-subscribed unless explicitly disabled in the job submit 
 request using the "\-\-exclusive" option.