typos

docs/src/content/docs/comparison/supabase.mdx

@@ -9,10 +9,10 @@ architecturally.
 
 For one, both Postgres and SupaBase are heck of a lot more modular. "Rule 34" of
 the database world: if you can think of it, there's a Postgres extension for it.
-And SupaBase doesn't an excellent job at making all that flexibility available
+And SupaBase does an excellent job at making all that flexibility available
 without getting in the way and giving you untethered access while further
 expanding upon it.
-In many ways, TrailBase is trying to evnetually do the same for SQLite:
+In many ways, TrailBase is trying to eventually do the same for SQLite:
 combining PocketBase's simplicity with SupaBase's layering.
 
 One foundational difference is that Postgres itself is a multi-user,

docs/src/content/docs/documentation/APIs/record_apis.mdx

@@ -4,7 +4,7 @@ title: Record APIs
 
 import { Aside } from "@astrojs/starlight/components";
 
-The easiest and most type-safe path to access you `TABLE`s and `VIEW`s is to use
+The easiest and most type-safe path to access your `TABLE`s and `VIEW`s is to use
 TrailBase's restful CRUD _Record APIs_.
 The only requirements are:
 
@@ -111,7 +111,7 @@ update but are hidden on reads. This is meant as a convenient convention to
 allow for internal data fields, e.g hiding the record owner in an otherwise public
 data set or hiding a user's internal credit rating from their profile. A
 similar effect could otherwise be achieved by exposing a table for inserts and
-updates only while poxying reads through a VIEW.
+updates only while proxying reads through a VIEW.
 
 <Aside type="note" title="Unhiding">
   Note that views can also be used to rename columns and thus expose hidden columns
@@ -174,7 +174,7 @@ For example, to query the 10 highest grossing movies with a watch time less
 than 2 hours and an actor called John, one could query:
 
 ```bash
-curl -g '<address>/api/recrods/v1/movies?limit=10&order=grossing&watch_time_min[lt]=120&actors[like]=%John%'
+curl -g '<address>/api/records/v1/movies?limit=10&order=grossing&watch_time_min[lt]=120&actors[like]=%John%'
 ```
 
 ## File Upload

docs/src/content/docs/documentation/auth.mdx

@@ -33,7 +33,7 @@ of the box. It combines:
 Breaking this apart, __asymmetric cryptography__ means that tokens signed with a
 private key by the TrailBase "auth server", which can then be validated by
 others ("resource servers") using only the corresponding public key.
-The __Statelesss JWTs__ contain metadata that identities the user w/o having to
+The __Stateless JWTs__ contain metadata that identities the user w/o having to
 talk to the auth server.
 Combining the two, other back-ends can authenticate, validate & identify, users
 hermetically.

docs/src/content/docs/documentation/extending.mdx

@@ -84,7 +84,7 @@ main application router, see `/examples/custom-binary`.
 
 ### Stored Procedures & Query APIs
 
-Unlike Postgres or MySQL, SQLite does not supported stored procedures out of
+Unlike Postgres or MySQL, SQLite does not support stored procedures out of
 the box.
 TrailBase has adopted sqlean's
 [user-defined functions](https://github.com/nalgeon/sqlean/blob/main/docs/define.md)

docs/src/content/docs/documentation/production.mdx

@@ -75,7 +75,7 @@ You could also consider setting up probers probing other endpoints.
 
 ## Disaster Recovery
 
-The simplest option is to mount anothjer local or remote drive and use
+The simplest option is to mount another local or remote drive and use
 TrailBase's periodic backups.
 However, this may lead to significant data loss in case of a disaster, which
 may be acceptable for first party content but likely not for user-generated

docs/src/content/docs/getting-started/starting-up.mdx

@@ -61,7 +61,7 @@ of pages to explore.
 * The settings page
   (<span class="not-content inline align-middle"><Icon name="tabler:settings" /></span>)
   lets you configure instance-wide settings.
-  Alternatively, uou can also directly edit TrailBase's config file, however, unlike
+  Alternatively, you can also directly edit TrailBase's config file, however, unlike
   the UI you'll need to restart the server to apply the changes.
   TrailBase uses protobuf for its configuration. The schema can be
   found [here](https://github.com/trailbaseio/trailbase/proto/config.proto).