diff --git a/docs/source/reference/proxy.md b/docs/source/reference/proxy.md
index 6723d88e..240993bd 100644
--- a/docs/source/reference/proxy.md
+++ b/docs/source/reference/proxy.md
@@ -7,9 +7,12 @@ Hub manages by default as a subprocess (it can be run externally, as well, and
 typically is in production deployments).
 
 The upside to CHP, and why we use it by default, is that it's easy to install
-and run (if you have nodejs, you are set!). The downsides are that it's a
-single process and does not support any persistence of the routing table. So
-if the proxy process dies, your whole JupyterHub instance is inaccessible
+and run (if you have nodejs, you are set!). The downsides are that
+
+- it's a single process and
+- does not support any persistence of the routing table.
+
+So if the proxy process dies, your whole JupyterHub instance is inaccessible
 until the Hub notices, restarts the proxy, and restores the routing table. For
 deployments that want to avoid such a single point of failure, or leverage
 existing proxy infrastructure in their chosen deployment (such as Kubernetes