fix spelling in MDI docs

doc/src/Howto_mdi.rst

@@ -72,7 +72,7 @@ either a stand-alone code or a plugin library.
 
 As explained on the `fix mdi/qm <fix_mdi_qm>` command doc page, it can
 be used to perform *ab initio* MD simulations or energy minimizations,
-or to evalute the quantum energy and forces for a series of
+or to evaluate the quantum energy and forces for a series of
 independent systems.  The examples/mdi directory has example input
 scripts for all of these use cases.
 

doc/src/Packages_details.rst

@@ -1479,7 +1479,7 @@ the :doc:`Build extras <Build_extras>` page.
 * lib/mdi/README
 * :doc:`Howto MDI <Howto_mdi>`
 * :doc:`mdi <mdi>`
-* :doc:`fix mdi/aimd <fix_mdi_aimd>`
+* :doc:`fix mdi/qm <fix_mdi_qm>`
 * examples/PACKAGES/mdi
 
 ----------

doc/src/fix_mdi_qm.rst

@@ -57,9 +57,9 @@ explained below.
 
 These are example use cases for this fix, discussed further below:
 
-* perform an ab intitio MD (AIMD) simulation with quantum forces
-* perform an energy minimziation with quantum forces
-* perform a nudged elatic band (NEB) calculation with quantum forces
+* perform an ab initio MD (AIMD) simulation with quantum forces
+* perform an energy minimization with quantum forces
+* perform a nudged elastic band (NEB) calculation with quantum forces
 * perform a QM calculation for a series of independent systems which LAMMPS reads or generates
 
 The code coupling performed by this command is done via the `MDI
@@ -71,7 +71,7 @@ information about how LAMMPS can operate as either an MDI driver or
 engine.
 
 The examples/mdi directory contains input scripts using this fix in
-the various use cases dicussed below.  In each case, two instances of
+the various use cases discussed below.  In each case, two instances of
 LAMMPS are used, once as an MDI driver, once as an MDI engine
 (surrogate for a QM code).  The examples/mdi/README file explains how
 to launch two codes so that they communicate via the MDI library using
@@ -157,7 +157,7 @@ atom coordinates.  The engine code computes quantum forces on each
 atom and the total energy of the system and returns them to LAMMPS.
 
 Note that if the AIMD simulation is an NPT or NPH model, or the energy
-minimization includesf :doc:`fix box relax <fix_box_relaxq>` to
+minimization includes :doc:`fix box relax <fix_box_relax>` to
 equilibrate the box size/shape, then LAMMPS computes a pressure.  This
 means the *virial* keyword should be set to *yes* so that the QM
 contribution to the pressure can be included.
@@ -172,7 +172,7 @@ atom coordinates and QM forces to a file.  Likewise the QM energy and
 virial could be output with the :doc:`thermo_style custom
 <thermo_style>` command.
 
-(3) To do a QM evaulation of energy and forces for a series of *N*
+(3) To do a QM evaluation of energy and forces for a series of *N*
 independent systems (simulation box and atoms), use *add no* and
 *every 1*.  Write a LAMMPS input script which loops over the *N*
 systems.  See the :doc:`Howto multiple <Howto_multiple>` doc page for
@@ -180,7 +180,7 @@ details on looping and removing old systems.  The series of systems
 could be initialized by reading them from data files with
 :doc:`read_data <read_data>` commands.  Or, for example, by using the
 :doc:`lattice <lattice>` , :doc:`create_atoms <create_atoms>`,
-:doc:`delete_atoms <deletea_atoms>`, and/or :doc:`displace_atoms
+:doc:`delete_atoms <delete_atoms>`, and/or :doc:`displace_atoms
 random <displace_atoms>` commands to generate a series of different
 systems.  At the end of the loop perform :doc:`run 0 <run>` and
 :doc:`write_dump <write_dump>` commands to invoke the QM code and

doc/src/mdi.rst

@@ -326,15 +326,15 @@ able to initiate and terminate the connection to the engine code.
 The only current MDI driver command in LAMMPS is the :doc:`fix mdi/qm
 <fix_mdi_qm>` command.  If it is only used once in an input script
 then it can initiate and terminate the connection.  But if it is being
-issuedd multiple times, e.g. in a loop that issues a :doc:`clear
-<clear>` command, then it cannot initiate/terminate the connection
+issued multiple times, e.g. in a loop that issues a :doc:`clear
+<clear>` command, then it cannot initiate or terminate the connection
 multiple times.  Instead, the *mdi connect* and *mdi exit* commands
-should be used outside the loop to intiate/terminate the connection.
+should be used outside the loop to initiate or terminate the connection.
 
 See the examples/mdi/in.series.driver script for an example of how
 this is done.  The LOOP in that script is reading a series of data
 file configurations and passing them to an MDI engine (e.g. quantum
-code) for enery and force evaluation.  A *clear* command inside the
+code) for energy and force evaluation.  A *clear* command inside the
 loop wipes out the current system so a new one can be defined.  This
 operation also destroys all fixes.  So the :doc:`fix mdi/qm
 <fix_mdi_qm>` command is issued once per loop iteration.  Note that it

doc/utils/sphinx-config/false_positives.txt

@@ -3679,13 +3679,19 @@ vx
 Vx
 vxcm
 vxmu
+vxx
+vxy
+vxz
 vy
 Vy
 vycm
+vyy
+vyz
 vz
 Vz
 vzcm
 vzi
+vzz
 Waals
 Wadley
 wallstyle