..

Author: ev-br

README.md

@@ -318,7 +318,7 @@ $ spin smoke-tutorials   # ReST user guide tutorials
 
 Here is a (non-exhaustive) list of possible gotchas:
 
-- _In-place development builds_.
+#### _In-place development builds_.
 
 Some tools (looking at you `meson-python`) simulate in-place builds with a
 `build-install` directory. If this directory is located under the project root,
@@ -342,7 +342,7 @@ If push really comes to shove, you may try using the magic env variable:
 however the need usually indicates an issue with the package itself.
 (see [gh-107](https://github.com/scipy/scipy_doctest/pull/107) for an example).
 
-- _Optional dependencies are not that optional_
+#### _Optional dependencies are not that optional_
 
 If your package contains optional dependencies, doctests do not know about them
 being optional. So you either guard the imports in doctests themselves (yikes!), or
@@ -361,7 +361,7 @@ Note that installed packages are no different:
 $ pytest --pyargs scipy --doctest-modules --ignore=/path/to/installed/scipy/_lib
 ```
 
-- _Doctest collection strategies_
+#### _Doctest collection strategies_
 
 The default collection strategy follows `doctest` module and `pytest`. This leads
 to duplicates if your package has the split between public and \_private modules,
@@ -383,9 +383,7 @@ leads to
   * `scipy.linalg._basic.det`, collected from `scipy/linalg/_basic.py`, is private.
   * `scipy.linalg.det`, collected from `scipy/linalg/__init__.py`, is public.
 
-<!-- -->
-
-- _`pytest`'s assertion rewriting_
+#### _`pytest`'s assertion rewriting_
 
 In some rare cases you may need to either explicitly register the `scipy_doctest`
 package with the `pytest` assertion rewriting machinery, or ask it to avoid rewriting
@@ -397,7 +395,7 @@ In general, rewriting assertions is not very useful for doctests, as the
 output on error is fixed by the doctest machinery anyway. Therefore, we believe
 adding `--assert=plain` is reasonable.
 
-- _Mixing strings and numbers_
+#### _Mixing strings and numbers_
 
 Generally, we aim to handle mixtures of strings and numeric data. Deeply nested data
 structures however may cause the checker to fall back to the vanilla `doctest` literal