From 734049feb850605e83d84bc4f2d254afa802eda9 Mon Sep 17 00:00:00 2001 From: Clarence Date: Thu, 21 Dec 2023 20:35:21 +0100 Subject: [PATCH] docs: fixed multiple typos (#19928) * docs: fixed typo integraions --> integrations * docs: fixed typo configration --> integrations * docs: fixed typo serivce --> service * docs: fixed typo thse --> these * docs: fixed typo infrastrusture --> infrastructure * docs: fixed typo organizatio --> organization * docs: fixed typo optimisation --> optimization * docs: fixed typo entitites --> entities * docs: fixed typo troubeshooting --> troubleshooting * prettier fix --------- Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> --- apps/docs/pages/guides/platform/branching.mdx | 2 +- .../migrating-and-upgrading-projects.mdx | 2 +- .../build-a-supabase-integration.mdx | 2 +- .../platform/oauth-apps/oauth-scopes.mdx | 40 +++++++++---------- .../guides/platform/org-based-billing.mdx | 4 +- .../pages/guides/platform/performance.mdx | 2 +- .../pages/guides/platform/permissions.mdx | 4 +- .../docs/pages/guides/platform/sso/gsuite.mdx | 2 +- .../pages/guides/platform/troubleshooting.mdx | 2 +- 9 files changed, 30 insertions(+), 30 deletions(-) diff --git a/apps/docs/pages/guides/platform/branching.mdx b/apps/docs/pages/guides/platform/branching.mdx index a2b0d7319d6..18f2b4dab56 100644 --- a/apps/docs/pages/guides/platform/branching.mdx +++ b/apps/docs/pages/guides/platform/branching.mdx @@ -572,7 +572,7 @@ If you have multiple preview branches, each preview branch might contain differe When a preview branch is merged into the production branch, it creates a schema drift between the production branch and the preview branches you haven't merged yet. -You can solve thse conflicts the way you would solve normal Git Conflicts: merge or rebase from your production Git branch to your preview Git branch. Since migrations are applied sequentially, ensure that migration files are timestamped correctly after the rebase. Changes that build on top of earlier changes should always have later timestamps. +You can solve these conflicts the way you would solve normal Git Conflicts: merge or rebase from your production Git branch to your preview Git branch. Since migrations are applied sequentially, ensure that migration files are timestamped correctly after the rebase. Changes that build on top of earlier changes should always have later timestamps. ### Changing Production Branch diff --git a/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx b/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx index f03a88f945f..5da5d2b54af 100644 --- a/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx +++ b/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx @@ -264,7 +264,7 @@ const NEW_PROJECT_SERVICE_KEY = 'new-project-service-key-yyy' ### Transfer to a different organization -Note that project migration is for transferring your projects to different regions. If you need to move your project to a different organization without touching the infrastrusture, see [project transfers](/docs/guides/platform/project-transfer). +Note that project migration is for transferring your projects to different regions. If you need to move your project to a different organization without touching the infrastructure, see [project transfers](/docs/guides/platform/project-transfer). export const Page = ({ children }) => diff --git a/apps/docs/pages/guides/platform/oauth-apps/build-a-supabase-integration.mdx b/apps/docs/pages/guides/platform/oauth-apps/build-a-supabase-integration.mdx index 56a5fcd5a74..75235a2259f 100644 --- a/apps/docs/pages/guides/platform/oauth-apps/build-a-supabase-integration.mdx +++ b/apps/docs/pages/guides/platform/oauth-apps/build-a-supabase-integration.mdx @@ -130,7 +130,7 @@ There are a couple common patterns you can consider adding to your integration t ### Store API keys in env variables -Some integraions, e.g. like [Cloudflare Workers](/partners/integrations/cloudflare-workers) provide convenient access to the API URL and API keys to allow user to speed up development. +Some integrations, e.g. like [Cloudflare Workers](/partners/integrations/cloudflare-workers) provide convenient access to the API URL and API keys to allow user to speed up development. Using the management API, you can retrieve a project's API credentials using the [`/projects/{ref}/api-keys` endpoint](https://api.supabase.com/api/v1#/projects/getProjectApiKeys). diff --git a/apps/docs/pages/guides/platform/oauth-apps/oauth-scopes.mdx b/apps/docs/pages/guides/platform/oauth-apps/oauth-scopes.mdx index 3bde7d623d7..2dba7d4b96b 100644 --- a/apps/docs/pages/guides/platform/oauth-apps/oauth-scopes.mdx +++ b/apps/docs/pages/guides/platform/oauth-apps/oauth-scopes.mdx @@ -19,26 +19,26 @@ Scopes are set when you [create an OAuth app](/docs/guides/platform/oauth-apps/b ## Available Scopes -| Name | Type | Description | -| ---------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Auth` | `Read` | Retrieve a project's auth configuration
Retrieve a project's SAML SSO providers | -| `Auth` | `Write` | Update a project's auth configuration
Create, update, or delete a project's SAML SSO providers | -| `Database` | `Read` | Retrieve the database configuration
Retrieve SQL snippets
Check if the database is in read-only mode
Retrieve a database's SSL enforcement configuration
Retrieve a database's schema typescript types | -| `Database` | `Write` | Create a SQL query
Enable database webhooks on the project
Update the project's database configration
Update a database's SSL enforcement configration
Disable read-only mode for 15mins
Retrieve the pgbouncer configuration
Create a PITR backup for a database | -| `Domains` | `Read` | Retrieve the custom domains for a project
Retrieve the vanity subdomain configuration for a project | -| `Domains` | `Write` | Activate, initialize, reverify, or delete the custom domain for a project
Activate, delete or check the availability of a vanity subdomain for a project | -| `Edge Functions` | `Read` | Retrieve information about a project's edge functions | -| `Edge Functions` | `Write` | Create, update, or delete an edge function | -| `Environment` | `Read` | Retrieve branches in a project | -| `Environment` | `Write` | Create, update, or delete a branch | -| `Organizations` | `Read` | Retrieve an organization's metadata
Retrieve all members in an organization | -| `Organizations` | `Write` | Create an organization | -| `Projects` | `Read` | Retrieve a project's metadata
Check if a project's database is eligible for upgrade
Retrieve a project's network restrictions
Retrieve a project's network bans | -| `Projects` | `Write` | Create a project
Upgrade a project's database
Remove a project's network bans
Update a project's network restrictions | -| `Rest` | `Read` | Retrieve a project's PostgREST configuration | -| `Rest` | `Write` | Update a project's PostgREST configuration | -| `Secrets` | `Read` | Retrieve a project's API keys
Retrieve a project's secrets
Retrieve a project's pgsodium config | -| `Secrets` | `Write` | Create or update a project's secrets
Update a project's pgsodium configuration | +| Name | Type | Description | +| ---------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Auth` | `Read` | Retrieve a project's auth configuration
Retrieve a project's SAML SSO providers | +| `Auth` | `Write` | Update a project's auth configuration
Create, update, or delete a project's SAML SSO providers | +| `Database` | `Read` | Retrieve the database configuration
Retrieve SQL snippets
Check if the database is in read-only mode
Retrieve a database's SSL enforcement configuration
Retrieve a database's schema typescript types | +| `Database` | `Write` | Create a SQL query
Enable database webhooks on the project
Update the project's database configuration
Update a database's SSL enforcement configuration
Disable read-only mode for 15mins
Retrieve the pgbouncer configuration
Create a PITR backup for a database | +| `Domains` | `Read` | Retrieve the custom domains for a project
Retrieve the vanity subdomain configuration for a project | +| `Domains` | `Write` | Activate, initialize, reverify, or delete the custom domain for a project
Activate, delete or check the availability of a vanity subdomain for a project | +| `Edge Functions` | `Read` | Retrieve information about a project's edge functions | +| `Edge Functions` | `Write` | Create, update, or delete an edge function | +| `Environment` | `Read` | Retrieve branches in a project | +| `Environment` | `Write` | Create, update, or delete a branch | +| `Organizations` | `Read` | Retrieve an organization's metadata
Retrieve all members in an organization | +| `Organizations` | `Write` | Create an organization | +| `Projects` | `Read` | Retrieve a project's metadata
Check if a project's database is eligible for upgrade
Retrieve a project's network restrictions
Retrieve a project's network bans | +| `Projects` | `Write` | Create a project
Upgrade a project's database
Remove a project's network bans
Update a project's network restrictions | +| `Rest` | `Read` | Retrieve a project's PostgREST configuration | +| `Rest` | `Write` | Update a project's PostgREST configuration | +| `Secrets` | `Read` | Retrieve a project's API keys
Retrieve a project's secrets
Retrieve a project's pgsodium config | +| `Secrets` | `Write` | Create or update a project's secrets
Update a project's pgsodium configuration | export const Page = ({ children }) => diff --git a/apps/docs/pages/guides/platform/org-based-billing.mdx b/apps/docs/pages/guides/platform/org-based-billing.mdx index 24ea28e61e5..8842db98e5e 100644 --- a/apps/docs/pages/guides/platform/org-based-billing.mdx +++ b/apps/docs/pages/guides/platform/org-based-billing.mdx @@ -78,7 +78,7 @@ Under the old system, you had different quotas for each service. i.e. on the Pro Quotas and features are applied to your entire organization, independent of how many projects you launch within that organization. For billing purposes, we sum the usage across all projects in a monthly invoice. -Upgrading your organization to a paid plan means that you unlock the benefits of the paid plan for **all** projects within that organizatio - for example, no projects in your "Pro" organization will be paused. See [pricing page](https://supabase.com/pricing) for details on all plans. +Upgrading your organization to a paid plan means that you unlock the benefits of the paid plan for **all** projects within that organization - for example, no projects in your "Pro" organization will be paused. See [pricing page](https://supabase.com/pricing) for details on all plans. ### Usage Items @@ -143,7 +143,7 @@ Compute Credits do not apply to other usage fees like egress, database size, ... Additionally, Compute Credits reset every month and do not accumulate, in case you're not running any projects. -With Legacy Billing, you used to pay $25 for every single Pro plan project in an organization. Previously, we gave you a free “Starter” instance on paid plans - we're now giving you $10 in Compute Credits instead, to cover the first instance. You end up not paying extra for the first project inside your paid plan organisation - just like before. In case you add a Compute Add-On to your first project, you also end up paying exactly the same as before. +With Legacy Billing, you used to pay $25 for every single Pro plan project in an organization. Previously, we gave you a free “Starter” instance on paid plans - we're now giving you $10 in Compute Credits instead, to cover the first instance. You end up not paying extra for the first project inside your paid plan organization - just like before. In case you add a Compute Add-On to your first project, you also end up paying exactly the same as before. ## Legacy vs Organization-based Billing diff --git a/apps/docs/pages/guides/platform/performance.mdx b/apps/docs/pages/guides/platform/performance.mdx index 6eb1e9a66cc..9011c1ae4cd 100644 --- a/apps/docs/pages/guides/platform/performance.mdx +++ b/apps/docs/pages/guides/platform/performance.mdx @@ -91,7 +91,7 @@ order by max_time desc limit 100; ``` -This query will show you statistics about queries ordered by the maximum execution time. It is similar to the query above ordered by calls, but this one highlights outliers that may have high executions times. Queries which have high or mean execution times are good candidates for optimisation. +This query will show you statistics about queries ordered by the maximum execution time. It is similar to the query above ordered by calls, but this one highlights outliers that may have high executions times. Queries which have high or mean execution times are good candidates for optimization. #### Most time consuming queries: diff --git a/apps/docs/pages/guides/platform/permissions.mdx b/apps/docs/pages/guides/platform/permissions.mdx index 1efb9f3228c..726786d033a 100644 --- a/apps/docs/pages/guides/platform/permissions.mdx +++ b/apps/docs/pages/guides/platform/permissions.mdx @@ -10,8 +10,8 @@ The Supabase platform offers additional services (e.g. Storage) on top of the Po However, these services assume a base level of access to their data, in order to e.g. be able to run migrations over it. Breaking these assumptions runs the risk of rendering these services inoperational for your project: -- all entitites under the `storage` schema are owned by `supabase_storage_admin` -- all entitites under the `auth` schema are owned by `supabase_auth_admin` +- all entities under the `storage` schema are owned by `supabase_storage_admin` +- all entities under the `auth` schema are owned by `supabase_auth_admin` It is possible for violations of these assumptions to not cause an immediate outage, but take effect at a later time when a newer migration becomes available. diff --git a/apps/docs/pages/guides/platform/sso/gsuite.mdx b/apps/docs/pages/guides/platform/sso/gsuite.mdx index c52ad4866ef..146ad6038e6 100644 --- a/apps/docs/pages/guides/platform/sso/gsuite.mdx +++ b/apps/docs/pages/guides/platform/sso/gsuite.mdx @@ -41,7 +41,7 @@ It's very important to send this file to your support contact at Supabase to com ## Step 5: Add service provider details [#add-service-provider-details] -Fill out these serivce provider details on the next screen. +Fill out these service provider details on the next screen. | Detail | Value | | -------------- | --------------------------------------------------- | diff --git a/apps/docs/pages/guides/platform/troubleshooting.mdx b/apps/docs/pages/guides/platform/troubleshooting.mdx index 81cf8856d8e..755a63f0124 100644 --- a/apps/docs/pages/guides/platform/troubleshooting.mdx +++ b/apps/docs/pages/guides/platform/troubleshooting.mdx @@ -1,7 +1,7 @@ import Layout from '~/layouts/DefaultGuideLayout' export const meta = { - id: 'troubeshooting', + id: 'troubleshooting', title: 'Troubleshooting', description: 'Diagnosing and fixing issues with your hosted Supabase project.', }