Reformat PEP8 section

Author: jorgepiloto

doc/source/coding-style/index.rst

@@ -1,29 +1,30 @@
-.. _coding_style:
-
 Coding Style
-************
-
-PyAnsys libraries are expected to follow `PEP8`_ and
-be consistent in style and formatting with the 'big three'
-data science libraries: `NumPy`_, `SciPy`_, and `pandas`_.
-
-.. _NumPy: https://numpy.org/
-.. _SciPy: https://www.scipy.org/
-.. _pandas: https://pandas.pydata.org/
-.. _PEP8: https://www.python.org/dev/peps/pep-0008/
+############
 
+Coding Style refers to the different rules defined in a software project which
+need to be followed when writing source code. These guidelines ensure that all
+the source code is going to look the same across the different files of the
+project.
 
-.. todo::
+The PyAnsys ecosystem is composed by multiple projects. To unify the coding
+style among all projects, this coding style guideline was devised. 
 
-   * Describe flake8 standards (in subpage), include example ``.flake8``
-     with minimum standards.
-   * Include anything we've written from other documentation either in
-     this page or other pages.
+PyAnsys libraries are expected to follow `PEP 8`_ and be consistent in style and
+formatting with the 'big three' data science libraries: `NumPy`_, `SciPy`_, and
+`pandas`_.
 
 .. toctree::
    :hidden:
    :maxdepth: 3
 
-   pep8_best_practices
-   beyond_pep8
-   flake8
+   pep8
+   formatting-tools
+   required-config
+
+
+.. LINKS AND REFERENCES
+
+.. _NumPy: https://numpy.org/
+.. _SciPy: https://www.scipy.org/
+.. _pandas: https://pandas.pydata.org/
+.. _PEP 8: https://www.python.org/dev/peps/pep-0008/