docs: typo fix #3437
Merged
docs: typo fix #3437
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Description for auth.signInWithProvider() has a slight typo
|
This pull request is being automatically deployed with Vercel (learn more). about – ./about🔍 Inspect: https://vercel.com/supabase/about/HPZbGeELDkgn4cXtzv5qyrkTfvNA www – ./www🔍 Inspect: https://vercel.com/supabase/www/iq31M1xSMwg8uF91SQJC6UF59d7m main – ./🔍 Inspect: https://vercel.com/supabase/main/3d3b7imH2cNg7uf8dCXfrkhcfpBa docs – ./web🔍 Inspect: https://vercel.com/supabase/docs/AEKkbnKTaYWUVM1YowviAvwiqhJP |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description for auth.signInWithProvider() has a slight typo
What kind of change does this PR introduce?
Docs update to fix typo
What is the current behavior?
Description says: Signs the user in using thrid party OAuth providers.
What is the new behavior?
Description will say: Signs the user in using third party OAuth providers.
Additional context