@bountybot I'd like to pay a bounty for each and every typo found on privy.io and docs.privy.io -- I'll do 10 USDC for the first 50 typos found, no expiration!

Post bounties and services on Farcaster by tagging me. Don’t worry about specific formatting or ordering since I'm using AI to process it (bountycaster.xyz) /bounties. FAQ: bountycaster.xyz/FAQ

We are 39 typos in, with 11 to go and lots of new pages on privy.io dropped, so I suspect we'll get there...

In case any hunters are still on the lookout 🕵️

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

https://docs.privy.io/guide/configuration/

First sentence in the screenshot below should be "..., further matching" instead of "..., to further match".

Let me know if that counts as a typo. :)

Also, "re-prompt" should be "reprompt" for correct spelling here:

Also, "re-prompt" should be "reprompt" for correct spelling here:

https://docs.privy.io/guide/configuration/networks

Same page as above:

supportedChains field, where you should pass a list of chain -object(S)- for your desired supported chains

Same page as above:

supportedChains field, where you should pass a list of chain -object(S)- for your desired supported chains

https://docs.privy.io/guide/configuration/networks

"re-using" should be "reusing" first paragraph:

https://docs.privy.io/guide/configuration/allowed-domains

Source:

"re-using" should be "reusing" first paragraph:

https://docs.privy.io/guide/configuration/allowed-domains

Source: https://www.grammarcheck.me/reuse-or-re-use/

Same page as above:

"Privy's REST API endpoints that you would query from your backend are gated by [-your- or  -the-] Privy App Secret, which should never be exposed on a user's client."

Same page as above:

"Privy's REST API endpoints that you would query from your backend are gated by [-your- or  -the-] Privy App Secret, which should never be exposed on a user's client."

https://docs.privy.io/guide/configuration/allowed-domains

Last green highlighted paragraph:

"If your preview deployments use a staging/development Privy App ID, feel free to leave Allowed Origins empty to support use of [-your- or -that-] App ID in previews, if you don't want to go through the setup above."

Last green highlighted paragraph:

"If your preview deployments use a staging/development Privy App ID, feel free to leave Allowed Origins empty to support use of [-your- or -that-] App ID in previews, if you don't want to go through the setup above."

https://docs.privy.io/guide/configuration/allowed-domains

"Specifically, in your config object, include a loginMethods array with the login methods [that you'd want] for your app."

"Specifically, in your config object, include a loginMethods array with the login methods [that you'd want] for your app."

https://docs.privy.io/guide/frontend/authentication/login

Last paragraph before Note:

 "... using the respective link- call", does link need a "-" at the end?

Last paragraph before Note:

 "... using the respective link- call", does link need a "-" at the end?

https://docs.privy.io/guide/frontend/authentication/login

End of first paragraph:

Instead of "... to redirect them" use "... redirecting them"

End of first paragraph:

Instead of "... to redirect them" use "... redirecting them"

https://docs.privy.io/guide/frontend/authentication/status

Same page as above, inside green Tip box:

"already-authenticated" shouldn't contain "-" and should be separate.

@henri There are 11 errors in this thread (which may or may not be valid or accepted) and I read only about 1/4th of the docs.

I'd love to do a solo bounty for the rest of the docs if you're interested!

Feel like there should be uniform punctuation after each bullet point. 

There are some non-final bullet points that end with blank space and others with a dot.

I think all non-final bullet points should end with ";" and the final one should end with a dot.