second rev on dev docs

Author: jhamman

docs/developers/contributing.rst

@@ -33,7 +33,7 @@ a bug report:
     # etc.
     ```
 
-2. An explanation of why the current behavior is wrong/not desired, and what you
+2. An explanation of why the current behaviour is wrong/not desired, and what you
    expect instead.
 
 3. Information about the version of Zarr, along with versions of dependencies and the
@@ -82,13 +82,13 @@ Then clone your fork to your local machine::
 Creating a development environment
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To work with the Zarr source code, it is recommended to use `hatch
-<https://hatch.pypa.io/latest/index.html>`_ to create a virtual environment and
-install all Zarr dependencies using the same versions as are used by
-the core developers and continuous integration services. Assuming you have a Python
-3 interpreter already installed, and you have cloned the Zarr source code and your
-current working directory is the root of the repository, you can do something like
-the following::
+To work with the Zarr source code, it is recommended to use
+`hatch <https://hatch.pypa.io/latest/index.html>`_ to create and manage development
+environments. Hatch will automatically install all Zarr dependencies using the same
+versions as are used by the core developers and continuous integration services.
+Assuming you have a Python 3 interpreter already installed, and you have cloned the
+Zarr source code and your current working directory is the root of the repository,
+you can do something like the following::
 
     $ pip install hatch
     $ hatch env show  # list all available environments
@@ -144,6 +144,10 @@ All tests are automatically run via GitHub Actions for every pull
 request and must pass before code can be accepted. Test coverage is
 also collected automatically via the Codecov service.
 
+.. note::
+    Previous versions of Zarr-Python made extensive use of doctests. These tests were
+    not maintained during the 3.0 refactor but may be brought back in the future.
+
 Code standards - using pre-commit
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -179,8 +183,7 @@ Test coverage
     is welcome to bring test coverage back to 100%. See :issue:`2613` for more details.
 
 Zarr strives to maintain 100% test coverage under the latest Python stable release
-(currently Python 3.12). Both unit tests and docstring doctests are included when computing
-coverage. Running::
+Both unit tests and docstring doctests are included when computing coverage. Running::
 
     $ hatch env run --env test.py3.12-2.1-optional run-coverage