remove backslash escapes for underscore in doc references

doc/src/compute_rdf.rst

@@ -45,7 +45,7 @@ Define a computation that calculates the radial distribution function
 (RDF), also called g(r), and the coordination number for a group of
 particles.  Both are calculated in histogram form by binning pairwise
 distances into *Nbin* bins from 0.0 to the maximum force cutoff
-defined by the :doc:`pair\_style <pair_style>` command or the cutoff
+defined by the :doc:`pair_style <pair_style>` command or the cutoff
 distance *Rcut* specified via the *cutoff* keyword.  The bins are of
 uniform size in radial distance.  Thus a single bin encompasses a thin
 shell of distances in 3d and a thin ring of distances in 2d.
@@ -53,9 +53,9 @@ shell of distances in 3d and a thin ring of distances in 2d.
 .. note::
 
    If you have a bonded system, then the settings of
-   :doc:`special\_bonds <special_bonds>` command can remove pairwise
+   :doc:`special_bonds <special_bonds>` command can remove pairwise
    interactions between atoms in the same bond, angle, or dihedral.  This
-   is the default setting for the :doc:`special\_bonds <special_bonds>`
+   is the default setting for the :doc:`special_bonds <special_bonds>`
    command, and means those pairwise interactions do not appear in the
    neighbor list.  Because this fix uses a neighbor list, it also means
    those pairs will not be included in the RDF. This does not apply when
@@ -65,11 +65,11 @@ shell of distances in 3d and a thin ring of distances in 2d.
    zero (e.g. 1.0e-50). Another workaround is to write a dump file, and
    use the :doc:`rerun <rerun>` command to compute the RDF for snapshots in
    the dump file.  The rerun script can use a
-   :doc:`special\_bonds <special_bonds>` command that includes all pairs in
+   :doc:`special_bonds <special_bonds>` command that includes all pairs in
    the neighbor list.
 
 By default the RDF is computed out to the maximum force cutoff defined
-by the :doc:`pair\_style <pair_style>` command.  If the *cutoff* keyword
+by the :doc:`pair_style <pair_style>` command.  If the *cutoff* keyword
 is used, then the RDF is computed accurately out to the *Rcut* > 0.0
 distance specified.
 
@@ -87,7 +87,7 @@ distance specified.
    timestep, whichever is less frequent), which is inefficient.  LAMMPS
    will warn you if this is the case.  If you specify a *Rcut* > force
    cutoff, you must insure ghost atom information out to *Rcut* + *skin*
-   is communicated, via the :doc:`comm\_modify cutoff <comm_modify>`
+   is communicated, via the :doc:`comm_modify cutoff <comm_modify>`
    command, else the RDF computation cannot be performed, and LAMMPS will
    give an error message.  The *skin* value is what is specified with the
    :doc:`neighbor <neighbor>` command.  In this case, you are forcing a
@@ -120,7 +120,7 @@ by *itypeN* are the central atom, and atoms of any of the range of
 types represented by *jtypeN* are the distribution atom.
 
 Pairwise distances are generated by looping over a pairwise neighbor
-list, just as they would be in a :doc:`pair\_style <pair_style>`
+list, just as they would be in a :doc:`pair_style <pair_style>`
 computation.  The distance between two atoms I and J is included in a
 specific histogram if the following criteria are met:
 
@@ -205,12 +205,12 @@ change from zero to one at the location of the spike in g(r).
    parallel efficiency and scaling. For systems, where only the type
    of atoms changes (e.g. when using :doc:`fix atom/swap <fix_atom_swap>`),
    you need to explicitly request the dynamic normalization updates
-   via :doc:`compute\_modify dynamic yes <compute_modify>`
+   via :doc:`compute_modify dynamic yes <compute_modify>`
 
 Related commands
 """"""""""""""""
 
-:doc:`fix ave/time <fix_ave_time>`, :doc:`compute\_modify <compute_modify>`,
+:doc:`fix ave/time <fix_ave_time>`, :doc:`compute_modify <compute_modify>`,
 :doc:`compute adf <compute_adf>`
 
 Default