ADRN/mcaptcha-website
1
0
Fork 0
forked from mCaptcha/website
Code Pull requests Activity

fix: consistently use authorization token instead of access token

Browse source
This commit is contained in:
Aravinth Manivannan 2024-03-23 13:48:45 +05:30
parent 073d5ed239
commit 27080e3e60
Signed by untrusted user: realaravinth
GPG key ID: F8F50389936984FF
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/blog/07-22-monthly-report/index.md
View file

@ -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

2
content/docs/webmasters/installing-captcha/index.md
View file

@ -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`.