From d50512e1c62cbf5a5ce5ad0634ef06173cb23db9 Mon Sep 17 00:00:00 2001
From: Tulir Asokan <tulir@maunium.net>
Date: Tue, 23 May 2023 11:54:43 +0300
Subject: [PATCH] Explicitly link to endpoint in AS-side /ping doc

---
 data/api/application-service/ping.yaml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/data/api/application-service/ping.yaml b/data/api/application-service/ping.yaml
index c4f12b4f..18682f11 100644
--- a/data/api/application-service/ping.yaml
+++ b/data/api/application-service/ping.yaml
@@ -34,8 +34,8 @@ paths:
         and the `hs_token` the homeserver has is correct.
 
         Currently this is only called by the homeserver as a direct result of
-        the application service calling the appservice ping endpoint in the
-        client API.
+        the application service calling
+        [`POST /_matrix/client/v1/appservice/{appserviceId}/ping`](#post_matrixclientv1appserviceappserviceidping).
       operationId: ping
       security:
         - homeserverAccessToken: []
@@ -53,7 +53,7 @@ paths:
                 type: string
                 description: |-
                   A transaction ID for the ping, copied directly from the
-                  client API appservice ping call.
+                  `POST /_matrix/client/v1/appservice/{appserviceId}/ping` call.
       responses:
         200:
           description: The provided `hs_token` is valid and the ping request was successful.