From f632f4a20f524b6ca697164ab9acbd832d07d68f Mon Sep 17 00:00:00 2001
From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Date: Thu, 4 Jun 2020 17:36:40 +0100
Subject: [PATCH] Clarify link to OpenID Connect specification (#2605)

OpenID Connect and OpenID are different things. This seems to be talking about
the former.
---
 api/client-server/openid.yaml                             | 2 +-
 changelogs/client_server/newsfragments/2605.clarification | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 changelogs/client_server/newsfragments/2605.clarification

diff --git a/api/client-server/openid.yaml b/api/client-server/openid.yaml
index 01fdf68f..98a2449e 100644
--- a/api/client-server/openid.yaml
+++ b/api/client-server/openid.yaml
@@ -62,7 +62,7 @@ paths:
         200:
           description: |-
             OpenID token information. This response is nearly compatible with the
-            response documented in the `OpenID 1.0 Specification <http://openid.net/specs/openid-connect-core-1_0.html#TokenResponse>`_
+            response documented in the `OpenID Connect 1.0 Specification <http://openid.net/specs/openid-connect-core-1_0.html#TokenResponse>`_
             with the only difference being the lack of an ``id_token``. Instead,
             the Matrix homeserver's name is provided.
           examples:
diff --git a/changelogs/client_server/newsfragments/2605.clarification b/changelogs/client_server/newsfragments/2605.clarification
new file mode 100644
index 00000000..e3d1fe98
--- /dev/null
+++ b/changelogs/client_server/newsfragments/2605.clarification
@@ -0,0 +1 @@
+Clarify link to OpenID Connect specification.