Fix cross references

Author: jorgepiloto

doc/source/guidelines/dev_practices.rst

@@ -11,7 +11,7 @@ coding paradigms:
    gained by following the basic guidelines listed in PEP 20. As suggested
    in these guidelines, focus on making your additions intuitive, novel,
    and helpful for PyAnsys users. When in doubt, use ``import this``.
-   For Ansys code quality standards, see :ref:`coding_style`.
+   For Ansys code quality standards, see :ref:`Coding Style`.
 
 #. Document your contributions. Include a docstring for any added
    function, method, or class, following `numpydocs docstring <https://numpydoc.readthedocs.io/en/latest/format.html>`_

doc/source/overview/administration.rst

@@ -43,7 +43,7 @@ description, or branch protection management.
 
 Each repository is expected to follow this minimum set of standards:
 
-- PEP8 code standards. See :ref:`best_practices`.
+- PEP8 code standards. See :ref:`PEP 8`.
 - CI/CD using GitHub actions or Azure DevOps to enforce coding standards.
 - Publicly hosted documentation describing the API and providing examples. See
   :ref:`Documentation Style`.

doc/source/overview/contributing.rst

@@ -82,7 +82,7 @@ When you are ready to start contributing code, see:
 
 - :ref:`development_practices` for information on how PyAnsys development is
   conducted
-- :ref:`best_practices` for information on how to style and format your
+- :ref:`PEP 8` for information on how to style and format your
   code to adhere to PyAnsys standards