diff --git a/doc/man/man1/sbatch.1 b/doc/man/man1/sbatch.1
index 184f97387db712e2f44fea035033378bd49d93e0..8ea5cd229ae444c59cb3405b610c41ecac241997 100644
--- a/doc/man/man1/sbatch.1
+++ b/doc/man/man1/sbatch.1
@@ -348,7 +348,8 @@ Identify which environment variables are propagated to the batch job.
 Multiple environment variable names should be comma separated.
 Environment variable names may be specified to propagate the current
 value of those variables (e.g. "\-\-export=EDITOR") or specific values
-for the variables may be exported (e.g.. "\-\-export=EDITOR=/bin/vi").
+for the variables may be exported (e.g.. "\-\-export=EDITOR=/bin/vi")
+in addition to the environment variables that would otherwise be set.
 This option particularly important for jobs that are submitted on one cluster
 and execute on a different cluster (e.g. with different paths). By default all
 environment variables are propagated. If the argument is \fINONE\fR or
diff --git a/doc/man/man1/srun.1 b/doc/man/man1/srun.1
index 4facd051ed7eab4aa4255fe580977d5e6e553e73..cec6d3709940cad8aa20b3ca41385b81b9b2aa2c 100644
--- a/doc/man/man1/srun.1
+++ b/doc/man/man1/srun.1
@@ -581,7 +581,8 @@ Identify which environment variables are propagated to the laucnhed application.
 Multiple environment variable names should be comma separated.
 Environment variable names may be specified to propagate the current
 value of those variables (e.g. "\-\-export=EDITOR") or specific values
-for the variables may be exported (e.g.. "\-\-export=EDITOR=/bin/vi").
+for the variables may be exported (e.g.. "\-\-export=EDITOR=/bin/vi")
+in addition to the environment variables that would otherwise be set.
 By default all environment variables are propagated.
 
 .TP