Add latest changes from gitlab-org/gitlab@master

1 files changed, 2 insertions, 5 deletions

diff --git a/doc/integration/openid_connect_provider.md b/doc/integration/openid_connect_provider.md
index f75630b93a2..3da17347e91 100644
--- a/doc/integration/openid_connect_provider.md
+++ b/doc/integration/openid_connect_provider.md
@@ -16,13 +16,13 @@ mobile applications.
 On the client side, you can use [OmniAuth::OpenIDConnect](https://github.com/jjbohn/omniauth-openid-connect/) for Rails
 applications, or any of the other available [client implementations](https://openid.net/developers/libraries/#connect).
 
-GitLab's implementation uses the [doorkeeper-openid_connect] gem, refer
+GitLab's implementation uses the [doorkeeper-openid_connect](https://github.com/doorkeeper-gem/doorkeeper-openid_connect "Doorkeeper::OpenidConnect website") gem, refer
 to its README for more details about which parts of the specifications
 are supported.
 
 ## Enabling OpenID Connect for OAuth applications
 
-Refer to the [OAuth guide] for basic information on how to set up OAuth
+Refer to the [OAuth guide](oauth_provider.md) for basic information on how to set up OAuth
 applications in GitLab. To enable OIDC for an application, all you have to do
 is select the `openid` scope in the application settings.
 
@@ -45,6 +45,3 @@ Currently the following user information is shared with clients:
 | `groups`         | `array`   | Names of the groups the user is a member of
 
 Only the `sub` and `sub_legacy` claims are included in the ID token, all other claims are available from the `/oauth/userinfo` endpoint used by OIDC clients.
-
-[doorkeeper-openid_connect]: https://github.com/doorkeeper-gem/doorkeeper-openid_connect "Doorkeeper::OpenidConnect website"
-[OAuth guide]: oauth_provider.md "GitLab as OAuth2 authentication service provider"