git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@11058 f3b2605a-c512-4ea7-a41b-209d697bcdaa

doc/clear.html

@@ -25,9 +25,9 @@ clear
 </P>
 <P>This command deletes all atoms, restores all settings to their default
 values, and frees all memory allocated by LAMMPS.  Once a clear
-command has been executed, it is as if LAMMPS were starting over, with
+command has been executed, it is almost as if LAMMPS were starting
-only the exceptions noted below.  This command enables multiple jobs
+over, with only the exceptions noted below.  This command enables
-to be run sequentially from one input script.
+multiple jobs to be run sequentially from one input script.
 </P>
 <P>These settings are not affected by a clear command: the working
 directory (<A HREF = "shell.html">shell</A> command), log file status

doc/clear.txt

@@ -22,9 +22,9 @@ clear
 
 This command deletes all atoms, restores all settings to their default
 values, and frees all memory allocated by LAMMPS.  Once a clear
-command has been executed, it is as if LAMMPS were starting over, with
+command has been executed, it is almost as if LAMMPS were starting
-only the exceptions noted below.  This command enables multiple jobs
+over, with only the exceptions noted below.  This command enables
-to be run sequentially from one input script.
+multiple jobs to be run sequentially from one input script.
 
 These settings are not affected by a clear command: the working
 directory ("shell"_shell.html command), log file status

doc/dump_modify.html

@@ -145,13 +145,13 @@ this keyword has no further effect.
 </P>
 <HR>
 
-<P>The <I>buffer</I> keyword applies only to dump styles <I>atom</I>, <I>custom</I>,
+<P>The <I>buffer</I> keyword applies only to dump styles <I>atom</I>, <I>cfg</I>,
-<I>local</I>, and <I>xyz</I>.  It also applies only to text output files, not to
+<I>custom</I>, <I>local</I>, and <I>xyz</I>.  It also applies only to text output
-binary or gzipped files.  If specified as <I>yes</I>, which is the default,
+files, not to binary or gzipped files.  If specified as <I>yes</I>, which
-then each processor writes its output into an internal text buffer,
+is the default, then each processor writes its output into an internal
-which is then sent to the processor(s) which perform file writes, and
+text buffer, which is then sent to the processor(s) which perform file
-written by those processors(s) as one large chunk of text.  If
+writes, and written by those processors(s) as one large chunk of text.
-specified as <I>no</I>, each processor sends its per-atom data in binary
+If specified as <I>no</I>, each processor sends its per-atom data in binary
 format to the processor(s) which perform file wirtes, and those
 processor(s) format and write it line by line into the output file.
 </P>

doc/dump_modify.txt

@@ -133,13 +133,13 @@ this keyword has no further effect.
 
 :line
 
-The {buffer} keyword applies only to dump styles {atom}, {custom},
+The {buffer} keyword applies only to dump styles {atom}, {cfg},
-{local}, and {xyz}.  It also applies only to text output files, not to
+{custom}, {local}, and {xyz}.  It also applies only to text output
-binary or gzipped files.  If specified as {yes}, which is the default,
+files, not to binary or gzipped files.  If specified as {yes}, which
-then each processor writes its output into an internal text buffer,
+is the default, then each processor writes its output into an internal
-which is then sent to the processor(s) which perform file writes, and
+text buffer, which is then sent to the processor(s) which perform file
-written by those processors(s) as one large chunk of text.  If
+writes, and written by those processors(s) as one large chunk of text.
-specified as {no}, each processor sends its per-atom data in binary
+If specified as {no}, each processor sends its per-atom data in binary
 format to the processor(s) which perform file wirtes, and those
 processor(s) format and write it line by line into the output file.