docs: update install section

doc/src/Install_git.rst

@@ -60,7 +60,7 @@ between them at any time using "git checkout <branch name>".)
    files (mostly by accident).  If you do not need access to the entire
    commit history (most people don't), you can speed up the "cloning"
    process and reduce local disk space requirements by using the
-   *--depth* git command line flag.  That will create a "shallow clone"
+   ``--depth`` git command line flag.  That will create a "shallow clone"
    of the repository, which contains only a subset of the git history.
    Using a depth of 1000 is usually sufficient to include the head
    commits of the *develop*, the *release*, and the *maintenance*
@@ -122,7 +122,7 @@ changed.  How to do this depends on the build system you are using.
 
       .. code-block:: bash
 
-         cmake . --build
+         cmake --build .
 
       CMake should auto-detect whether it needs to re-run the CMake
       configuration step and otherwise redo the build for all files

doc/src/Install_tarball.rst

@@ -31,7 +31,7 @@ command:
    tar -xzvf lammps*.tar.gz
 
 This will create a LAMMPS directory with the version date in its name,
-e.g. lammps-28Mar23.
+e.g. ``lammps-28Mar23``.
 
 ----------
 

doc/src/Install_windows.rst

@@ -34,7 +34,7 @@ When you download the installer package, you run it on your Windows
 machine.  It will then prompt you with a dialog, where you can choose
 the installation directory, unpack and copy several executables,
 potential files, documentation PDFs, selected example files, etc.  It
-will then update a few system settings (e.g. PATH, LAMMPS_POTENTIALS)
+will then update a few system settings (e.g. ``PATH``, ``LAMMPS_POTENTIALS``)
 and add an entry into the Start Menu (with references to the
 documentation, LAMMPS homepage and more).  From that menu, there is
 also a link to an uninstaller that removes the files and undoes the