fix backticks

Signed-off-by: William Woodruff <william@astral.sh>

Author: woodruffw

peps/pep-9999.rst

@@ -323,7 +323,7 @@ Rejected Ideas
 "Lateral" Discovery
 -------------------
 
-This PEP's discovery mechanism uses the `.well-known` location scheme
+This PEP's discovery mechanism uses the ``.well-known`` location scheme
 defined in :rfc:`8615`. This scheme is widely adopted by machine-to-machine
 protocols, including OpenID Connect itself
 (for `OpenID Connect Discovery <https://openid.net/specs/openid-connect-discovery-1_0.html>`_).
@@ -344,12 +344,12 @@ However, this approach also has downsides:
 * It assumes that arbitrary indices can provide an adjacent path without
   interfering with existing functionality, which isn't necessarily true.
   For example, a given third-party implementation may already use
-  all routes under `/legacy/{*}` for other purposes.
+  all routes under ``/legacy/{*}`` for other purposes.
 * It's less consistent with existing machine-to-machine protocol
-  conventions, which overwhelmingly use the `.well-known` scheme. Developing
+  conventions, which overwhelmingly use the ``.well-known`` scheme. Developing
   a custom location scheme here would require additional informational
   materials for server administrators and operators who are accustomed
-  to the `.well-known` scheme.
+  to the ``.well-known`` scheme.
 
 "Implicit" Discovery
 --------------------
@@ -396,4 +396,3 @@ Copyright
 
 This document is placed in the public domain or under the
 CC0-1.0-Universal license, whichever is more permissive.
-