docs: Fix typos in docs (#497)

docs/content/how-to/headless-ecommerce-store-with-gatsby-contentful-medusa.md

@@ -160,7 +160,7 @@ The migrations included in this project will create the following content types:
 - **Hero**: a component that can take a Title, CTA and a background image.
 - **Tile**: a component that can be added to a Tile Section and renders a Title, CTA and an Image.
 - **Tile Section**: a component that can hold a number of Tiles or Products. When used with a Product, the Tile Section will display the product thumbnail and it's title and will link to the product page.
-- **Link**: a component that can link to an external or internal path; or, alternatively, hold a reference to a Page or Product entry. If used with Page or Product, the link path will be infered from the referenced entry.
+- **Link**: a component that can link to an external or internal path; or, alternatively, hold a reference to a Page or Product entry. If used with Page or Product, the link path will be inferred from the referenced entry.
 - **Navigation Item**: an item to include in a Navigation Menu. Each navigation item has a title that can be displayed in a menu and a link that defines where the user will be navigated to when the item is clicked.
 - **Product**: represents a product as syncronized from Medusa. A product's variants will be copied over as well.
 - **Product Variant**: The variants of a product.

docs/content/how-to/setting-up-a-nextjs-storefront-for-your-medusa-project.md

@@ -4,7 +4,7 @@ title: Setting up a Next.js storefront for your Medusa project
 
 # Setting up a Next.js storefront for your Medusa project
 
-> Medusa is a headless open source commerce platform giving engineers the foundation for building unique and scaleable digital commerce projects through our API-first engine.
+> Medusa is a headless open source commerce platform giving engineers the foundation for building unique and scalable digital commerce projects through our API-first engine.
 > Being headless, our starters serve as a good foundation for you to get coupled with a frontend in a matter of minutes.
 
 This article assumes you already have the Medusa project created and ready to be linked to your Next.js starter.

docs/content/how-to/uploading-images-to-s3.md

@@ -45,7 +45,7 @@ Navigate to the IAM section of your AWS console and perform the following steps:
 - Add the existing **AmazonS3FullAccess** policy to the user
 - Submit the details
 
-Upon successfull creation of the user, you are presented with an **Access key ID** and a **Secret access key**. Note both of them down for later use.
+Upon successful creation of the user, you are presented with an **Access key ID** and a **Secret access key**. Note both of them down for later use.
 
 ### Installation
 

docs/content/tutorial/1-creating-your-medusa-server.md

@@ -85,7 +85,7 @@ In the API reference docs you can find all the available requests that are expos
 
 ### Setup Stripe as a payment provider (Guide coming soon)
 
-One of the first things you may want to do when building out your store would be to add a payment provider. Your starter project comes with a dummy payment provider that simply fakes payments being processed. In the real world you want a payment provider that can handle credit card information securely and make sure that funds are being transfered to your account. Stripe is one of the most popular payment providers and Medusa has an official plugin that you can easily install in your project.
+One of the first things you may want to do when building out your store would be to add a payment provider. Your starter project comes with a dummy payment provider that simply fakes payments being processed. In the real world you want a payment provider that can handle credit card information securely and make sure that funds are being transferred to your account. Stripe is one of the most popular payment providers and Medusa has an official plugin that you can easily install in your project.
 
 ## Summary
 

docs/content/tutorial/2-adding-custom-functionality.md

@@ -252,4 +252,4 @@ You have now learned how to add custom functionality to your Medusa server, whic
 
 You have now been introduced to many of the key parts of Medusa and with your knowledge of customization you can now begin creating some really powerful commerce experiences. If you have an idea for a cool customization go ahead and make it right now! If you are not completely ready yet you can browse the reference docs further.
 
-<!-- In the next part of this tutorial we will look into linking your local project with Medusa Cloud to make develpment smoother while leveraging the powerful management tools that merchants use to manage their Medusa store. -->
+<!-- In the next part of this tutorial we will look into linking your local project with Medusa Cloud to make development smoother while leveraging the powerful management tools that merchants use to manage their Medusa store. -->

docs/content/tutorial/3-linking-your-local-project-with-medusa-cloud.md

@@ -36,7 +36,7 @@ Once you have authenticated your CLI for your Medusa Cloud account you are ready
 medusa link --develop
 ```
 
-The `link` command will first check that you have authenticated your CLI which we did in the previous step. Then it will perform the local linking, which essentially adds an admin user in the local database specified in `medusa-config.js`. Finally, your browser will open Medusa Cloud to perform the linking there, which tells Medusa Cloud where your local server is running. On succesful linking in the browser you will see a confirmation page with a "Go to orders" button. If you click this button you will be taken to an overview of the orders made in your local project.
+The `link` command will first check that you have authenticated your CLI which we did in the previous step. Then it will perform the local linking, which essentially adds an admin user in the local database specified in `medusa-config.js`. Finally, your browser will open Medusa Cloud to perform the linking there, which tells Medusa Cloud where your local server is running. On successful linking in the browser you will see a confirmation page with a "Go to orders" button. If you click this button you will be taken to an overview of the orders made in your local project.
 
 You should note that the `--develop` flag is optional for the `link` command. If provided it tells the CLI to start up your server after linking is completed; you may leave it out if you'd rather start your server separately.
 

integration-tests/api/__tests__/admin/shipping-options.js

@@ -124,7 +124,7 @@ describe("/admin/shipping-options", () => {
       expect(res.data.message).toEqual("ID does not exist")
     })
 
-    it("it succesfully updates a set of existing requirements", async () => {
+    it("it successfully updates a set of existing requirements", async () => {
       const api = useApi()
 
       const payload = {
@@ -156,7 +156,7 @@ describe("/admin/shipping-options", () => {
       expect(res.status).toEqual(200)
     })
 
-    it("it succesfully updates a set of existing requirements by updating one and deleting the other", async () => {
+    it("it successfully updates a set of existing requirements by updating one and deleting the other", async () => {
       const api = useApi()
 
       const payload = {
@@ -182,7 +182,7 @@ describe("/admin/shipping-options", () => {
       expect(res.status).toEqual(200)
     })
 
-    it("succesfully updates a set of requirements because max. subtotal >= min. subtotal", async () => {
+    it("successfully updates a set of requirements because max. subtotal >= min. subtotal", async () => {
       const api = useApi()
 
       const payload = {

www/reference/src/components/search/hit-component.js

@@ -7,7 +7,7 @@ const HitComponent = ({ hit, children }) => {
   const { goTo, api } = useContext(NavigationContext)
   let { url, type, hierarchy } = hit
 
-  /** Get the API that is not currenty being viewed, so we can create
+  /** Get the API that is not currently being viewed, so we can create
    * an URL that goes to the other API.
    */
   const getOtherAPI = () => {