fix: consistently use authorization token instead of access token
This commit is contained in:
parent
073d5ed239
commit
27080e3e60
2 changed files with 2 additions and 2 deletions
|
@ -69,7 +69,7 @@ mCaptcha docs over the months have become inconsistent and incorrect. I
|
||||||
cleaned up some of the mess and added [a
|
cleaned up some of the mess and added [a
|
||||||
tutorial](/docs/introduction/installing-captcha/) to help folks install
|
tutorial](/docs/introduction/installing-captcha/) to help folks install
|
||||||
mCaptcha on their website. The docs also gets [a
|
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.
|
to mCaptcha jargon.
|
||||||
|
|
||||||
## New releases: glue libraries
|
## New releases: glue libraries
|
||||||
|
|
|
@ -91,7 +91,7 @@ A full example is available
|
||||||
|
|
||||||
## 5. Configure backend to authenticate CAPTCHA tokens
|
## 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
|
form submission payload. The access token will be associated with a
|
||||||
parameter called `mcaptcha__token`.
|
parameter called `mcaptcha__token`.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue