Merge pull request #1448 from 0xflotus/patch-4

fix: small errors

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 Four: GoTrue](/docs/learn/auth-deep-dive/auth-gotrue) -->
 - Watch [Part Five: Google Oauth](/docs/learn/auth-deep-dive/auth-google-oauth)
-- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)
+- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)

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)
+- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)

web/spec/postgres.yml

@@ -115,8 +115,8 @@ pages:
         sql: |
           ```sql
           alter table table_name
-            add constraint constraint_name_1 foreign key (colum_1) references foreign_table(id),
-            add constraint constraint_name_2 foreign key (colum_2) references foreign_table(id);
+            add constraint constraint_name_1 foreign key (column_1) references foreign_table(id),
+            add constraint constraint_name_2 foreign key (column_2) references foreign_table(id);
           ```
       - name: Delete a table
         sql: |
@@ -224,7 +224,7 @@ pages:
           
   Database Users:
     description: |
-      Users and Roles are almost interchangable.
+      Users and Roles are almost interchangeable.
 
     examples:
       - name: Create New User

web/spec/supabase.json

@@ -5074,7 +5074,7 @@
 										"isExported": true
 									},
 									"comment": {
-										"shortText": "Subscribe to realtime changes in your databse."
+										"shortText": "Subscribe to realtime changes in your database."
 									},
 									"parameters": [
 										{
@@ -13172,4 +13172,4 @@
 			]
 		}
 	]
-}
+}