Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

chore(docs) Remove instances of let's to resolve mdx lint warnings (#47013)

Miranda Limonczenko0aa7b4965f3d
diff --git a/apps/docs/content/guides/ai/automatic-embeddings.mdx b/apps/docs/content/guides/ai/automatic-embeddings.mdx
index e87691d6153..cb39bb5a8aa 100644
--- a/apps/docs/content/guides/ai/automatic-embeddings.mdx
+++ b/apps/docs/content/guides/ai/automatic-embeddings.mdx
@@ -41,7 +41,7 @@ We'll start by setting up the infrastructure needed to queue and process embeddi
### Step 1: Enable extensions
-First, let's enable the required extensions:
+First, enable the required extensions:
<Tabs
scrollable
@@ -174,7 +174,7 @@ Here we create:
- A generic function to invoke any Edge Function with a given name and request body.
- A generic trigger function to clear a column on update. This function accepts the column name as an argument and sets it to `NULL` in the `NEW` record. We'll explain how to use this function later.
-Every project has a unique API URL that is required to invoke Edge Functions. Let's go ahead and add the project URL secret to Vault depending on your environment.
+Every project has a unique API URL that is required to invoke Edge Functions. Add the project URL secret to Vault depending on your environment.
When working with a local Supabase stack, add the following to your `supabase/seed.sql` file:
@@ -303,7 +303,7 @@ select
);
```
-Let's discuss some common questions about this approach:
+Common questions about this approach:
#### Why not generate all embeddings in a single Edge Function request?
@@ -347,14 +347,12 @@ _supabase/functions/embed/index.ts_:
// Setup type definitions for built-in Supabase Runtime APIs
import 'jsr:@supabase/functions-js/edge-runtime.d.ts'
+// We'll make a direct Postgres connection to update the document
+import postgres from 'https://deno.land/x/[email protected]/mod.js'
// We'll use the OpenAI API to generate embeddings
import OpenAI from 'jsr:@openai/openai'
-
import { z } from 'npm:zod'
-// We'll make a direct Postgres connection to update the document
-import postgres from 'https://deno.land/x/[email protected]/mod.js'
-
// Initialize OpenAI client
const openai = new OpenAI({
// We'll need to manually set the `OPENAI_API_KEY` environment variable
@@ -572,7 +570,7 @@ See [Deploy to Production](/docs/guides/functions/deploy) for more information o
## Usage
-Now that the infrastructure is in place, let's go through an example of how to use this system to automatically generate embeddings for a table of documents. You can use this approach with multiple tables and customize the input for each embedding generation as needed.
+With the infrastructure in place, follow this example to automatically generate embeddings for a table of documents. You can use this approach with multiple tables and customize the input for each embedding generation as needed.
### 1. Create table to store documents with embeddings
@@ -675,7 +673,7 @@ We intentionally use a `before` trigger because it allows us to modify the recor
### 3. Insert and update documents
-Let's insert a new document and update its content to see the embedding generation in action:
+Insert a new document and update its content to see the embedding generation in action:
```sql
-- Insert a new document
@@ -701,7 +699,7 @@ where title = 'Understanding Vector Databases';
You should see the generated embedding for the document.
-Next let's update the content of the document:
+Next, update the content of the document:
```sql
-- Update the content of the document
diff --git a/apps/docs/content/guides/ai/concepts.mdx b/apps/docs/content/guides/ai/concepts.mdx
index 984bae34831..264cbcc9860 100644
--- a/apps/docs/content/guides/ai/concepts.mdx
+++ b/apps/docs/content/guides/ai/concepts.mdx
@@ -16,7 +16,7 @@ Embeddings capture the "relatedness" of text, images, video, or other types of i
- **Classifications:** how do we categorize a body of text?
- **Clustering:** how do we identify trends?
-Let's explore an example of text embeddings. Say we have three phrases:
+The following example uses text embeddings. Given three phrases:
1. "The cat chases the mouse"
2. "The kitten hunts rodents"
diff --git a/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx b/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx
index 8d6bc5eb3ee..486efa6a645 100644
--- a/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx
+++ b/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx
@@ -20,7 +20,7 @@ It allows ChatGPT to dynamically pull relevant information into conversations fr
## Example: Chat with Postgres docs
-Let’s build an example where we can “ask ChatGPT questions” about the Postgres documentation. Although ChatGPT already knows about the Postgres documentation because it is publicly available, this is a basic example which demonstrates how to work with PDF files.
+Build an example where we can “ask ChatGPT questions” about the Postgres documentation. Although ChatGPT already knows about the Postgres documentation because it is publicly available, this is a basic example which demonstrates how to work with PDF files.
This plugin requires several steps:
@@ -139,7 +139,7 @@ To integrate our plugin with ChatGPT, register it in the ChatGPT dashboard. Assu
You can now ask questions about Postgres and receive answers derived from the documentation.
-Let's try it out: ask ChatGPT to find out when to use `check` and when to use `using`. You will be able to see what queries were sent to our plugin and what it responded to.
+Try it out: ask ChatGPT to find out when to use `check` and when to use `using`. You will be able to see what queries were sent to our plugin and what it responded to.
![Ask ChatGPT](/docs/img/ai/chatgpt-plugins/ask-chatgpt.png)
diff --git a/apps/docs/content/guides/ai/examples/nextjs-vector-search.mdx b/apps/docs/content/guides/ai/examples/nextjs-vector-search.mdx
index 6bf0c7d4c87..28a4b0f6684 100644
--- a/apps/docs/content/guides/ai/examples/nextjs-vector-search.mdx
+++ b/apps/docs/content/guides/ai/examples/nextjs-vector-search.mdx
@@ -24,7 +24,7 @@ We assume that you have a Next.js project with a collection of `.mdx` files nest
## Prepare the database
-Let's prepare the database schema. We can use the "OpenAI Vector Search" quickstart in the [SQL Editor](/dashboard/project/_/sql), or you can copy/paste the SQL below and run it yourself.
+Prepare the database schema. We can use the "OpenAI Vector Search" quickstart in the [SQL Editor](/dashboard/project/_/sql), or you can copy/paste the SQL below and run it yourself.
<Tabs
scrollable
@@ -167,7 +167,7 @@ Let's prepare the database schema. We can use the "OpenAI Vector Search" quickst
Anytime the user sends a query, we want to find the content that's relevant to their questions. We can do this using pgvector's similarity search.
- These are quite complex SQL operations, so let's wrap them in database functions that we can call from our frontend using [RPC](/docs/reference/javascript/rpc).
+ For complex SQL operations, wrap them in database functions that you can call from the frontend using [RPC](/docs/reference/javascript/rpc).
</StepHikeCompact.Details>
diff --git a/apps/docs/content/guides/ai/hugging-face.mdx b/apps/docs/content/guides/ai/hugging-face.mdx
index 082a73a1370..0fb7fd4cdfa 100644
--- a/apps/docs/content/guides/ai/hugging-face.mdx
+++ b/apps/docs/content/guides/ai/hugging-face.mdx
@@ -91,7 +91,7 @@ Create a file called `.env.local` to store your Hugging Face access token:
HUGGING_FACE_ACCESS_TOKEN=<your-token-here>
```
-Let's modify the Edge Function to import Hugging Face's inference client and perform a `text-to-image` request:
+Modify the Edge Function to import Hugging Face's inference client and perform a `text-to-image` request:
```ts
import { HfInference } from 'https://esm.sh/@huggingface/[email protected]'
@@ -125,7 +125,7 @@ Deno.serve(async (req) => {
1. The `image` result returned from the API will be a `Blob`. We can pass the `Blob` directly into a `new Response()` which will automatically set the content type and body of the response from the `image`.
-Finally let's serve the Edge Function locally to test it:
+Finally, serve the Edge Function locally to test it:
```shell
supabase functions serve --env-file .env.local --no-verify-jwt
diff --git a/apps/docs/content/guides/ai/hybrid-search.mdx b/apps/docs/content/guides/ai/hybrid-search.mdx
index 44a682da120..70d44c1fa9b 100644
--- a/apps/docs/content/guides/ai/hybrid-search.mdx
+++ b/apps/docs/content/guides/ai/hybrid-search.mdx
@@ -44,7 +44,7 @@ This constant can be any positive number, but is typically small. A constant of
## Hybrid search in Postgres
-Let's implement hybrid search in Postgres using `tsvector` (keyword search) and `pgvector` (semantic search).
+Implement hybrid search in Postgres using `tsvector` (keyword search) and `pgvector` (semantic search).
First we'll create a `documents` table to store the documents that we will search over. This is just an example - adjust this to match the structure of your application.
@@ -131,7 +131,7 @@ limit
$$;
```
-Let's break this down:
+Where:
- **Parameters:** The function accepts quite a few parameters, but the main (required) ones are `query_text`, `query_embedding`, and `match_count`.
- `query_text` is the user's query text (more on this shortly)
diff --git a/apps/docs/content/guides/ai/integrations/roboflow.mdx b/apps/docs/content/guides/ai/integrations/roboflow.mdx
index 2b9d61fc7ac..660fd73acfa 100644
--- a/apps/docs/content/guides/ai/integrations/roboflow.mdx
+++ b/apps/docs/content/guides/ai/integrations/roboflow.mdx
@@ -41,7 +41,7 @@ An inference server will be available at `http://localhost:9001`.
### Step 2: Run inference on an image
-You can run inference on images and videos. Let's run inference on an image.
+You can run inference on images and videos.
Create a new Python file and add the following code:
diff --git a/apps/docs/content/guides/ai/quickstarts/generate-text-embeddings.mdx b/apps/docs/content/guides/ai/quickstarts/generate-text-embeddings.mdx
index f6921cebd91..ed7beaecbf8 100644
--- a/apps/docs/content/guides/ai/quickstarts/generate-text-embeddings.mdx
+++ b/apps/docs/content/guides/ai/quickstarts/generate-text-embeddings.mdx
@@ -9,7 +9,7 @@ This guide will walk you through how to generate high quality text embeddings in
## Build the Edge Function
-Let's build an Edge Function that will accept an input string and generate an embedding for it. Edge Functions are server-side TypeScript HTTP endpoints that run on-demand closest to your users.
+Build an Edge Function that accepts an input string and generates an embedding for it. Edge Functions are server-side TypeScript HTTP endpoints that run on-demand closest to your users.
<StepHikeCompact>
@@ -58,7 +58,7 @@ Let's build an Edge Function that will accept an input string and generate an em
<StepHikeCompact.Details title="Setup Inference Session" fullWidth>
- Let's create a new inference session to be used in the lifetime of this function. Multiple requests can use the same inference session.
+ Create a new inference session to use for the lifetime of this function. Multiple requests can use the same inference session.
Currently, only the `gte-small` (https://huggingface.co/Supabase/gte-small) text embedding model is supported in Supabase's Edge Runtime.
diff --git a/apps/docs/content/guides/ai/rag-with-permissions.mdx b/apps/docs/content/guides/ai/rag-with-permissions.mdx
index 4b2df595dce..da34eb5353d 100644
--- a/apps/docs/content/guides/ai/rag-with-permissions.mdx
+++ b/apps/docs/content/guides/ai/rag-with-permissions.mdx
@@ -33,7 +33,7 @@ create table document_sections (
);
```
-Notice how we record the `owner_id` on each document. Let's create an RLS policy that restricts access to `document_sections` based on whether or not they own the linked document:
+Notice the record of `owner_id` on each document. Create an RLS policy that restricts access to `document_sections` based on whether or not they own the linked document:
```sql
-- Grant the privileges the roles need
@@ -85,7 +85,7 @@ Every app has its own unique requirements and may differ from the above example.
### Documents owned by multiple people
-Instead of a one-to-many relationship between `users` and `documents`, you may require a many-to-many relationship so that multiple people can access the same document. Let's reimplement this using a join table:
+Instead of a one-to-many relationship between `users` and `documents`, you may require a many-to-many relationship so that multiple people can access the same document. Reimplement this using a join table:
```sql
create table document_owners (
@@ -112,7 +112,7 @@ Instead of directly querying the `documents` table, we query the join table.
### User and document data live outside of Supabase
-You may have an existing system that stores users, documents, and their permissions in a separate database. Let's explore the scenario where this data exists in another Postgres database. We'll use a foreign data wrapper (FDW) to connect to the external DB from within your Supabase DB:
+You may have an existing system that stores users, documents, and their permissions in a separate database. Consider the scenario where this data exists in another Postgres database. We'll use a foreign data wrapper (FDW) to connect to the external DB from within your Supabase DB:
<Admonition type="caution">
@@ -126,7 +126,7 @@ For data sources other than Postgres, see [Foreign Data Wrappers](/docs/guides/d
</Admonition>
-Let's assume your external DB contains a `users` and `documents` table like this:
+Assume your external DB contains a `users` and `documents` table like this:
```sql
create table public.users (
@@ -143,7 +143,7 @@ create table public.documents (
);
```
-In your Supabase DB, let's create foreign tables that link to the above tables:
+In your Supabase DB, create foreign tables that link to the above tables:
```sql
create schema external;
diff --git a/apps/docs/content/guides/ai/vecs-python-client.mdx b/apps/docs/content/guides/ai/vecs-python-client.mdx
index 16b08d2105e..ffd6389b56c 100644
--- a/apps/docs/content/guides/ai/vecs-python-client.mdx
+++ b/apps/docs/content/guides/ai/vecs-python-client.mdx
@@ -9,7 +9,7 @@ Supabase provides a Python client called [`vecs`](https://github.com/supabase/ve
## Quick start
-Let's see how Vecs works using a local database. Make sure you have the Supabase CLI [installed](/docs/guides/cli#installation) on your machine.
+To see how Vecs works, use a local database. Make sure you have the Supabase CLI [installed](/docs/guides/cli#installation) on your machine.
### Initialize your project
diff --git a/apps/docs/content/guides/api/creating-routes.mdx b/apps/docs/content/guides/api/creating-routes.mdx
index 701bf327560..5f503a8e3aa 100644
--- a/apps/docs/content/guides/api/creating-routes.mdx
+++ b/apps/docs/content/guides/api/creating-routes.mdx
@@ -8,7 +8,7 @@ API routes are automatically created when you create Postgres Tables, Views, or
## Create a table
-Let's create our first API route by creating a table called `todos` to store tasks.
+Create your first API route by creating a table called `todos` to store tasks.
This creates a corresponding route `todos` which can accept `GET`, `POST`, `PATCH`, & `DELETE` requests.
<Tabs
@@ -78,7 +78,7 @@ Both of these routes require the key to be passed through an `apikey` header.
You can interact with your API directly via HTTP requests, or you can use the client libraries which we provide.
-Let's see how to make a request to the `todos` table which we created in the first step,
+See how to make a request to the `todos` table which we created in the first step,
using the API URL (`SUPABASE_URL`) and Key (`SUPABASE_PUBLISHABLE_KEY`) we provided:
<Tabs
diff --git a/apps/docs/content/guides/auth/auth-captcha.mdx b/apps/docs/content/guides/auth/auth-captcha.mdx
index 6b5e2cc358e..11e6c6da73c 100644
--- a/apps/docs/content/guides/auth/auth-captcha.mdx
+++ b/apps/docs/content/guides/auth/auth-captcha.mdx
@@ -74,7 +74,7 @@ Now import the `HCaptcha` component from the `@hcaptcha/react-hcaptcha` library.
import HCaptcha from '@hcaptcha/react-hcaptcha'
```
-Let's create a empty state to store our `captchaToken`
+Create an empty state to store the `captchaToken`
```jsx
const [captchaToken, setCaptchaToken] = useState()
@@ -86,7 +86,7 @@ Now lets add the `HCaptcha` component to the JSX section of our code
<HCaptcha />
```
-We will pass it the sitekey we copied from the hCaptcha website as a property along with a `onVerify` property which takes a callback function. This callback function will have a token as one of its properties. Let's set the token in the state using `setCaptchaToken`
+Pass it the sitekey we copied from the hCaptcha website as a property along with a `onVerify` property which takes a callback function. This callback function will have a token as one of its properties. Set the token in the state using `setCaptchaToken`
```jsx
<HCaptcha
@@ -115,7 +115,7 @@ Create a ref to use on our `HCaptcha` component.
const captcha = useRef()
```
-Let's add a ref attribute on the `HCaptcha` component and assign the `captcha` constant to it.
+Add a `ref` attribute on the `HCaptcha` component and assign the `captcha` constant to it.
```jsx
<HCaptcha
@@ -153,7 +153,7 @@ Now import the Turnstile component from the @marsidev/react-turnstile library.
import { Turnstile } from '@marsidev/react-turnstile'
```
-Let's create an empty state to store our `captchaToken`
+Create an empty state to store the `captchaToken`
```jsx
const [captchaToken, setCaptchaToken] = useState()
@@ -165,7 +165,7 @@ Now lets add the Cloudflare Turnstile component to the JSX section of our code:
<Turnstile />
```
-We will pass it the sitekey we copied from the Cloudflare website as a property along with a `onSuccess` property which takes a callback function. This callback function will have a token as one of its properties. Let's set the token in the state using `setCaptchaToken`:
+Pass it the sitekey we copied from the Cloudflare website as a property along with a `onSuccess` property which takes a callback function. This callback function will have a token as one of its properties. Set the token in the state using `setCaptchaToken`:
```jsx
<Turnstile
diff --git a/apps/docs/content/guides/auth/enterprise-sso/auth-sso-saml.mdx b/apps/docs/content/guides/auth/enterprise-sso/auth-sso-saml.mdx
index ee7fc5d56dd..75e5841b52d 100644
--- a/apps/docs/content/guides/auth/enterprise-sso/auth-sso-saml.mdx
+++ b/apps/docs/content/guides/auth/enterprise-sso/auth-sso-saml.mdx
@@ -106,7 +106,7 @@ If you use [Multi-Factor Authentication](/docs/guides/auth/auth-mfa) with SSO, t
A common use case with SSO is to use the UUID of the identity provider as the identifier for the organization the user belongs to -- frequently known as a tenant. By associating the identity provider's UUID with your tenants, you can use restrictive RLS policies to scope down actions and data that a user is able to access.
-For example, let's say you have a table like:
+For example, say you have a table like:
```sql
create table organization_settings (
diff --git a/apps/docs/content/guides/database/extensions/http.mdx b/apps/docs/content/guides/database/extensions/http.mdx
index f987f35493c..5cd72c01538 100644
--- a/apps/docs/content/guides/database/extensions/http.mdx
+++ b/apps/docs/content/guides/database/extensions/http.mdx
@@ -20,7 +20,7 @@ The `http` extension allows you to call RESTful endpoints within Postgres.
## Overview
-Let's cover some basic concepts:
+This section covers basic concepts:
- REST: stands for REpresentational State Transfer. It's a way to request data from external services.
- RESTful APIs are servers which accept HTTP "calls". The calls are typically:
diff --git a/apps/docs/content/guides/database/extensions/pgaudit.mdx b/apps/docs/content/guides/database/extensions/pgaudit.mdx
index 6ec31eec88c..48c482aa12b 100644
--- a/apps/docs/content/guides/database/extensions/pgaudit.mdx
+++ b/apps/docs/content/guides/database/extensions/pgaudit.mdx
@@ -113,7 +113,7 @@ set pgaudit.log = 'none';
### User logging
-There are some cases where you may want to monitor a database user's actions. For instance, let's say you connected your database to [Zapier](/partners/integrations/zapier) and created a custom role for it to use:
+There are some cases where you may want to monitor a database user's actions. For instance, say you connected your database to [Zapier](/partners/integrations/zapier) and created a custom role for it to use:
```sql
create user "zapier" with password '<new password>';
diff --git a/apps/docs/content/guides/database/extensions/pgtap.mdx b/apps/docs/content/guides/database/extensions/pgtap.mdx
index a4e678a06f0..e7a0f7843be 100644
--- a/apps/docs/content/guides/database/extensions/pgtap.mdx
+++ b/apps/docs/content/guides/database/extensions/pgtap.mdx
@@ -8,7 +8,7 @@ description: 'Unit testing in Postgres.'
## Overview
-Let's cover some basic concepts:
+This section covers basic concepts:
- Unit tests: allow you to test small parts of a system (like a database table!).
- TAP: stands for [Test Anything Protocol](http://testanything.org/). It is an framework which aims to simplify the error reporting during testing.
diff --git a/apps/docs/content/guides/database/extensions/postgis.mdx b/apps/docs/content/guides/database/extensions/postgis.mdx
index 728bf7ebbf9..1e45230f2cf 100644
--- a/apps/docs/content/guides/database/extensions/postgis.mdx
+++ b/apps/docs/content/guides/database/extensions/postgis.mdx
@@ -47,9 +47,9 @@ drop extension if exists postgis;
## Examples
-Now that we are ready to get started with PostGIS, let’s create a table and see how we can use PostGIS for some typical use cases. Imagine we are creating a basic restaurant-searching app.
+To get started with PostGIS, create a table and see to use PostGIS for some typical use cases. Imagine creating a basic restaurant-searching app.
-Let’s create our table. Each row represents a restaurant with its location stored in `location` column as a `Point` type.
+Create the table. Each row represents a restaurant with its location stored in `location` column as a `Point` type.
```sql
create table if not exists public.restaurants (
@@ -330,7 +330,7 @@ val data = supabase.postgrest.rpc(
![Searching within a bounding box of a map](/docs/img/guides/database/extensions/postgis/map.png)
-When you are working on a map-based application where the user scrolls through your map, you might want to load the data that lies within the bounding box of the map every time your users scroll. PostGIS can return the rows that are within the bounding box just by supplying the bottom left and the top right coordinates. Let’s look at what the function would look like:
+When you are working on a map-based application where the user scrolls through your map, you might want to load the data that lies within the bounding box of the map every time your users scroll. PostGIS can return the rows that are within the bounding box by supplying the bottom left and the top right coordinates. The function looks like this:
```sql
create or replace function restaurants_in_view(min_lat float, min_long float, max_lat float, max_long float)
diff --git a/apps/docs/content/guides/database/extensions/timescaledb.mdx b/apps/docs/content/guides/database/extensions/timescaledb.mdx
index abea2efc839..588927defb0 100644
--- a/apps/docs/content/guides/database/extensions/timescaledb.mdx
+++ b/apps/docs/content/guides/database/extensions/timescaledb.mdx
@@ -60,7 +60,7 @@ It's good practice to create the extension within a separate schema (like `exten
## Usage
-To demonstrate how `timescaledb` works, consider a basic example where we have a table that stores temperature data from different sensors. We will create a table named "temperatures" and store data for two sensors.
+To demonstrate how `timescaledb` works, consider an example where we have a table that stores temperature data from different sensors. Create a table named "temperatures" and store data for two sensors.
First we create a hypertable, which is a virtual table that is partitioned into chunks based on time intervals. The hypertable acts as a proxy for the actual table and makes it easy to query and manage time-series data.
diff --git a/apps/docs/content/guides/database/full-text-search.mdx b/apps/docs/content/guides/database/full-text-search.mdx
index 89358757126..5104d8bb33c 100644
--- a/apps/docs/content/guides/database/full-text-search.mdx
+++ b/apps/docs/content/guides/database/full-text-search.mdx
@@ -831,7 +831,7 @@ don't need to be created at the time we execute the query. This will make our qu
### Searchable columns
-Let's create a new column `fts` inside the `books` table to store the searchable index of the `title` and `description` columns.
+Create a new column `fts` inside the `books` table to store the searchable index of the `title` and `description` columns.
We can use a special feature of Postgres called
[Generated Columns](https://www.postgresql.org/docs/current/ddl-generated-columns.html)
diff --git a/apps/docs/content/guides/database/functions.mdx b/apps/docs/content/guides/database/functions.mdx
index 5dac1acaa3e..3c9c3511177 100644
--- a/apps/docs/content/guides/database/functions.mdx
+++ b/apps/docs/content/guides/database/functions.mdx
@@ -32,7 +32,7 @@ and run the SQL queries yourself.
## Basic functions [#simple-functions]
-Let's create a basic Database Function which returns a string "hello world".
+Create a basic database function that returns the string "hello world".
```sql
create or replace function hello_world() -- 1
diff --git a/apps/docs/content/guides/database/joins-and-nesting.mdx b/apps/docs/content/guides/database/joins-and-nesting.mdx
index 361180a3a6c..f9b372ab745 100644
--- a/apps/docs/content/guides/database/joins-and-nesting.mdx
+++ b/apps/docs/content/guides/database/joins-and-nesting.mdx
@@ -8,7 +8,7 @@ The data APIs automatically detect relationships between Postgres tables. Since
## One-to-many joins
-Let's use an example database that stores `orchestral_sections` and `instruments`:
+Use an example database that stores `orchestral_sections` and `instruments`:
<Tabs
scrollable
@@ -111,7 +111,7 @@ create table instruments (
We can get the nested `SectionsWithInstruments` type like this:
```ts
-import { QueryResult, QueryData, QueryError } from '@supabase/supabase-js'
+import { QueryData, QueryError, QueryResult } from '@supabase/supabase-js'
const sectionsWithInstrumentsQuery = supabase.from('orchestral_sections').select(`
id,
diff --git a/apps/docs/content/guides/database/partitions.mdx b/apps/docs/content/guides/database/partitions.mdx
index 73e9f3a2903..8b18ef2c070 100644
--- a/apps/docs/content/guides/database/partitions.mdx
+++ b/apps/docs/content/guides/database/partitions.mdx
@@ -36,7 +36,7 @@ Postgres supports various partitioning methods based on how you want to partitio
## Creating partitioned tables
-Let's consider an example of range partitioning for a sales table based on the order date. We'll create monthly partitions to store data for each month:
+The following example uses range partitioning for a sales table based on the order date. We'll create monthly partitions to store data for each month:
```sql
create table sales (
@@ -109,7 +109,7 @@ Here are basic examples for each of the partitioning types in Postgres.
### Range partitioning
-Let's consider a range partitioning example for a table that stores sales data based on the order date. We'll create monthly partitions to store data for each month.
+The following range partitioning example stores sales data based on the order date. We'll create monthly partitions to store data for each month.
In this example, the **`sales`** table is partitioned into two partitions: **`sales_january`** and **`sales_february`**. The data in these partitions is based on the specified range of order dates:
@@ -137,7 +137,7 @@ create table sales_2000_02
### List partitioning
-Let's consider a list partitioning example for a table that stores customer data based on their region. We'll create partitions to store customers from different regions.
+The following list partitioning example stores customer data based on their region. We'll create partitions to store customers from different regions.
In this example, the **`customers`** table is partitioned into two partitions: `customers_americas` and `customers_asia`. The data in these partitions is based on the specified list of regions:
diff --git a/apps/docs/content/guides/database/postgres/cascade-deletes.mdx b/apps/docs/content/guides/database/postgres/cascade-deletes.mdx
index a250cb473fc..e3a73311ce0 100644
--- a/apps/docs/content/guides/database/postgres/cascade-deletes.mdx
+++ b/apps/docs/content/guides/database/postgres/cascade-deletes.mdx
@@ -38,7 +38,7 @@ In practice, you can use either `NO ACTION` or `RESTRICT` depending on your need
## Example
-Let's further illustrate the difference with an example. We'll use the following data:
+To illustrate the difference, use the following example. We'll use the following data:
`grandparent`
@@ -117,7 +117,7 @@ Even though the foreign key constraint between parent and grandparent is `CASCAD
### `NO ACTION`
-Let's change the child-father relationship to `NO ACTION`:
+Change the child-father relationship to `NO ACTION`:
```sql
alter table child
@@ -157,7 +157,7 @@ ERROR: update or delete on table "parent" violates foreign key constraint "child
DETAIL: Key (id)=(1) is still referenced from table "child".
```
-But, when we combine it with _other_ constraints, then any other constraints take precedence. For example, let's run the same but add a `mother` column that has a `CASCADE` delete:
+But, when we combine it with _other_ constraints, then any other constraints take precedence. For example, run the same scenario but add a `mother` column that has a `CASCADE` delete:
```sql
alter table child
@@ -169,7 +169,7 @@ set mother = 2
where id = 1;
```
-Then let's run a delete on the `grandparent` table:
+Then run a delete on the `grandparent` table:
```shell
postgres=# delete from grandparent;
diff --git a/apps/docs/content/guides/database/postgres/column-level-security.mdx b/apps/docs/content/guides/database/postgres/column-level-security.mdx
index d1e3ebbdb93..13937a5fc64 100644
--- a/apps/docs/content/guides/database/postgres/column-level-security.mdx
+++ b/apps/docs/content/guides/database/postgres/column-level-security.mdx
@@ -22,7 +22,7 @@ Restricted roles cannot use the wildcard operator (`*`) on the affected table. I
Policies in Row Level Security (RLS) are used to restrict access to rows in a table. Think of them like adding a `WHERE` clause to every query.
-For example, let's assume you have a `posts` table with the following columns:
+For example, assume you have a `posts` table with the following columns:
- `id`
- `user_id`
diff --git a/apps/docs/content/guides/database/postgres/enums.mdx b/apps/docs/content/guides/database/postgres/enums.mdx
index 6fbb8d4b602..8d8ff726b79 100644
--- a/apps/docs/content/guides/database/postgres/enums.mdx
+++ b/apps/docs/content/guides/database/postgres/enums.mdx
@@ -93,7 +93,7 @@ where name = 'Alice';
To add new values to an existing Postgres Enum, you can use the `ALTER TYPE` statement. Here's how you can do it:
-Let's say you have an existing Enum called `mood`, and you want to add a new value, `content`:
+Say you have an existing enum called `mood`, and you want to add a new value, `content`:
{/* prettier-ignore */}
```sql
diff --git a/apps/docs/content/guides/database/postgres/indexes.mdx b/apps/docs/content/guides/database/postgres/indexes.mdx
index a4a33e4ab6a..3263e5a6e6a 100644
--- a/apps/docs/content/guides/database/postgres/indexes.mdx
+++ b/apps/docs/content/guides/database/postgres/indexes.mdx
@@ -13,7 +13,7 @@ Even though indexes improve query performance, the Postgres query planner may no
## Create an index
-Let's take an example table:
+Start with an example table:
```sql
create table persons (
diff --git a/apps/docs/content/guides/database/postgres/row-level-security.mdx b/apps/docs/content/guides/database/postgres/row-level-security.mdx
index ca895abf839..3e1112bc60e 100644
--- a/apps/docs/content/guides/database/postgres/row-level-security.mdx
+++ b/apps/docs/content/guides/database/postgres/row-level-security.mdx
@@ -172,7 +172,7 @@ Supabase provides some [helpers](#helper-functions) that simplify RLS if you're
You can specify select policies with the `using` clause.
-Let's say you have a table called `profiles` in the public schema and you want to enable read access to everyone.
+Say you have a table called `profiles` in the public schema and you want to enable read access to everyone.
```sql
-- 1. Create table
@@ -204,7 +204,7 @@ for select using ( (select auth.uid()) = user_id );
You can specify insert policies with the `with check` clause. The `with check` expression ensures that any new row data adheres to the policy constraints.
-Let's say you have a table called `profiles` in the public schema and you only want users to be able to create a profile for themselves. In that case, we want to check their User ID matches the value that they are trying to insert:
+Say you have a table called `profiles` in the public schema and you only want users to create a profile for themselves. In that case, we want to check their User ID matches the value that they are trying to insert:
```sql
-- 1. Create table
@@ -230,7 +230,7 @@ You can specify update policies by combining both the `using` and `with check` e
The `using` clause represents the condition that must be true for the update to be allowed, and `with check` clause ensures that the updates made adhere to the policy constraints.
-Let's say you have a table called `profiles` in the public schema and you only want users to be able to update their own profile.
+Say you have a table called `profiles` in the public schema and you only want users to update their own profile.
You can create a policy where the `using` clause checks if the user owns the profile being updated. And the `with check` clause ensures that, in the resultant row, users do not change the `user_id` to a value that is not equal to their User ID, maintaining that the modified profile still meets the ownership condition.
@@ -265,7 +265,7 @@ To perform an `UPDATE` operation, a corresponding [`SELECT` policy](#select-poli
You can specify delete policies with the `using` clause.
-Let's say you have a table called `profiles` in the public schema and you only want users to be able to delete their own profile:
+Say you have a table called `profiles` in the public schema and you only want users to be able to delete their own profile:
```sql
-- 1. Create table
diff --git a/apps/docs/content/guides/database/tables.mdx b/apps/docs/content/guides/database/tables.mdx
index 79c3a43e0fa..2a210617936 100644
--- a/apps/docs/content/guides/database/tables.mdx
+++ b/apps/docs/content/guides/database/tables.mdx
@@ -357,7 +357,7 @@ height={1145}
This is where the "Relational" naming comes from, as data typically forms some sort of relationship.
In our "movies" example above, we might want to add a "category" for each movie (for example, "Action", or "Documentary").
-Let's create a new table called `categories` and "link" our `movies` table.
+Create a new table called `categories` and link it to the `movies` table.
```sql
create table categories (
diff --git a/apps/docs/content/guides/functions/examples/discord-bot.mdx b/apps/docs/content/guides/functions/examples/discord-bot.mdx
index 085e109716b..a7ba70a4806 100644
--- a/apps/docs/content/guides/functions/examples/discord-bot.mdx
+++ b/apps/docs/content/guides/functions/examples/discord-bot.mdx
@@ -153,7 +153,7 @@ Navigate to your Function details in the Supabase Dashboard to get your Endpoint
1. Go back to your application (Greeter) page on Discord Developer Portal
2. Fill **INTERACTIONS ENDPOINT URL** field with the URL and click on **Save Changes**.
-The application is now ready. Let's proceed to the next section to install it.
+The application is now ready. Proceed to the next section to install it.
## Install the slash command on your Discord server
diff --git a/apps/docs/content/guides/functions/examples/image-manipulation.mdx b/apps/docs/content/guides/functions/examples/image-manipulation.mdx
index 3afed37cb90..7bddc3ed424 100644
--- a/apps/docs/content/guides/functions/examples/image-manipulation.mdx
+++ b/apps/docs/content/guides/functions/examples/image-manipulation.mdx
@@ -61,7 +61,7 @@ If you open the `output.png` file you will find a transformed version of your or
### Deploy to your hosted project
-Now, let's deploy the function to your Supabase project.
+Deploy the function to your Supabase project.
```bash
supabase link
diff --git a/apps/docs/content/guides/functions/unit-test.mdx b/apps/docs/content/guides/functions/unit-test.mdx
index 98af634535f..0f5fec4f31e 100644
--- a/apps/docs/content/guides/functions/unit-test.mdx
+++ b/apps/docs/content/guides/functions/unit-test.mdx
@@ -123,7 +123,7 @@ Make sure to replace the placeholders (`supabaseUrl`, `supabaseKey`, `my_table`)
## Running Edge Functions locally
-To locally test and debug Edge Functions, you can use the Supabase CLI. Let's explore how to run Edge Functions locally using the Supabase CLI:
+To locally test and debug Edge Functions, use the Supabase CLI to run Edge Functions locally:
1. Ensure that the Supabase server is running by executing the following command:
diff --git a/apps/docs/content/guides/getting-started/quickstarts/redwoodjs.mdx b/apps/docs/content/guides/getting-started/quickstarts/redwoodjs.mdx
index 3e8a6c42fc3..661521fefbc 100644
--- a/apps/docs/content/guides/getting-started/quickstarts/redwoodjs.mdx
+++ b/apps/docs/content/guides/getting-started/quickstarts/redwoodjs.mdx
@@ -143,7 +143,7 @@ hideToc: true
<StepHikeCompact.Step step={8}>
<StepHikeCompact.Details title="Update seed script">
- Let's seed the database with a few instruments.
+ Seed the database with a few instruments.
Update the file `scripts/seed.ts` to contain the following code:
</StepHikeCompact.Details>
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-flutter.mdx b/apps/docs/content/guides/getting-started/tutorials/with-flutter.mdx
index 9c345a4d4dd..9f9d8b943f5 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-flutter.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-flutter.mdx
@@ -18,7 +18,7 @@ If you get stuck while working through this guide, refer to the [full example on
## Building the app
-Let's start building the Flutter app from scratch.
+Build the Flutter app from scratch.
### Initialize a Flutter app
@@ -29,7 +29,7 @@ an app called `supabase_quickstart`:
flutter create supabase_quickstart
```
-Then let's install the only additional dependency: [`supabase_flutter`](https://pub.dev/packages/supabase_flutter)
+Then install the only additional dependency: [`supabase_flutter`](https://pub.dev/packages/supabase_flutter)
Copy and paste the following line in your pubspec.yaml to install the package:
@@ -41,7 +41,7 @@ Run `flutter pub get` to install the dependencies.
### Setup deep links
-Now that we have the dependencies installed let's setup deep links.
+With dependencies installed, set up deep links.
Setting up deep links is required to bring back the user to the app when they click on the magic link to sign in.
We can setup deep links with just a minor tweak on our Flutter application.
@@ -144,7 +144,7 @@ void main() {
### Main function
-Now that we have deep links ready let's initialize the Supabase client inside our `main` function with the API credentials that you copied [earlier](#get-the-api-keys). These variables will be exposed on the app, and that's completely fine since we have [Row Level Security](/docs/guides/auth#row-level-security) enabled on our Database.
+With deep links configured, initialize the Supabase client inside the `main` function with the API credentials that you copied [earlier](#get-the-api-keys). These variables will be exposed on the app, and that's completely fine since we have [Row Level Security](/docs/guides/auth#row-level-security) enabled on our Database.
<$CodeTabs>
@@ -191,7 +191,7 @@ Notice that we have a `showSnackBar` extension method that we will use to show s
### Set up a login page
-Let's create a Flutter widget to manage logins and sign ups. We will use Magic Links, so users can sign in with their email without using passwords.
+Create a Flutter widget to manage logins and sign ups. We will use Magic Links, so users can sign in with their email without using passwords.
Notice that this page sets up a listener on the user's auth state using `onAuthStateChange`. A new event will fire when the user comes back to the app by clicking their magic link, which this page can catch and redirect the user accordingly.
@@ -310,7 +310,7 @@ class _LoginPageState extends State<LoginPage> {
### Set up account page
After a user is signed in we can allow them to edit their profile details and manage their account.
-Let's create a new widget called `account_page.dart` for that.
+Create a new widget called `account_page.dart`.
<$CodeTabs>
@@ -459,7 +459,7 @@ class _AccountPageState extends State<AccountPage> {
### Launch!
-Now that we have all the components in place, let's update `lib/main.dart`.
+With all components in place, update `lib/main.dart`.
The `home` of the `MaterialApp`, meaning the initial page shown to the user, will be the `LoginPage` if the user is not authenticated, and the `AccountPage` if the user is authenticated.
We also included some theming to make the app look a bit nicer.
@@ -569,7 +569,7 @@ Once you are done with all of the above, it is time to dive into coding.
### Create an upload widget
-Let's create an avatar for the user so that they can upload a profile photo.
+Create an avatar so the user can upload a profile photo.
We can start by creating a new component:
<$CodeTabs>
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-ionic-angular.mdx b/apps/docs/content/guides/getting-started/tutorials/with-ionic-angular.mdx
index 0148facc6db..a1bec2c404b 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-ionic-angular.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-ionic-angular.mdx
@@ -125,7 +125,7 @@ Every Supabase project is configured with [Storage](/docs/guides/storage) for ma
### Create an upload widget
-Let's create an avatar for the user so that they can upload a profile photo.
+Create an avatar so the user can upload a profile photo.
First, install two packages in order to interact with the user's camera.
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-nuxt-3.mdx b/apps/docs/content/guides/getting-started/tutorials/with-nuxt-3.mdx
index b116e3d8266..4541d2fc44b 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-nuxt-3.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-nuxt-3.mdx
@@ -18,7 +18,7 @@ If you get stuck while working through this guide, you can find the [full exampl
## Building the app
-Start building the Vue 3 app from scratch.
+Build the Vue 3 app from scratch.
### Initialize a Nuxt 3 app
@@ -128,7 +128,7 @@ To access the user information, use the composable [`useSupabaseUser`](https://s
### Account component
After a user is signed in we can allow them to edit their profile details and manage their account.
-Create a new component for that called `Account.vue`.
+Create a new component called `Account.vue`.
<$CodeTabs>
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx b/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx
index 36482c6e839..7ff85870f22 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx
@@ -43,7 +43,7 @@ to how your Supabase `public` schema references the `auth.users`.
## Building the app
-Let's start building the RedwoodJS app from scratch.
+Build the RedwoodJS app from scratch.
<Admonition type="note">
@@ -77,7 +77,7 @@ While the app is installing, you should see:
Thanks for trying out Redwood!
```
-Then let's install the only additional dependency [supabase-js](https://github.com/supabase/supabase-js) by running the `setup auth` command:
+Then install the only additional dependency [supabase-js](https://github.com/supabase/supabase-js) by running the `setup auth` command:
```bash
yarn redwood setup auth supabase
@@ -174,7 +174,7 @@ You can find the full contents of this file [in the example repository](https://
### Start RedwoodJS and your first page
-Let's test our setup at the moment by starting up the app:
+Test your setup by starting the app:
```bash
yarn rw dev
@@ -188,7 +188,7 @@ yarn rw dev
You should see a "Welcome to RedwoodJS" page and a message about not having any pages yet.
-So, let's create a "home" page:
+Create a "home" page:
```bash
yarn rw generate page home /
@@ -232,7 +232,7 @@ export default Routes
### Set up a login component
-Let's set up a Redwood component to manage logins and sign ups. We'll use Magic Links, so users can sign in with their email without using passwords.
+Set up a Redwood component to manage logins and sign ups. We'll use Magic Links, so users can sign in with their email without using passwords.
```bash
yarn rw g component auth
@@ -310,7 +310,7 @@ export default Auth
After a user is signed in we can allow them to edit their profile details and manage their account.
-Let's create a new component for that called `Account.js`.
+Create a new component called `Account.js`.
```bash
yarn rw g component account
@@ -495,7 +495,7 @@ Next, add a way for users to upload a profile photo. Supabase configures every p
### Create an upload widget
-Let's create an avatar for the user so that they can upload a profile photo. We can start by creating a new component:
+Create an avatar so the user can upload a profile photo. Start by creating a new component:
```bash
yarn rw g component avatar
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-swift.mdx b/apps/docs/content/guides/getting-started/tutorials/with-swift.mdx
index 4e240e1d969..45057d067c1 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-swift.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-swift.mdx
@@ -17,7 +17,7 @@ If you get stuck while working through this guide, you can find the [full exampl
## Building the app
-Let's start building the SwiftUI app from scratch.
+Build the SwiftUI app from scratch.
### Create a SwiftUI app in Xcode
@@ -281,7 +281,7 @@ Next, add a way for users to upload a profile photo. Supabase configures every p
### Add `PhotosPicker`
-Let's add support for the user to pick an image from the library and upload it.
+Add support for the user to pick an image from the library and upload it.
Start by creating a new type to hold the picked avatar image:
<$CodeTabs>
diff --git a/apps/docs/content/guides/integrations/supabase-for-platforms.mdx b/apps/docs/content/guides/integrations/supabase-for-platforms.mdx
index c1ac2b31012..45be844a97f 100644
--- a/apps/docs/content/guides/integrations/supabase-for-platforms.mdx
+++ b/apps/docs/content/guides/integrations/supabase-for-platforms.mdx
@@ -267,7 +267,7 @@ It's important that the data in development branches is NOT production data, esp
</Admonition>
-It's common in `DEV` branches to "seed" data. This is basically test data for users. Let's insert the following seed to our new todos table:
+In `DEV` branches, seed data is common test data for users. Insert the following seed into the new todos table:
```sql
insert into todos (task)
diff --git a/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx b/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx
index 6401ab340f4..3922893cc9e 100644
--- a/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx
+++ b/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx
@@ -494,7 +494,7 @@ create policy "Users can update their own comments"
#### 4. Test cases:
-Now everything is setup, let's write RLS test cases, note that each section could be in its own test:
+With setup complete, write RLS test cases. Each section can be in its own test:
```sql
-- Assuming we already have: 000-setup-tests-hooks.sql file we can use tests helpers
diff --git a/apps/docs/content/guides/platform/custom-domains.mdx b/apps/docs/content/guides/platform/custom-domains.mdx
index 441a7657a4d..66f65eb63fb 100644
--- a/apps/docs/content/guides/platform/custom-domains.mdx
+++ b/apps/docs/content/guides/platform/custom-domains.mdx
@@ -90,6 +90,7 @@ Use the [`domains reverify`](/docs/reference/cli/supabase-domains-reverify) comm
supabase domains reverify --project-ref abcdefghijklmnopqrst
```
+{/* supa-mdx-lint-disable-next-line Rule004ExcludeWords */}
In the background, Supabase will check your DNS records and issue an SSL certificate. Supabase uses multiple Certificate Authorities (including Let's Encrypt, Google Trust Services and SSL.com) to ensure high availability. The specific issuer is chosen based on availability and this process can take up to 30 minutes.
### Prepare to activate your domain
@@ -160,7 +161,7 @@ To get started:
You can configure vanity subdomains via the CLI only.
-Let's assume your Supabase project's domain is `abcdefghijklmnopqrst.supabase.co` and you wish to configure a vanity subdomain at `my-example-brand.supabase.co`.
+Assume your Supabase project's domain is `abcdefghijklmnopqrst.supabase.co` and you wish to configure a vanity subdomain at `my-example-brand.supabase.co`.
### Check subdomain availability
diff --git a/apps/docs/content/guides/platform/manage-your-usage/edge-function-invocations.mdx b/apps/docs/content/guides/platform/manage-your-usage/edge-function-invocations.mdx
index 64e08ed131d..a3747e1aceb 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/edge-function-invocations.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/edge-function-invocations.mdx
@@ -13,7 +13,7 @@ Edge Function Invocations are billed using Package pricing, with each package re
### Example
-For simplicity, let's assume a package size of 1 million and a charge of <Price price="2" /> per package without a free quota.
+For simplicity, assume a package size of 1 million and a charge of <Price price="2" /> per package without a free quota.
| Invocations | Packages Billed | Costs |
| ----------- | --------------- | ------------------- |
diff --git a/apps/docs/content/guides/platform/manage-your-usage/realtime-messages.mdx b/apps/docs/content/guides/platform/manage-your-usage/realtime-messages.mdx
index 5d582735396..ba6dc01a594 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/realtime-messages.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/realtime-messages.mdx
@@ -19,7 +19,7 @@ Realtime Messages are billed using Package pricing, with each package representi
### Example
-For simplicity, let's assume a package size of 1,000,000 and a charge of <Price price="2.50" /> per package without quota.
+For simplicity, assume a package size of 1,000,000 and a charge of <Price price="2.50" /> per package without quota.
| Messages | Packages Billed | Costs |
| --------- | --------------- | ---------------------- |
diff --git a/apps/docs/content/guides/platform/manage-your-usage/realtime-peak-connections.mdx b/apps/docs/content/guides/platform/manage-your-usage/realtime-peak-connections.mdx
index 8722b1cd36a..b8fa985060c 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/realtime-peak-connections.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/realtime-peak-connections.mdx
@@ -24,7 +24,7 @@ Realtime Peak Connections are billed using Package pricing, with each package re
### Example
-For simplicity, let's assume a package size of 1,000 and a charge of <Price price="10" /> per package with no quota.
+For simplicity, assume a package size of 1,000 and a charge of <Price price="10" /> per package with no quota.
| Peak Connections | Packages Billed | Costs |
| ---------------- | --------------- | -------------------- |
diff --git a/apps/docs/content/guides/platform/manage-your-usage/storage-image-transformations.mdx b/apps/docs/content/guides/platform/manage-your-usage/storage-image-transformations.mdx
index f09f5861aed..743ef928393 100644
--- a/apps/docs/content/guides/platform/manage-your-usage/storage-image-transformations.mdx
+++ b/apps/docs/content/guides/platform/manage-your-usage/storage-image-transformations.mdx
@@ -53,7 +53,7 @@ Storage Image Transformations are billed using Package pricing, with each packag
### Example
-For simplicity, let's assume a package size of 1,000 and a charge of <Price price="5" /> per package with no quota.
+For simplicity, assume a package size of 1,000 and a charge of <Price price="5" /> per package with no quota.
| Origin Images | Packages Billed | Costs |
| ------------- | --------------- | -------------------- |
diff --git a/apps/docs/content/guides/realtime/postgres-changes.mdx b/apps/docs/content/guides/realtime/postgres-changes.mdx
index 9c5ac6caaeb..fc5673ed61b 100644
--- a/apps/docs/content/guides/realtime/postgres-changes.mdx
+++ b/apps/docs/content/guides/realtime/postgres-changes.mdx
@@ -4,7 +4,7 @@ subtitle: 'Listen to Postgres changes using Supabase Realtime.'
description: 'Listen to Postgres changes using Supabase Realtime.'
---
-Let's explore how to use Realtime's Postgres Changes feature to listen to database events.
+Use Realtime's Postgres Changes to listen to database events.
## Quick start
diff --git a/apps/docs/content/guides/realtime/presence.mdx b/apps/docs/content/guides/realtime/presence.mdx
index 52c0a9f29e2..5618cce8863 100644
--- a/apps/docs/content/guides/realtime/presence.mdx
+++ b/apps/docs/content/guides/realtime/presence.mdx
@@ -4,7 +4,7 @@ description: 'Share state between users with Realtime Presence.'
subtitle: 'Share state between users with Realtime Presence.'
---
-Let's explore how to implement Realtime Presence to track state between multiple users.
+Use Realtime Presence to track state between multiple users.
## Usage
diff --git a/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx b/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
index a32e5609e26..6afbb77b6ac 100644
--- a/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
+++ b/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
@@ -30,7 +30,7 @@ using ( true );
### Create a trigger function
-Let's create a function that we can call any time a record is created, updated, or deleted. This function will make use of some of Postgres's native [trigger variables](https://www.postgresql.org/docs/current/plpgsql-trigger.html#PLPGSQL-DML-TRIGGER). For this example, we want to have a topic with the name `topic:<record id>` to which we're going to broadcast events.
+Create a function to call whenever a record is created, updated, or deleted. This function will make use of some of Postgres's native [trigger variables](https://www.postgresql.org/docs/current/plpgsql-trigger.html#PLPGSQL-DML-TRIGGER). For this example, we want to have a topic with the name `topic:<record id>` to which we're going to broadcast events.
{/* prettier-ignore */}
```sql
@@ -56,7 +56,7 @@ $$;
### Create a trigger
-Let's set up a trigger so the function is executed after any changes to the table.
+Set up a trigger so the function runs after any changes to the table.
{/* prettier-ignore */}
```sql
diff --git a/apps/docs/content/guides/self-hosting/self-hosted-proxy-https.mdx b/apps/docs/content/guides/self-hosting/self-hosted-proxy-https.mdx
index cbdaebfb1c4..cefb46b8b26 100644
--- a/apps/docs/content/guides/self-hosting/self-hosted-proxy-https.mdx
+++ b/apps/docs/content/guides/self-hosting/self-hosted-proxy-https.mdx
@@ -4,6 +4,8 @@ description: 'Set up a reverse proxy with HTTPS for self-hosted Supabase.'
subtitle: 'Set up a reverse proxy with HTTPS for self-hosted Supabase.'
---
+{/* supa-mdx-lint-disable Rule004ExcludeWords */}
+
HTTPS is required for production self-hosted Supabase deployments. This guide covers two production approaches using a reverse proxy in front of self-hosted Supabase API gateway, plus a self-signed certificate option for development environment.
## Before you begin
diff --git a/apps/docs/content/guides/storage/cdn/fundamentals.mdx b/apps/docs/content/guides/storage/cdn/fundamentals.mdx
index f23548b098f..825fd0dc8bd 100644
--- a/apps/docs/content/guides/storage/cdn/fundamentals.mdx
+++ b/apps/docs/content/guides/storage/cdn/fundamentals.mdx
@@ -9,7 +9,7 @@ All assets uploaded to Supabase Storage are cached on a Content Delivery Network
### Example
-Let's walk through an example of how a CDN helps with performance.
+The following example shows how a CDN helps with performance.
A new bucket is created for a Supabase project launched in Singapore. All requests to the Supabase Storage API are routed to the CDN first.
diff --git a/apps/docs/content/guides/storage/schema/custom-roles.mdx b/apps/docs/content/guides/storage/schema/custom-roles.mdx
index bcc5447a490..5edc3802f40 100644
--- a/apps/docs/content/guides/storage/schema/custom-roles.mdx
+++ b/apps/docs/content/guides/storage/schema/custom-roles.mdx
@@ -12,7 +12,7 @@ Supabase Storage uses the same role-based access control system as any other Sup
## Create a custom role
-Let's create a custom role `manager` to provide full read access to a specific bucket. For a more advanced setup, see the [RBAC Guide](/docs/guides/api/custom-claims-and-role-based-access-control-rbac#create-auth-hook-to-apply-user-role).
+Create a custom role `manager` to provide full read access to a specific bucket. For a more advanced setup, see the [RBAC Guide](/docs/guides/api/custom-claims-and-role-based-access-control-rbac#create-auth-hook-to-apply-user-role).
```sql
create role 'manager';
@@ -24,7 +24,7 @@ grant anon to manager;
## Create a policy
-Let's create a policy that gives full read permissions to all objects in the bucket `teams` for the `manager` role.
+Create a policy that gives full read permissions to all objects in the bucket `teams` for the `manager` role.
```sql
create policy "Manager can view all files in the bucket 'teams'"
diff --git a/apps/docs/content/guides/storage/serving/bandwidth.mdx b/apps/docs/content/guides/storage/serving/bandwidth.mdx
index 021810276c4..8bdf13e9812 100644
--- a/apps/docs/content/guides/storage/serving/bandwidth.mdx
+++ b/apps/docs/content/guides/storage/serving/bandwidth.mdx
@@ -63,7 +63,7 @@ curl -s -w "%{size_download}\n" -o /dev/null "https://my_project.supabase.co/sto
```
This will return the size of the file in bytes.
-For this example, let's say that `20230902_200037.gif` has a file size of 3 megabytes and `volleyball.png` has a file size of 570 kilobytes.
+For this example, assume that `20230902_200037.gif` has a file size of 3 megabytes and `volleyball.png` has a file size of 570 kilobytes.
Now, we have to sum all the egress for all the files to get the total egress:
diff --git a/apps/docs/content/troubleshooting/manually-created-databases-are-not-visible-in-the-supabase-dashboard-4415aa.mdx b/apps/docs/content/troubleshooting/manually-created-databases-are-not-visible-in-the-supabase-dashboard-4415aa.mdx
index 87e25287dca..39c79699176 100644
--- a/apps/docs/content/troubleshooting/manually-created-databases-are-not-visible-in-the-supabase-dashboard-4415aa.mdx
+++ b/apps/docs/content/troubleshooting/manually-created-databases-are-not-visible-in-the-supabase-dashboard-4415aa.mdx
@@ -11,7 +11,7 @@ If you've manually created an additional database within your Supabase project,
## Key concepts
-Before diving into the problem, let's define some key terms:
+Before diving into the problem, define some key terms:
- **What is a Postgres Cluster?**
In Postgres terminology, a "cluster" refers to a collection of databases managed by a single Postgres server instance. This single instance can host multiple independent databases, each with its own set of tables, users, and permissions. Every Supabase project runs on top of a full Postgres cluster.
diff --git a/apps/docs/content/troubleshooting/rls-simplified-BJTcS8.mdx b/apps/docs/content/troubleshooting/rls-simplified-BJTcS8.mdx
index af9d929abe3..e2cbb853fde 100644
--- a/apps/docs/content/troubleshooting/rls-simplified-BJTcS8.mdx
+++ b/apps/docs/content/troubleshooting/rls-simplified-BJTcS8.mdx
@@ -75,7 +75,7 @@ WHERE
### WITH CHECK:
-Let's say you have a profile table. Well, you don't want user's to be able to modify their user_id when they make an insert, do you?
+Say you have a profile table. Well, you don't want user's to be able to modify their user_id when they make an insert, do you?
The `WITH CHECK` condition inspects values that are being added or modified. For INSERT you'd use it by itself. There's no need for a using clause:
diff --git a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx
index 7234ad53a91..5680737403d 100644
--- a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx
+++ b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx
@@ -119,7 +119,7 @@ When a distinct combination connects to your database, a new direct connection p
### **Does Supavisor immediately establish the max pool size?**
-No, it doesn't. Let's break it down:
+No, it doesn't. See why:
- In transaction mode, the pooler will only add connections if there are not enough connections to service all pending queries simultaneously. If 10 clients connect, but a single direct connection can comfortably accommodate them all, the pooler will not create more.
- If necessary, it can create as many connections to prevent queries from pending up to the limit specified by the "Pool Size".