correct various misspelled words and remove corresponding false positives

doc/src/Build_basics.rst

@@ -317,7 +317,7 @@ Several options are available and "mode=exe" is the default.
 .. code-block:: bash
 
    make machine               # build LAMMPS executable lmp_machine
-   mkae mode=exe machine      # same as "make machine"
+   make mode=exe machine      # same as "make machine"
    make mode=lib machine      # build LAMMPS static lib liblammps_machine.a
    make mode=shlib machine    # build LAMMPS shared lib liblammps_machine.so
    make mode=shexe machine    # same as "mode=exe" but uses objects from "mode=shlib"

doc/src/Build_cmake.rst

@@ -112,7 +112,7 @@ folder, recreate the directory and start over.
 The cmake command takes one required argument, which is the LAMMPS
 cmake directory which contains the CMakeLists.txt file.
 
-The argument can be preceeded or followed by various CMake
+The argument can be prefixed or followed by various CMake
 command-line options.  Several useful ones are:
 
 .. code-block:: bash

doc/src/Build_settings.rst

@@ -95,7 +95,7 @@ to assist:
    FFT_LIB =       -lfftw3 -lfftw3_omp # FFTW3 double precision with threads (needs -DFFT_FFTW_THREADS)
    FFT_LIB =       -lfftw3 -lfftw3f    # FFTW3 single precision
    FFT_LIB =       -lmkl_intel_lp64 -lmkl_sequential -lmkl_core   # MKL with Intel compiler, serial interface
-   FFT_LIB =       -lmkl_gf_lp64 -lmkl_sequential -lmkl_core      # MKL with GNU compier, serial interface
+   FFT_LIB =       -lmkl_gf_lp64 -lmkl_sequential -lmkl_core      # MKL with GNU compiler, serial interface
    FFT_LIB =       -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core # MKL with Intel compiler, threaded interface
    FFT_LIB =       -lmkl_gf_lp64 -lmkl_gnu_thread -lmkl_core      # MKL with GNU compiler, threaded interface
    FFT_LIB =       -lmkl_rt            # MKL with automatic runtime selection of interface libs

doc/src/Howto_chunk.rst

@@ -110,7 +110,7 @@ of a center of mass, which requires summing mass\*position over the
 atoms and then dividing by summed mass.
 
 All of these computes produce a global vector or global array as
-output, wih one or more values per chunk.  The output can be used in
+output, with one or more values per chunk.  The output can be used in
 various ways:
 
 * As input to the :doc:`fix ave/time <fix_ave_time>` command, which can

doc/src/Packages_details.rst

@@ -746,7 +746,7 @@ invoked at run time via the "-sf opt" or "-suffix opt" :doc:`command-line switch
 have styles optimized for CPU performance.
 
 **Authors:** James Fischer (High Performance Technologies), David Richie,
-and Vincent Natoli (Stone Ridge Technolgy).
+and Vincent Natoli (Stone Ridge Technology).
 
 **Install:**
 

doc/src/Run_basics.rst

@@ -11,7 +11,7 @@ Using the "-in in.file" variant is recommended:
    $ lmp_serial < in.file
    $ /path/to/lammps/src/lmp_serial -i in.file
    $ mpirun -np 4 lmp_mpi -in in.file
-   $ mpirun -np 8 /path/to//lammps/src/lmp_mpi -in in.file
+   $ mpirun -np 8 /path/to/lammps/src/lmp_mpi -in in.file
    $ mpirun -np 6 /usr/local/bin/lmp -in in.file
 
 You normally run the LAMMPS command in the directory where your input

doc/src/USER/atc/man_boundary.html

@@ -25,7 +25,7 @@
 syntax</a></h4>
 <p>fix_modify AtC boundary type &lt;atom-type-id&gt;</p>
 <ul>
-<li>&lt;atom-type-id&gt; = type id for atoms that represent a ficticious boundary internal to the FE mesh </li>
+<li>&lt;atom-type-id&gt; = type id for atoms that represent a fictitious boundary internal to the FE mesh </li>
 </ul>
 <h4><a class="anchor" id="examples">
 examples</a></h4>

doc/src/USER/atc/man_fix_atc.html

@@ -85,7 +85,7 @@ description</a></h4>
  fix AtC kernel quartic_sphere 10.0 <br/>
  <br/>
  # create a uniform 1 x 1 x 1 mesh that covers region contain the group <br/>
- # with periodicity this effectively creats a system average <br/>
+ # with periodicity this effectively creates a system average <br/>
  fix_modify AtC mesh create 1 1 1 box p p p <br/>
 <br/>
  # change from default lagrangian map to eulerian <br/>

doc/src/fix_atc.rst

@@ -83,7 +83,7 @@ likewise for this post-processing example:
     fix AtC kernel quartic_sphere 10.0
 
     # create a uniform 1 x 1 x 1 mesh that covers region contain the group
-    # with periodicity this effectively creats a system average
+    # with periodicity this effectively creates a system average
     fix_modify AtC mesh create 1 1 1 box p p p
 
     # change from default lagrangian map to eulerian

doc/src/fix_ave_correlate_long.rst

@@ -51,7 +51,7 @@ Syntax
        *nlen* args = Nlen
          Nlen = length of each correlator
        *ncount* args = Ncount
-         Ncount = number of values over which succesive correlators are averaged
+         Ncount = number of values over which successive correlators are averaged
 
 Examples
 """"""""

doc/src/kim_commands.rst

@@ -41,7 +41,7 @@ Syntax
             on the prefix specified in *variable* and a number appended to
             indicate which element in the list of values is in the variable.
      *explicit* = returns the values separately in one more more variable names
-            provided as arguments that preceed *formatarg*\ . [default for *kim_param*]
+            provided as arguments that precede *formatarg*\ . [default for *kim_param*]
 
 * query\_function = name of the OpenKIM web API query function to be used
 * queryargs = a series of *keyword=value* pairs that represent the web query; supported keywords depend on the query function

doc/src/pair_meamc.rst

@@ -119,7 +119,7 @@ that will be used with other potentials.
    filenames can appear in any order, e.g. "Si C" or "C Si" in the
    example above.  However, if the 2nd filename is not NULL (as in the
    example above), it contains settings that are Fortran-indexed for the
-   elements that preceed it.  Thus you need to insure you list the
+   elements that precede it.  Thus you need to insure you list the
    elements between the filenames in an order consistent with how the
    values in the 2nd filename are indexed.  See details below on the
    syntax for settings in the 2nd file.
@@ -230,7 +230,7 @@ where
                    hcp = hexagonal close-packed
                    dim = dimer
                    dia = diamond (interlaced fcc for alloy)
-                   dia3= diamond structure with primary 1NN and secondary 3NN interation
+                   dia3= diamond structure with primary 1NN and secondary 3NN interaction
                    b1  = rock salt (NaCl structure)
                    c11 = MoSi2 structure
                    l12 = Cu3Au structure (lower case L, followed by 12)

doc/src/rerun.rst

@@ -53,7 +53,7 @@ computed on the shapshot to produce thermodynamic or other output.
 This can be useful in the following kinds of scenarios, after an
 initial simulation produced the dump file:
 
-* Compute the energy and forces of snaphots using a different potential.
+* Compute the energy and forces of snapshots using a different potential.
 * Calculate one or more diagnostic quantities on the snapshots that
   weren't computed in the initial run.  These can also be computed with
   settings not used in the initial run, e.g. computing an RDF via the

doc/utils/sphinx-config/false_positives.txt

@@ -2279,8 +2279,6 @@ Prakash
 pre
 Pre
 prec
-preceed
-preceeded
 precession
 prefactor
 prefactors
@@ -2673,7 +2671,6 @@ smtbq
 sna
 snad
 snapcoeff
-snaphots
 snapparam
 snav
 Snodin
@@ -2817,7 +2814,6 @@ tdamp
 tdpd
 tDPD
 Tdrude
-Technolgy
 Telsa
 tempCorrCoeff
 templated
@@ -3140,7 +3136,6 @@ Whelan
 whitesmoke
 Wi
 Wicaksono
-wih
 Wijk
 Wikipedia
 wildcard