Apply suggestions from code review

Author: alejoe91

doc/development/development.rst

@@ -406,7 +406,7 @@ How to make a release
 Checklist
 ^^^^^^^^^
 * pyproject.toml: check that the version is ahead of current release. Also, comment out the @ (git dependencies)
-* In the top level ``__init__`` (located at ``src/spikeinterface/__init__.py``) uncomment ``DEV_MODE`` (this is used for the docker installations)
+* In the top level ``__init__`` (located at ``src/spikeinterface/__init__.py``) set ``DEV_MODE`` to ``False`` (this is used for the docker installations)
 * Create a new release note for the appropriate version on doc/releases/new_version_tag.
 
 There can be large releases like:
@@ -444,5 +444,5 @@ As a specific example:
 * Push the tag to the remote repository which will trigger the release action (.github/workflows/publish-to-pypi.yml)
 * Do an after-release `PR <https://github.com/SpikeInterface/spikeinterface/pull/3828/files>`_:
     - Uncomment the git installs in pyproject
-    - Modify `DEV_MODE` in the top level ``__init__`` (located at ``src/spikeinterface/__init__.py``)
+    - Set ``DEV_MODE`` to ``True`` in the top level ``__init__`` (located at ``src/spikeinterface/__init__.py``)
     - Update `pyproject.toml` version one patch ahead or one minor if it is larger one.