replace implicit code tag with colon .replace("::\n\n.. code-block", ":\n\n.. code-block")

1 files changed, 7 insertions, 7 deletions

diff --git a/doc/en/goodpractices.rst b/doc/en/goodpractices.rst
index 065308c14..0aa0dc97c 100644
--- a/doc/en/goodpractices.rst
+++ b/doc/en/goodpractices.rst
@@ -12,7 +12,7 @@ pip_ for installing your application and any dependencies,
 as well as the ``pytest`` package itself.
 This ensures your code and dependencies are isolated from your system Python installation.
 
-Next, place a ``setup.py`` file in the root of your package with the following minimum content::
+Next, place a ``setup.py`` file in the root of your package with the following minimum content:
 
 .. code-block:: python
 
@@ -20,7 +20,7 @@ Next, place a ``setup.py`` file in the root of your package with the following m
 
     setup(name="PACKAGENAME", packages=find_packages())
 
-Where ``PACKAGENAME`` is the name of your package. You can then install your package in "editable" mode by running from the same directory::
+Where ``PACKAGENAME`` is the name of your package. You can then install your package in "editable" mode by running from the same directory:
 
 .. code-block:: bash
 
@@ -64,7 +64,7 @@ Tests outside application code
 
 Putting tests into an extra directory outside your actual application code
 might be useful if you have many functional tests or for other reasons want
-to keep tests separate from actual application code (often a good idea)::
+to keep tests separate from actual application code (often a good idea):
 
 .. code-block:: text
 
@@ -98,7 +98,7 @@ be imported as ``test_app`` and ``test_view`` top-level modules by adding ``test
 ``sys.path``.
 
 If you need to have test modules with the same name, you might add ``__init__.py`` files to your
-``tests`` folder and subfolders, changing them to packages::
+``tests`` folder and subfolders, changing them to packages:
 
 .. code-block:: text
 
@@ -122,7 +122,7 @@ This is problematic if you are using a tool like `tox`_ to test your package in
 because you want to test the *installed* version of your package, not the local code from the repository.
 
 In this situation, it is **strongly** suggested to use a ``src`` layout where application root package resides in a
-sub-directory of your root::
+sub-directory of your root:
 
 .. code-block:: text
 
@@ -150,7 +150,7 @@ Tests as part of application code
 
 Inlining test directories into your application package
 is useful if you have direct relation between tests and application modules and
-want to distribute them along with your application::
+want to distribute them along with your application:
 
 .. code-block:: text
 
@@ -165,7 +165,7 @@ want to distribute them along with your application::
             test_view.py
             ...
 
-In this scheme, it is easy to run your tests using the ``--pyargs`` option::
+In this scheme, it is easy to run your tests using the ``--pyargs`` option:
 
 .. code-block:: bash