From 6fb9c407ac8e413aaafcd31135da932b9eb98ead Mon Sep 17 00:00:00 2001 From: 0xflotus <0xflotus@gmail.com> Date: Wed, 5 May 2021 23:50:50 +0200 Subject: [PATCH] =?UTF-8?q?fix:=20small=20errors=20=F0=9F=98=85?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * fix: small error * fix: small error --- web/docs/learn/auth-deep-dive/gotrue.md | 4 ++-- web/docs/learn/auth-deep-dive/jwts.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/web/docs/learn/auth-deep-dive/gotrue.md b/web/docs/learn/auth-deep-dive/gotrue.md index 0e73b079c69..c73e357807d 100644 --- a/web/docs/learn/auth-deep-dive/gotrue.md +++ b/web/docs/learn/auth-deep-dive/gotrue.md @@ -45,7 +45,7 @@ You'll have to make sure your google app is verified of course in order to reque [Gotrue-js](https://github.com/supabase/gotrue-js) (and also [gotrue-csharp](https://github.com/supabase/gotrue-csharp), [gotrue-py](https://github.com/j0/gotrue-py), [gotrue-kt](https://github.com/supabase/gotrue-kt), and [gotrue-dart](https://github.com/supabase/gotrue-dart)) are all wrappers around the gotrue API endpoints, and make for easier session management inside your client. -But all the functionality of gotrue-js is also available in supabase-js, which uses gotrue-js internall when you do things like: +But all the functionality of gotrue-js is also available in supabase-js, which uses gotrue-js internally when you do things like: ```jsx const { user, session, error } = await supabase.auth.signIn({ @@ -69,4 +69,4 @@ In the next guide we'll be looking at how to setup external OAuth providers: Wat - Watch [Part Three: Policies](/docs/learn/auth-deep-dive/auth-policies) - Watch [Part Five: Google Oauth](/docs/learn/auth-deep-dive/auth-google-oauth) -- Sign up for Supabase: [app.supabase.io](https://app.supabase.io) \ No newline at end of file +- Sign up for Supabase: [app.supabase.io](https://app.supabase.io) diff --git a/web/docs/learn/auth-deep-dive/jwts.md b/web/docs/learn/auth-deep-dive/jwts.md index 783dcc83d10..98510717fa9 100644 --- a/web/docs/learn/auth-deep-dive/jwts.md +++ b/web/docs/learn/auth-deep-dive/jwts.md @@ -30,7 +30,7 @@ Well, the JSON object starts out looking something like this: } ``` -`sub` is the "subject", which is usually the uuid of the user. `name` is self explanitory, and `iat` is the unix timestamp at which the token was created. Many JWTs will also have an `exp` which is the data at which the token is set to expire, and can no longer be used. These are some of the standard fields you may find in a JWT, but you can pretty much store whatever you want in there, for example: +`sub` is the "subject", which is usually the uuid of the user. `name` is self explanatory, and `iat` is the unix timestamp at which the token was created. Many JWTs will also have an `exp` which is the data at which the token is set to expire, and can no longer be used. These are some of the standard fields you may find in a JWT, but you can pretty much store whatever you want in there, for example: ```js { @@ -176,4 +176,4 @@ Now that you understand what JWTs are and where they're used in Supabase, you ca - [Part Three: Policies](/docs/learn/auth-deep-dive/auth-policies) - [Part Four: GoTrue](/docs/learn/auth-deep-dive/auth-gotrue) - [Part Five: Google Oauth](/docs/learn/auth-deep-dive/auth-google-oauth) -- Sign up for Supabase: [app.supabase.io](https://app.supabase.io) \ No newline at end of file +- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)