From 47420bafff446900a537cec107c1f6eadf642dc7 Mon Sep 17 00:00:00 2001 From: Isaiah Hamilton <70828596+Isaiah-Hamilton@users.noreply.github.com> Date: Sun, 31 Oct 2021 23:16:26 -0400 Subject: [PATCH] docs: fix typos (#3715) * procedure numbers fix * fix(typo): fix typos for Docs * fix(typo): fix typos for Docs * Update row-level-security.mdx * Update plv8.mdx --- about/docs/careers/data-engineers.mdx | 4 ++-- web/docs/company/privacy.md | 12 ++++++------ web/docs/going-into-prod.mdx | 2 +- web/docs/guides/auth/auth-google.mdx | 4 ++-- web/docs/guides/auth/row-level-security.mdx | 2 +- web/docs/guides/client-libraries.mdx | 2 +- web/docs/guides/database/full-text-search.mdx | 4 ++-- web/docs/guides/database/intro.mdx | 2 +- web/docs/guides/database/json.mdx | 14 +++++++------- web/docs/guides/database/managing-timezones.mdx | 2 +- web/docs/guides/with-angular.mdx | 4 ++-- 11 files changed, 26 insertions(+), 26 deletions(-) diff --git a/about/docs/careers/data-engineers.mdx b/about/docs/careers/data-engineers.mdx index f80603924f6..93930089f6c 100644 --- a/about/docs/careers/data-engineers.mdx +++ b/about/docs/careers/data-engineers.mdx @@ -16,8 +16,8 @@ import Process from '@site/docs/careers/snippets/process.mdx' - Be the business intelligence star player at Supabase by helping dig deep into the data we are generating. Deep knowledge of SQL and relevant tooling is a must. - Help customer success & sales team by working to identify and monitor: - Usage Insights - - Find and segment cohorts based around account level data, behaviour, traffic sources, and measure their subsequent behaviours - - Find and monitor product qualified leads based around account and behaviour characteristics + - Find and segment cohorts based around account level data, behavior, traffic sources, and measure their subsequent behaviours + - Find and monitor product qualified leads based around account and behavior characteristics - Customer health segmentation into actionable cohorts (e.g. healthy, churn, at risk) - Help identify opportunities high touch, low touch, & tech touch customer success & sales approaches - Help sales & customer success identify opportunity for unscheduled outreach diff --git a/web/docs/company/privacy.md b/web/docs/company/privacy.md index 8768b645610..308381bef3b 100644 --- a/web/docs/company/privacy.md +++ b/web/docs/company/privacy.md @@ -164,15 +164,15 @@ The criteria used to determine the period for which personal information about y 4. **Legal Obligation.** Where we are processing personal information based on a legal obligation, we generally will retain the information for the period of time necessary to fulfill the legal obligation. 5. **Legal Claim.** We may need to apply a "legal hold" that retains information beyond our typical retention period where we face threat of legal claim.  In that case, we will retain the information until the hold is removed, which typically means the claim or threat of claim has been resolved. -In all cases, in addition to the purposes and legal bases, we consider the amount, nature and sensitivity of the personal information, as well as the potential risk of harm from unauthorised use or disclosure of your personal information. +In all cases, in addition to the purposes and legal bases, we consider the amount, nature and sensitivity of the personal information, as well as the potential risk of harm from unauthorized use or disclosure of your personal information. ### 4. Recipients of Personal Information In addition to the recipients listed in Annexes 1 and 2, we may also share your personal information with the following (as required in accordance with the uses set out in Annexes 1 and 2): 1. **Service providers and advisors**: we may share your personal information with third party vendors and other service providers that perform services for us or on our behalf, which may include providing professional services, such as legal and accounting services, mailing, email or chat services, fraud prevention, web hosting, or providing analytic services. -2. **Affiliates**. Other companies owned by or under common ownership as Supabase, including our subsidiaries (i.e., any organisation we own or control) and our ultimate holding company (i.e., any organisation that owns or controls us) and any subsidiaries it owns. These companies will use your personal information in the same way as we can under these Privacy Disclosures. -3. **Purchasers and third parties in connection with a business transaction**: your personal information may be disclosed to third parties in connection with a transaction, such as a merger, sale of assets or shares, reorganisation, financing, change of control or acquisition of all or a portion of our business. +2. **Affiliates**. Other companies owned by or under common ownership as Supabase, including our subsidiaries (i.e., any organization we own or control) and our ultimate holding company (i.e., any organization that owns or controls us) and any subsidiaries it owns. These companies will use your personal information in the same way as we can under these Privacy Disclosures. +3. **Purchasers and third parties in connection with a business transaction**: your personal information may be disclosed to third parties in connection with a transaction, such as a merger, sale of assets or shares, reorganization, financing, change of control or acquisition of all or a portion of our business. 4. **Law enforcement, regulators and other parties for legal reasons**: we may share your personal information with third parties as required by law or if we reasonably believe that such action is necessary to (i) comply with the law and the reasonable requests of law enforcement; (ii) detect and investigate illegal activities and breaches of agreements, including our Terms; and/or (iii) exercise or protect the rights, property, or personal safety of Supabase, its users or others. ### 5. Marketing and Advertising @@ -183,11 +183,11 @@ We will only send you marketing messages if you have given us your consent to do ### 6. Storing and transferring your personal information -**Security**. We implement appropriate technical and organisational measures to protect your personal information against accidental or unlawful destruction, loss, change or damage. All personal information we collect will be stored by our cloud hosting provider on secure servers. We will never send you unsolicited emails or contact you by phone requesting credit or debit card information or national identification numbers. +**Security**. We implement appropriate technical and organizational measures to protect your personal information against accidental or unlawful destruction, loss, change or damage. All personal information we collect will be stored by our cloud hosting provider on secure servers. We will never send you unsolicited emails or contact you by phone requesting credit or debit card information or national identification numbers. **International Transfers of your Personal Information**. The personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in where we and our third party service providers have operations. If you are located in the EEA, United Kingdom or Switzerland, your personal information may be processed outside of those regions, including in the United States. -In the event of such a transfer, we ensure that: (i) the personal information is transferred to countries recognised as offering an equivalent level of protection; or (ii) the transfer is made pursuant to appropriate safeguards, such as standard data protection clauses adopted by the European Commission. +In the event of such a transfer, we ensure that: (i) the personal information is transferred to countries recognized as offering an equivalent level of protection; or (ii) the transfer is made pursuant to appropriate safeguards, such as standard data protection clauses adopted by the European Commission. If you wish to enquire further about these safeguards used, please contact us using the details set out at the end of these Privacy Disclosures. @@ -222,7 +222,7 @@ Due to the confidential nature of data processing we may ask you to provide proo Our European Services uses cookies and similar technologies such as pixels and Local Storage Objects (LSOs) like HTML5 (together "**_cookies_**") to distinguish you from other users of our European Services. This helps us to provide you with a good experience when you browse our European Services and also allows us to monitor and analyse how you use and interact with our European Services so that we can continue to improve our European Services. -Cookies are pieces of code that allow for personalisation of our European Services experience by saving your information such as user ID and other preferences. A cookie is a small data file that we transfer to your computer's hard disk for record-keeping purposes. +Cookies are pieces of code that allow for personalization of our European Services experience by saving your information such as user ID and other preferences. A cookie is a small data file that we transfer to your computer's hard disk for record-keeping purposes. We use the following types of cookies: diff --git a/web/docs/going-into-prod.mdx b/web/docs/going-into-prod.mdx index 9ee933d0012..74533325aba 100644 --- a/web/docs/going-into-prod.mdx +++ b/web/docs/going-into-prod.mdx @@ -1,7 +1,7 @@ --- id: going-into-prod title: Going into Prod Checklist -description: 'Things to do before making your app publicaly available' +description: 'Things to do before making your app publicly available' --- After developing your project, and deciding it's time to Go Live With Real Users, you should run through this checklist to ensure that your project is: diff --git a/web/docs/guides/auth/auth-google.mdx b/web/docs/guides/auth/auth-google.mdx index 481cd653cce..514df8a9562 100644 --- a/web/docs/guides/auth/auth-google.mdx +++ b/web/docs/guides/auth/auth-google.mdx @@ -71,8 +71,8 @@ The next step requires a callback URL, which looks like this: - Click `Create Credentials` near the top then select `OAuth client ID` - On the `Create OAuth client ID` page, select your application type. If you're not sure, choose `Web application`. - Fill in your app name. -- At the bottom, under `Authorised redirect URIs` click `Add URI`. -- Enter your callback URI under `Authorised redirect URIs` at the bottom. +- At the bottom, under `Authorized redirect URIs` click `Add URI`. +- Enter your callback URI under `Authorized redirect URIs` at the bottom. - Enter your callback URI in the `Valid OAuth Redirect URIs` box. - Click `Save Changes` at the bottom right. - Click `Create`. diff --git a/web/docs/guides/auth/row-level-security.mdx b/web/docs/guides/auth/row-level-security.mdx index 12ec835ad4d..bc428c0f720 100644 --- a/web/docs/guides/auth/row-level-security.mdx +++ b/web/docs/guides/auth/row-level-security.mdx @@ -46,7 +46,7 @@ Returns the role of the user making the request. In most cases this is either `a ### `auth.email()` -Retuns the email of the user making the request. +Returns the email of the user making the request. ## Examples diff --git a/web/docs/guides/client-libraries.mdx b/web/docs/guides/client-libraries.mdx index 1b19dd32ce5..698b487486b 100755 --- a/web/docs/guides/client-libraries.mdx +++ b/web/docs/guides/client-libraries.mdx @@ -370,7 +370,7 @@ const { data, error } = await supabase ```py data = supabase.table('cities').insert({'name': 'Gotham', 'country_id': 556 }).execute() -# assert if insert resonse is a success +# assert if insert response is a success assert data.get("status_code") in (200, 201) # bulk insert diff --git a/web/docs/guides/database/full-text-search.mdx b/web/docs/guides/database/full-text-search.mdx index 6cc8f88cd05..a59a1a09967 100644 --- a/web/docs/guides/database/full-text-search.mdx +++ b/web/docs/guides/database/full-text-search.mdx @@ -39,7 +39,7 @@ values ('The Poky Little Puppy','Janette Sebring Lowrey','Puppy is slower than other, bigger animals.'), ('The Tale of Peter Rabbit','Beatrix Potter','Rabbit eats some vegetables.'), ('Tootle','Gertrude Crampton','Little toy train has big dreams.'), - ('Green Eggs and Ham','Dr. Seuss','Sam has changing food preferences and eats unusally colored food.'), + ('Green Eggs and Ham','Dr. Seuss','Sam has changing food preferences and eats unusually colored food.'), ('Harry Potter and the Goblet of Fire','J.K. Rowling','Fourth year of school starts, big drama ensues.'); ``` @@ -51,7 +51,7 @@ values | 1 | The Poky Little Puppy | Janette Sebring Lowrey | Puppy is slower than other, bigger animals. | | 2 | The Tale of Peter Rabbit | Beatrix Potter | Rabbit eats some vegetables. | | 3 | Tootle | Gertrude Crampton | Little toy train has big dreams. | -| 4 | Green Eggs and Ham | Dr. Seuss | Sam has changing food preferences and eats unusally colored food. | +| 4 | Green Eggs and Ham | Dr. Seuss | Sam has changing food preferences and eats unusually colored food. | | 5 | Harry Potter and the Goblet of Fire | J.K. Rowling | Fourth year of school starts, big drama ensues. | diff --git a/web/docs/guides/database/intro.mdx b/web/docs/guides/database/intro.mdx index e505b948326..67f0d5486fd 100644 --- a/web/docs/guides/database/intro.mdx +++ b/web/docs/guides/database/intro.mdx @@ -20,7 +20,7 @@ This package included a query language called "PostQUEL". In 1994, Postgres95 was built on top of POSTGRES code, adding an SQL language interpreter as a replacement for PostQUEL. Eventually, Postgres95 was renamed to PostgreSQL to reflect the SQL query capability. -After this, many people refered to it as Postgres since it's less prone to confusion. Supabase is all about +After this, many people refereed to it as Postgres since it's less prone to confusion. Supabase is all about simplicity, so we also refer to it as Postgres.