DO NOT MERGE: drop some links to see if they're the bad ones.

Author: TallJimbo

stack/documenting-code-with-type-annotations.rst

@@ -5,7 +5,7 @@ Documenting code with type hints
 ################################
 
 Many DM packages (especially the middleware suite) use type hints for static analysis, which often duplicates the type information included in docstrings.
-Documentation built with `Documenteer 2.x`_ can often leave this information out, because the `sphinx-autodoc-typehints`_ extension (included automatically) will parse the annotations and include type information in the docs automatically.
+Documentation built with ``Documenteer 2.x`` can often leave this information out, because the ``sphinx-autodoc-typehints`` extension (included automatically) will parse the annotations and include type information in the docs automatically.
 
 .. note::
    `pipelines.lsst.io`_ is currently still built with Documenteer 1.x, but is expected to transition soon.
@@ -110,6 +110,4 @@ Annotations on properties and attributes are not applied to documentation automa
    Important instance attributes that cannot have a class-level default value should be made into properties so they can be documented.
 
 
-.. _`Documenteer 2.x`: https://documenteer.lsst.io
-.. _`sphinx-autodoc-typehints`: https://pypi.org/project/sphinx-autodoc-typehints/
 .. _`pipelines.lsst.io`: https://pipelines.lsst.io