[4.2.x] Refs #34140 -- Applied rst code-block to non-Python examples.

Thanks to J.V. Zammit, Paolo Melchiorre, and Mariusz Felisiak for
reviews.

Backport of 534ac4829764f317cf2fbc4a18354fcc998c1425 from main.

1 files changed, 9 insertions, 3 deletions

diff --git a/docs/topics/testing/advanced.txt b/docs/topics/testing/advanced.txt
index fafc4e0bbc..101058b7dc 100644
--- a/docs/topics/testing/advanced.txt
+++ b/docs/topics/testing/advanced.txt
@@ -414,7 +414,9 @@ you may want to use the Django test runner to run your own test suite
 and thus benefit from the Django testing infrastructure.
 
 A common practice is a *tests* directory next to the application code, with the
-following structure::
+following structure:
+
+.. code-block:: text
 
     runtests.py
     polls/
@@ -869,12 +871,16 @@ the coverage of your tests.
 
 Django can be easily integrated with `coverage.py`_, a tool for measuring code
 coverage of Python programs. First, `install coverage.py`_. Next, run the
-following from your project folder containing ``manage.py``::
+following from your project folder containing ``manage.py``:
+
+.. code-block:: shell
 
    coverage run --source='.' manage.py test myapp
 
 This runs your tests and collects coverage data of the executed files in your
-project. You can see a report of this data by typing following command::
+project. You can see a report of this data by typing following command:
+
+.. code-block:: shell
 
    coverage report