[Documentation] Remove duplicated checks groups descriptions form clang-tidy/index.rst

[Eugene.Zelenko]

Summary

Checks are described at beginning and directory names follow name prefixes, so another list is redundant.

[alexfh]

docs/clang-tidy/index.rst

344

These links point to the code, so they are still somewhat useful. We could leave a link to the clang-tidy directory (http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/) and explain that most subdirectories there correspond to check modules and the descriptions of modules can be found <link to the relevant section of this documentation>.

[Eugene.Zelenko]

Rephrase text and add link to Clang-tidy directory. Will be good idea is native English speaker will look on this change.

[alexfh]

docs/clang-tidy/index.rst

343

are located in subdirectories of .... and contain checks targeting a certain aspect of code quality (performance, readability, etc.), certain coding style or standard (Google, LLVM, CERT, etc.) or a widely used API (e.g. MPI).

344

Could you linkify above?

345

The "If the check verifies..." sentence is now somewhat tautological, just remove it.

[Eugene.Zelenko]

Address Alexander's comments.

[alexfh]

LG. Thanks!

docs/clang-tidy/index.rst

 available checks or with any other value of ``-checks=`` to see which checks are
 enabled by this value.
 
+:: _checks-groups-table:
+
 There are currently the following groups of checks:
 
 ====================== =========================================================

 .. _LLVM Coding Standards: http://llvm.org/docs/CodingStandards.html
 .. _LLVM Phabricator: http://llvm.org/docs/Phabricator.html
 
+Next, you need to decide which module the check belongs to. Modules
+are located in subdirectories of
+``clang-tidy/ <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/>``_
+and contain checks targeting a certain aspect of code quality (performance,
+readability, etc.), certain coding style or standard (Google, LLVM, CERT, etc.)
+or a widely used API (e.g. MPI). Their names are same as user-facing check
+groups names described :ref:`above <checks-groups-table>`.
 
-Next, you need to decide which module the check belongs to. If the check
-verifies conformance of the code to a certain coding style, it probably deserves
-a separate module and a directory in ``clang-tidy/``. There are already modules
-implementing checks related to:
-
-* `C++ Core Guidelines
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cppcoreguidelines/>`_
-* `CERT Secure Coding Standards
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cert/>`_
-* `Google Style Guide
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/google/>`_
-* `LLVM Style
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/llvm/>`_
-* `modernizing C/C++ code
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/modernize/>`_
-* potential `performance problems
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/performance/>`_
-* various `readability issues
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/readability/>`_
-* and `miscellaneous checks
-  <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/misc/>`_
-  that we couldn't find a better category for.
-
 After choosing the module, you need to create a class for your check:
 
 .. code-block:: c++