From 229eb4e13dade840cb07a91dbb99d1a7e4cb0ebb Mon Sep 17 00:00:00 2001
From: ffabss <37747351+ffabss@users.noreply.github.com>
Date: Sat, 26 Dec 2020 16:35:31 +0100
Subject: [PATCH] docs/specs: correct typos

---
 web/docs/gotrue/client/api-refreshaccesstoken.mdx | 2 +-
 web/docs/realtime/server/about.md                 | 4 ++--
 web/spec/gotrue.yml                               | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/web/docs/gotrue/client/api-refreshaccesstoken.mdx b/web/docs/gotrue/client/api-refreshaccesstoken.mdx
index 19cc0c094aa..3b68234d442 100644
--- a/web/docs/gotrue/client/api-refreshaccesstoken.mdx
+++ b/web/docs/gotrue/client/api-refreshaccesstoken.mdx
@@ -53,7 +53,7 @@ A valid refresh token that was returned on login.
 
 ## Examples
 
-### Get a new access and refresh token using a valied refresh_token
+### Get a new access and refresh token using a valid refresh_token
 
 
 
diff --git a/web/docs/realtime/server/about.md b/web/docs/realtime/server/about.md
index 33a7c21c89d..be0ca0c1484 100644
--- a/web/docs/realtime/server/about.md
+++ b/web/docs/realtime/server/about.md
@@ -29,7 +29,7 @@ A few reasons:
 #### What are the benefits?
 
 1. The beauty of listening to the replication functionality is that you can make changes to your database from anywhere - your API, directly in the DB, via a console etc - and you will still receive the changes via websockets.
-2. Decoupling. For example, if you want to send a new slack message every time someone makes a new purchase you might build that funcitonality directly into your API. This allows you to decouple your async functionality from your API.
+2. Decoupling. For example, if you want to send a new slack message every time someone makes a new purchase you might build that functionality directly into your API. This allows you to decouple your async functionality from your API.
 3. This is built with Phoenix, an [extremely scalable Elixir framework](https://www.phoenixframework.org/blog/the-road-to-2-million-websocket-connections)
 
 
@@ -57,7 +57,7 @@ There are a some requirements for your database
    1. it must have the `wal_level` set to logical. You can check this by running `SHOW wal_level;`. To set the `wal_level`, you can call `ALTER SYSTEM SET wal_level = logical;`
    2. You must set `max_replication_slots` to at least 1: `ALTER SYSTEM SET max_replication_slots = 5;`
 3. Create a `PUBLICATION` for this server to listen to: `CREATE PUBLICATION supabase_realtime FOR ALL TABLES;`
-4. [OPTIONAL] If you want to recieve the old record (previous values) on UDPATE and DELETE, you can set the `REPLICA IDENTITY` to `FULL` like this: `ALTER TABLE your_table REPLICA IDENTITY FULL;`. This has to be set for each table unfortunately.
+4. [OPTIONAL] If you want to receive the old record (previous values) on UDPATE and DELETE, you can set the `REPLICA IDENTITY` to `FULL` like this: `ALTER TABLE your_table REPLICA IDENTITY FULL;`. This has to be set for each table unfortunately.
 
 ### Server set up
 
diff --git a/web/spec/gotrue.yml b/web/spec/gotrue.yml
index 849574bfe47..74de4f0252b 100644
--- a/web/spec/gotrue.yml
+++ b/web/spec/gotrue.yml
@@ -259,7 +259,7 @@ pages:
   api.refreshAccessToken:
     $ref: '"GoTrueApi".GoTrueApi.refreshAccessToken'
     examples:
-      - name: Get a new access and refresh token using a valied refresh_token
+      - name: Get a new access and refresh token using a valid refresh_token
         js: |
           ```js
           const { error, data } = await api