diff --git a/doc/en/explanation/goodpractices.rst b/doc/en/explanation/goodpractices.rst
index ac6ed4298..5277c2ac5 100644
--- a/doc/en/explanation/goodpractices.rst
+++ b/doc/en/explanation/goodpractices.rst
@@ -114,15 +114,15 @@ which are better explained in this excellent `blog post`_ by Ionel Cristian Măr
 
 .. note::
 
-    If you do not use an editable install and use the ``src`` layout as above you need to extend the Python's 
-    search path for module files to execute the tests against the local copy directly. You can do it in an 
+    If you do not use an editable install and use the ``src`` layout as above you need to extend the Python's
+    search path for module files to execute the tests against the local copy directly. You can do it in an
     ad-hoc manner by setting the ``PYTHONPATH`` environment variable:
 
     .. code-block:: bash
 
        PYTHONPATH=src pytest
 
-    or in a permanent manner by using the :confval:`pythonpath` configuration variable and adding the 
+    or in a permanent manner by using the :confval:`pythonpath` configuration variable and adding the
     following to your ``pyproject.toml``:
 
     .. code-block:: toml
@@ -132,8 +132,8 @@ which are better explained in this excellent `blog post`_ by Ionel Cristian Măr
 
 .. note::
 
-    If you do not use an editable install and not use the ``src`` layout (``mypkg`` directly in the root 
-    directory) you can rely on the fact that Python by default puts the current directory in ``sys.path`` to 
+    If you do not use an editable install and not use the ``src`` layout (``mypkg`` directly in the root
+    directory) you can rely on the fact that Python by default puts the current directory in ``sys.path`` to
     import your package and run ``python -m pytest`` to execute the tests against the local copy directly.
 
     See :ref:`pytest vs python -m pytest` for more information about the difference between calling ``pytest`` and