diff --git a/doc/integration/auth0.md b/doc/integration/auth0.md index 4d0c4072fcd9a21bfc189c58f41e3a6649010d77..212b4854dd737e8e94c4ce6ba3cc179e5002d9eb 100644 --- a/doc/integration/auth0.md +++ b/doc/integration/auth0.md @@ -89,4 +89,4 @@ user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/azure.md b/doc/integration/azure.md index a4b5545331fc6662902b6e9806ce059cb1babba9..5e3e9f5ab772e8a17e54903568c5403dbeceb319 100644 --- a/doc/integration/azure.md +++ b/doc/integration/azure.md @@ -84,4 +84,4 @@ To enable the Microsoft Azure OAuth2 OmniAuth provider you must register your ap On the sign in page there should now be a Microsoft icon below the regular sign in form. Click the icon to begin the authentication process. Microsoft will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/cas.md b/doc/integration/cas.md index 05cd501e1ab8483fd14b4380d746dab277cde0f7..f757edf0bc2a41f63a0a5e5b5fa3a7466fc29b76 100644 --- a/doc/integration/cas.md +++ b/doc/integration/cas.md @@ -64,5 +64,5 @@ To enable the CAS OmniAuth provider you must register your application with your On the sign in page there should now be a CAS tab in the sign in form. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/crowd.md b/doc/integration/crowd.md index 5f0ee89d6cb0ccb048f2d15cd725410823ecfe84..f8370cd349efe9df0f6921ade171fb273f52d1af 100644 --- a/doc/integration/crowd.md +++ b/doc/integration/crowd.md @@ -59,5 +59,5 @@ To enable the Crowd OmniAuth provider you must register your application with Cr On the sign in page there should now be a Crowd tab in the sign in form. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/facebook.md b/doc/integration/facebook.md index d1eabb76392e1d95dc4d206d0ad8adfc7378da5e..a67de23b17b4eae93652bf7c2a9d929e554fc83d 100644 --- a/doc/integration/facebook.md +++ b/doc/integration/facebook.md @@ -98,4 +98,4 @@ something else descriptive. On the sign in page there should now be a Facebook icon below the regular sign in form. Click the icon to begin the authentication process. Facebook will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/github.md b/doc/integration/github.md index cc95ad3f924421e7e47128a2d348a407ba591433..cea85f073ccc5889a3a02a04bad96b6c8fa88845 100644 --- a/doc/integration/github.md +++ b/doc/integration/github.md @@ -111,4 +111,4 @@ Click the icon to begin the authentication process. GitHub will ask the user to If everything goes well the user will be returned to GitLab and will be signed in. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/gitlab.md b/doc/integration/gitlab.md index c79b08c99c8e9c3b7e0c7693c6dc142c26250a3d..eec40a9b8f12ef7b29455222782ca15b0f164f31 100644 --- a/doc/integration/gitlab.md +++ b/doc/integration/gitlab.md @@ -85,4 +85,4 @@ Click the icon to begin the authentication process. GitLab.com will ask the user If everything goes well the user will be returned to your GitLab instance and will be signed in. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/google.md b/doc/integration/google.md index 7eba7000d9466b3e34e0f9ad95505b279bd9f97e..1e7ad90c5a8e1db9a0802b0d841ae9039a576474 100644 --- a/doc/integration/google.md +++ b/doc/integration/google.md @@ -90,4 +90,4 @@ At this point, when users first try to authenticate to your GitLab installation 1. Add any additional information as you wish - homepage, logo, privacy policy, etc. None of this is required, but it may help your users. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/saml.md b/doc/integration/saml.md index cd53ee635ccc60678173830caf01b3588378deec..7a809eddac0804227c5c6be904ae274ab3ecde5f 100644 --- a/doc/integration/saml.md +++ b/doc/integration/saml.md @@ -317,4 +317,4 @@ Make sure that one of the above described scenarios is valid, or the requests wi fail with one of the mentioned errors. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/shibboleth.md b/doc/integration/shibboleth.md index 9ff46a71fcabd1bc4cd30e6f26a0b87b5b4b0ce3..e0fc1bb801fee9923b955813c5de6d6ee8616392 100644 --- a/doc/integration/shibboleth.md +++ b/doc/integration/shibboleth.md @@ -124,4 +124,4 @@ you will not get a shibboleth session! ``` [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source diff --git a/doc/integration/twitter.md b/doc/integration/twitter.md index 2c7c34cc8e77cc077868158a06e0969ac8f5e4d2..d0976b6201eab29395136645235e051a5db5b513 100644 --- a/doc/integration/twitter.md +++ b/doc/integration/twitter.md @@ -80,4 +80,4 @@ To enable the Twitter OmniAuth provider you must register your application with On the sign in page there should now be a Twitter icon below the regular sign in form. Click the icon to begin the authentication process. Twitter will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in. [reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure -[restart]: ../administration/restart_gitlab.md#installations-from-source +[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source