From 1d6b565de452d24e1db0ca21ba69289809fdc32a Mon Sep 17 00:00:00 2001 From: John Olheiser Date: Fri, 23 Oct 2020 10:59:45 -0500 Subject: Refactor docs (#13275) * First pass Signed-off-by: jolheiser * More changes Signed-off-by: jolheiser * Redirects Signed-off-by: jolheiser --- docs/content/doc/help/faq.en-us.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/content/doc/help') diff --git a/docs/content/doc/help/faq.en-us.md b/docs/content/doc/help/faq.en-us.md index 7a7044f61c..34e6bca3ac 100644 --- a/docs/content/doc/help/faq.en-us.md +++ b/docs/content/doc/help/faq.en-us.md @@ -129,7 +129,7 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo ## What is Swagger? [Swagger](https://swagger.io/) is what Gitea uses for its API. All Gitea instances have the built-in API, though it can be disabled by setting `ENABLE_SWAGGER` to `false` in the `api` section of your `app.ini` -For more information, refer to Gitea's [API docs]({{< relref "doc/advanced/api-usage.en-us.md" >}}) +For more information, refer to Gitea's [API docs]({{< relref "doc/developers/api-usage.en-us.md" >}}) [Swagger Example](https://try.gitea.io/api/swagger) @@ -140,7 +140,7 @@ There are multiple things you can combine to prevent spammers. 1. By only whitelisting certain domains with OpenID (see below) 2. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY` -3. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI]({{< relref "doc/usage/command-line.en-us.md" >}}), [API]({{< relref "doc/advanced/api-usage.en-us.md" >}}), or Gitea's Admin UI +3. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI]({{< relref "doc/usage/command-line.en-us.md" >}}), [API]({{< relref "doc/developers/api-usage.en-us.md" >}}), or Gitea's Admin UI ### Only allow certain email domains You can configure `EMAIL_DOMAIN_WHITELIST` in your app.ini under `[service]` -- cgit v1.2.3