diff --git a/docs/requirements.txt b/docs/requirements.txt
index 7af20d13..54683842 100644
--- a/docs/requirements.txt
+++ b/docs/requirements.txt
@@ -10,7 +10,7 @@
 
 autodoc-traits
 jupyterhub-sphinx-theme
-myst-parser
+myst-parser>=0.19
 pre-commit
 pytablewriter>=0.56
 ruamel.yaml
diff --git a/docs/source/explanation/singleuser.md b/docs/source/explanation/singleuser.md
index a18dfed3..3c7337d4 100644
--- a/docs/source/explanation/singleuser.md
+++ b/docs/source/explanation/singleuser.md
@@ -44,7 +44,7 @@ Most of this is implemented in the {class}`~.HubOAuth` class. `jupyterhub.single
 By default, `jupyter-server` uses its own cookie to authenticate.
 If that cookie is not present, the server redirects you a login page and asks you to enter a password or token.
 
-Jupyter Server 2.0 introduces two new _APIs_ for customizing authentication: The [IdentityProvider](jupyter-server:jupyter_server.auth.IdentityProvider) and the [Authorizer](jupyter-server:jupyter_server.auth.Authorizer).
+Jupyter Server 2.0 introduces two new _APIs_ for customizing authentication: the [IdentityProvider](inv:jupyter-server#jupyter_server.auth.IdentityProvider) and the [Authorizer](inv:jupyter-server#jupyter_server.auth.Authorizer).
 More information can be found in the [Jupyter Server documentation](https://jupyter-server.readthedocs.io).
 
 JupyterHub implements these APIs in `jupyterhub.singleuser.extension`.