Linkify endpoints properly

specification/client_server_api.rst

@@ -1246,6 +1246,9 @@ have to wait in milliseconds before they can try again.
 .. |/events| replace:: ``/events``
 .. _/events: #get-matrix-client-%CLIENT_MAJOR_VERSION%-events
 
+.. |/createRoom| replace:: ``/createRoom``
+.. _/createRoom: #post-matrix-client-%CLIENT_MAJOR_VERSION%-createroom
+
 .. |/rooms/<room_id>/initialSync| replace:: ``/rooms/<room_id>/initialSync``
 .. _/rooms/<room_id>/initialSync: #get-matrix-client-%CLIENT_MAJOR_VERSION%-rooms-roomid-initialsync
 

specification/modules/dm.rst

@@ -42,14 +42,14 @@ may for example, prompt the user, ignore the flag altogether. To do this, it
 stores this event in account data using the ``account_data`` API: see `Client
 Config`_.
 
-The inviter's client should set the ``is_direct`` flag to ``createRoom``
+The inviter's client should set the ``is_direct`` flag to .. |/createRoom|_
-(`Creation`_) whenever the flow the user has followed is one where their
+whenever the flow the user has followed is one where their
 intention is to speak directly with another person, as opposed to bringing that
 person in to a shared room. For example, clicking on, 'Start Chat' beside a
 person's profile picture would imply the ``is_direct`` flag should be set.
 
 Server behaviour
 ----------------
-When the ``is_direct`` flag is given to ``createRoom`` (`Creation`_), the home
+When the ``is_direct`` flag is given to .. |/createRoom|_, the home
 server must set the ``is_direct`` flag in the invite member event for any users
 invited in the ``createRoom`` call.