Normalize code block type.

Author: felixfontein

docs/docsite/rst/dev_guide/migrating_roles.rst

@@ -71,7 +71,7 @@ You will need to use the Fully Qualified Collection Name (FQCN) to use the roles
 
 So for example, in the above collection, the FQCN to access  ``role1`` would be:
 
-.. code-block:: Python
+.. code-block:: python
 
 	mynamespace.mycollection.role1
 

docs/docsite/rst/dev_guide/style_guide/index.rst

@@ -387,7 +387,7 @@ Ensure all icons, images, diagrams, and non text elements have a meaningful alte
 
 To add alt text in rst:
 
-  .. code-block:: reStructuredText
+  .. code-block:: rst
 
     .. image:: path/networkdiag.png
        :width: 400
@@ -416,7 +416,7 @@ Label tables with a descriptive title.
 
 For RST:
 
-  .. code-block:: reStructuredText
+  .. code-block:: rst
 
     .. table:: File descriptions
 

docs/docsite/rst/reference_appendices/faq.rst

@@ -884,7 +884,7 @@ Until the jinja2 2.10 release, Jinja was only able to return strings, but Ansibl
 
 The following example of a single templating action shows this behavior:
 
-.. code-block:: Jinja
+.. code-block:: jinja
 
   {{ 'ansible' | regex_search('foobar') }}
 
@@ -896,7 +896,7 @@ The native jinja2 functionality actually allows us to return full Python objects
 
   Native jinja2 functionality is not needed when ``regex_search`` is used as an intermediate result that is then compared to the jinja2 ``none`` test.
 
-  .. code-block:: Jinja
+  .. code-block:: jinja
 
      {{ 'ansible' | regex_search('foobar') is none }}