change lexer names to fix ci

Author: oraNod

docs/docsite/rst/dev_guide/developing_collections_distributing.rst

@@ -220,7 +220,7 @@ For example, to exclude the :file:`sensitive` folder within the ``playbooks`` fo
 
 By default, the ``MANIFEST.in`` style directives would exclude all files by default, but there are default directives in place. Those default directives are described below. To see the directives in use during build, pass ``-vvv`` with the ``ansible-galaxy collection build`` command.
 
-.. code-block:: manifest
+.. code-block:: text
 
    include meta/*.yml
    include *.txt *.md *.rst COPYING LICENSE

docs/docsite/rst/os_guide/intro_bsd.rst

@@ -157,36 +157,36 @@ The playbook below
 
 displays the details
 
-.. code-block:: ansible-output
+.. code-block:: text
 
-  shell> ANSIBLE_STDOUT_CALLBACK=yaml ansible-playbook -i hosts playbook.yml
+   shell> ANSIBLE_STDOUT_CALLBACK=yaml ansible-playbook -i hosts playbook.yml
 
-  PLAY [test_11] *******************************************************************************
+   PLAY [test_11] *******************************************************************************
 
-  TASK [command] *******************************************************************************
-  [WARNING]: Platform freebsd on host test_11 is using the discovered Python interpreter at
-  /usr/local/bin/python, but future installation of another Python interpreter could change the
-  meaning of that path. See https://docs.ansible.com/ansible-
-  core/2.18/reference_appendices/interpreter_discovery.html for more information.
-  changed: [test_11]
+   TASK [command] *******************************************************************************
+   [WARNING]: Platform freebsd on host test_11 is using the discovered Python interpreter at
+   /usr/local/bin/python, but future installation of another Python interpreter could change the
+   meaning of that path. See https://docs.ansible.com/ansible-
+   core/2.18/reference_appendices/interpreter_discovery.html for more information.
+   changed: [test_11]
 
-  TASK [debug] *********************************************************************************
-  ok: [test_11] =>
-    result.stdout: /usr/local/bin/python
+   TASK [debug] *********************************************************************************
+   ok: [test_11] =>
+     result.stdout: /usr/local/bin/python
 
-  TASK [debug] *********************************************************************************
-  ok: [test_11] =>
-    msg: |-
-      ansible_interpreter_python_fallback:
-        - /usr/local/bin/python
-        - /usr/local/bin/python3
-        - /usr/local/bin/python3.11
+   TASK [debug] *********************************************************************************
+   ok: [test_11] =>
+     msg: |-
+       ansible_interpreter_python_fallback:
+         - /usr/local/bin/python
+         - /usr/local/bin/python3
+         - /usr/local/bin/python3.11
 
-      discovered_interpreter_python:
-        /usr/local/bin/python
+       discovered_interpreter_python:
+         /usr/local/bin/python
 
-      ansible_playbook_python:
-        /usr/bin/python3
+       ansible_playbook_python:
+         /usr/bin/python3
 
 You can see that the first item from the list ``ansible_interpreter_python_fallback`` was discovered at the FreeBSD remote host. The variable ``ansible_playbook_python`` keeps the path to Python at the Linux control node that ran the playbook.