From 27080e3e607f4849c963b419fe6f07e9d08b2076 Mon Sep 17 00:00:00 2001 From: Aravinth Manivannan Date: Sat, 23 Mar 2024 13:48:45 +0530 Subject: [PATCH] fix: consistently use authorization token instead of access token --- content/blog/07-22-monthly-report/index.md | 2 +- content/docs/webmasters/installing-captcha/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/blog/07-22-monthly-report/index.md b/content/blog/07-22-monthly-report/index.md index 7137aa7..b5a462d 100644 --- a/content/blog/07-22-monthly-report/index.md +++ b/content/blog/07-22-monthly-report/index.md @@ -69,7 +69,7 @@ mCaptcha docs over the months have become inconsistent and incorrect. I cleaned up some of the mess and added [a tutorial](/docs/introduction/installing-captcha/) to help folks install mCaptcha on their website. The docs also gets [a -glossary](/docs/terminology/access-token/), which contain explanations +glossary](/docs/webmasters/terminology/), which contain explanations to mCaptcha jargon. ## New releases: glue libraries diff --git a/content/docs/webmasters/installing-captcha/index.md b/content/docs/webmasters/installing-captcha/index.md index 51f0bf5..da5c09f 100644 --- a/content/docs/webmasters/installing-captcha/index.md +++ b/content/docs/webmasters/installing-captcha/index.md @@ -91,7 +91,7 @@ A full example is available ## 5. Configure backend to authenticate CAPTCHA tokens -1. Get [access token](/docs/terminology/access-token) from the user's +1. Get [authorization token](/docs/webmasters/terminology/#authorization-token) from the user's form submission payload. The access token will be associated with a parameter called `mcaptcha__token`.