Merge branch 'master' into docs/development

docs/content/add-plugins/algolia.md

@@ -57,7 +57,7 @@ And that's all! You've now enabled Algolia for your Medusa store engine. The plu
 
 **Usage**
 
-This article will not go too much into depth about how the search functionality works under the hood when querying the API. We refer to the [previous article on MeiliSearch](https://www.medusajs.com/post/meilisearch-and-medusa) if this is of your interest. In there, you will find a quick showcase using Postman as well as a thorough walkthrough of how you can display the results in your storefront using ReactJS (GatsbyJS).
+This article will not go too much into depth about how the search functionality works under the hood when querying the API. We refer to the [previous article on MeiliSearch](https://medusajs.com/blog/meilisearch-medusa) if this is of your interest. In there, you will find a quick showcase using Postman as well as a thorough walkthrough of how you can display the results in your storefront using ReactJS (GatsbyJS).
 
 Instead, to illustrate the power of our Search API and search engine plugins, we'll switch out a MeiliSearch plugin with our new Algolia plugin in a store with existing products. Upon restarting the server with the new configuration, your products will automatically be fed into Algolia and the search functionality in your frontend will remain unchanged.
 

docs/content/add-plugins/sendgrid.mdx

@@ -297,7 +297,7 @@ You don’t have to create a template for every type in the reference. You can s
   ```
 </details>
 
-### Order Cancelled
+### Order Canceled
 
 **Key in plugin options:** `order_canceled_template`
 

docs/content/advanced/backend/endpoints/add-admin.md

@@ -24,7 +24,7 @@ export default () => {
 
   router.get("/admin/hello", (req, res) => {
     res.json({
-      message: "Welcome to Your Store!"
+      message: "Welcome to Your Store!",
     })
   })
 
@@ -61,8 +61,8 @@ Then, create an object that will hold the CORS configurations:
 
 ```js
 const corsOptions = {
-    origin: projectConfig.admin_cors.split(","),
-    credentials: true,
+  origin: projectConfig.admin_cors.split(","),
+  credentials: true,
 }
 ```
 
@@ -72,7 +72,7 @@ Finally, for each route you add, create an `OPTIONS` request:
 router.options("/admin/hello", cors(corsOptions))
 router.get("/admin/hello", (req, res) => {
   //...
-});
+})
 ```
 
 ## Multiple Endpoints
@@ -84,13 +84,13 @@ You can add more than one endpoints in `src/api/index.js`:
 ```js
 router.get("/admin/hello", (req, res) => {
   res.json({
-    message: "Welcome to Your Store!"
+    message: "Welcome to Your Store!",
   })
 })
 
 router.get("/admin/bye", (req, res) => {
   res.json({
-    message: "Come back again!"
+    message: "Come back again!",
   })
 })
 ```
@@ -105,7 +105,7 @@ To do that with the previous example, first, create the file `src/api/hello.js`
 export default (router) => {
   router.get("/admin/hello", (req, res) => {
     res.json({
-      message: "Welcome to Your Store!"
+      message: "Welcome to Your Store!",
     })
   })
 }
@@ -119,7 +119,7 @@ Next, create the file `src/api/bye.js` with the following content:
 export default (router) => {
   router.get("/admin/bye", (req, res) => {
     res.json({
-      message: "Come back again!"
+      message: "Come back again!",
     })
   })
 }
@@ -156,17 +156,15 @@ You can retrieve any registered service in your endpoint using `req.scope.resolv
 Here’s an example of an endpoint that retrieves the count of products in your store:
 
 ```js
-router.get('/admin/products/count', (req, res) => {
-    const productService = req.scope.resolve('productService')
+router.get("/admin/products/count", (req, res) => {
+  const productService = req.scope.resolve("productService")
 
-    productService
-      .count()
-      .then((count) => {
-        res.json({
-          count
-        })
-      })
+  productService.count().then((count) => {
+    res.json({
+      count,
+    })
   })
+})
 ```
 
 The `productService` has a `count` method that returns a Promise. This Promise resolves to the count of the products. You return a JSON of the product count.
@@ -178,13 +176,13 @@ Protected routes are routes that should be accessible by logged-in users only.
 To make a route protected, first, import the `authenticate` middleware:
 
 ```js
-import authenticate from '@medusajs/medusa/dist/api/middlewares/authenticate'
+import authenticate from "@medusajs/medusa/dist/api/middlewares/authenticate"
 ```
 
 Then, add the middleware to your route:
 
 ```js
-router.get('/store/products/count', authenticate(), (req, res) => {
+router.get("/store/products/count", authenticate(), (req, res) => {
   //...
 })
 ```

docs/content/advanced/backend/endpoints/add-storefront.md

@@ -24,7 +24,7 @@ export default () => {
 
   router.get("/store/hello", (req, res) => {
     res.json({
-      message: "Welcome to My Store!"
+      message: "Welcome to My Store!",
     })
   })
 
@@ -55,13 +55,13 @@ You can add more than one endpoints in `src/api/index.js`:
 ```js
 router.get("/store/hello", (req, res) => {
   res.json({
-    message: "Welcome to My Store!"
+    message: "Welcome to My Store!",
   })
 })
 
 router.get("/store/bye", (req, res) => {
   res.json({
-    message: "Come back again!"
+    message: "Come back again!",
   })
 })
 ```
@@ -76,7 +76,7 @@ To do that with the previous example, first, create the file `src/api/hello.js`
 export default (router) => {
   router.get("/store/hello", (req, res) => {
     res.json({
-      message: "Welcome to My Store!"
+      message: "Welcome to My Store!",
     })
   })
 }
@@ -90,7 +90,7 @@ Next, create the file `src/api/bye.js` with the following content:
 export default (router) => {
   router.get("/store/bye", (req, res) => {
     res.json({
-      message: "Come back again!"
+      message: "Come back again!",
     })
   })
 }
@@ -127,17 +127,15 @@ You can retrieve any registered service in your endpoint using `req.scope.resolv
 Here’s an example of an endpoint that retrieves the count of products in your store:
 
 ```js
-router.get('/store/products/count', (req, res) => {
-    const productService = req.scope.resolve('productService')
+router.get("/store/products/count", (req, res) => {
+  const productService = req.scope.resolve("productService")
 
-    productService
-      .count()
-      .then((count) => {
-        res.json({
-          count
-        })
-      })
+  productService.count().then((count) => {
+    res.json({
+      count,
+    })
   })
+})
 ```
 
 The `productService` has a `count` method that returns a Promise. This Promise resolves to the count of the products. You return a JSON of the product count.
@@ -149,13 +147,13 @@ Protected routes are routes that should be accessible by logged-in customers onl
 To make a route protected, first, import the `authenticate` middleware:
 
 ```js
-import authenticate from '@medusajs/medusa/dist/api/middlewares/authenticate'
+import authenticate from "@medusajs/medusa/dist/api/middlewares/authenticate"
 ```
 
 Then, add the middleware to your route:
 
 ```jsx
-router.get('/store/products/count', authenticate(), (req, res) => {
+router.get("/store/products/count", authenticate(), (req, res) => {
   //...
 })
 ```

docs/content/advanced/backend/migrations.md

@@ -0,0 +1,97 @@
+# Migrations
+
+In this document, you’ll learn about what Migrations are, their purpose, how you can run them, and how you can create your own Migrations.
+
+:::note
+
+Medusa’s Migrations do not work with SQLite databases. They are intended to be used with PostgreSQL databases, which is the recommended Database for your Medusa production server.
+
+:::
+
+## Overview
+
+Migrations are scripts that are used to make additions or changes to your database schema. In Medusa, they are essential for both when you first install your server and for subsequent server upgrades later on.
+
+When you first create your Medusa server, the database schema used must have all the tables necessary for the server to run.
+
+When a new Medusa version introduces changes to the database schema, you'll have to run migrations to apply them to your own database.
+
+:::tip
+
+Migrations are used to apply changes to the database schema. However, there are some version updates of Medusa that require updating the data in your database to fit the new schema. Those are specific to each version and you should check out the version under Upgrade Guides for details on the steps.
+
+:::
+
+## How to Run Migrations
+
+Migrations in Medusa can be done in one of two ways:
+
+### Migrate Command
+
+Using the Medusa CLI tool, you can run migrations with the following command:
+
+```bash
+medusa migrations run
+```
+
+This will check for any migrations that contain changes to your database schema that aren't applied yet and run them on your server.
+
+### Seed Command
+
+Seeding is the process of filling your database with data that is either essential or for testing and demo purposes. In Medusa, the `seed` command will run the migrations to your database if necessary before it seeds your database with dummy data.
+
+You can use the following command to seed your database:
+
+```bash npm2yarn
+npm run seed
+```
+
+This will use the underlying `seed` command provided by Medusa's CLI to seed your database with data from the file `data/seed.json` on your Medusa server.
+
+## How to Create Migrations
+
+In this section, you’ll learn how to create your own migrations using [Typeorm](https://typeorm.io). This will allow you to modify Medusa’s predefined tables or create your own tables.
+
+### Create Migration
+
+To create a migration that makes changes to your Medusa schema, run the following command:
+
+```bash
+npx typeorm migration:create -n src/path/to/UserChanged
+```
+
+:::tip
+
+The migration file should be inside the src directory to make sure it is built when the build command is run next.
+
+:::
+
+This will create the migration file in the path you specify. You can use this without the need to install Typeorm's CLI tool. You can then go ahead and make changes to it as necessary.
+
+:::tip
+
+You can learn more about writing migrations in [Typeorm’s Documentation](https://typeorm.io/migrations).
+
+:::
+
+### Build Files
+
+Before you can run the migrations you need to run the build command to transpile the TypeScript files to JavaScript files:
+
+```bash npm2yarn
+npm run build
+```
+
+### Run Migration
+
+The last step is to run the migration with the command detailed earlier
+
+```bash
+medusa migrations run
+```
+
+If you check your database now you should see that the change defined by the migration has been applied successfully.
+
+## What’s Next 🚀
+
+- Learn more about [setting up your development server](../../tutorial/0-set-up-your-development-environment.md).

docs/content/advanced/backend/payment/how-to-create-payment-provider.md

@@ -6,7 +6,7 @@ In this document, you’ll learn how to add a Payment Provider to your Medusa se
 
 A Payment Provider is the payment method used to authorize, capture, and refund payment, among other actions. An example of a Payment Provider is Stripe.
 
-By default, Medusa has a [manual payment provider](https://github.com/medusajs/medusa/tree/2e6622ec5d0ae19d1782e583e099000f0a93b051/packages/medusa-fulfillment-manual) that has minimal implementation. It can be synonymous with a Cash on Delivery payment method. It allows store operators to manage the payment themselves but still keep track of its different stages on Medusa.
+By default, Medusa has a [manual payment provider](https://github.com/medusajs/medusa/tree/master/packages/medusa-payment-manual) that has minimal implementation. It can be synonymous with a Cash on Delivery payment method. It allows store operators to manage the payment themselves but still keep track of its different stages on Medusa.
 
 Adding a Payment Provider is as simple as creating a [service](../services/create-service.md) file in `src/services`. A Payment Provider is essentially a service that extends `PaymentService` from `medusa-interfaces`.
 
@@ -42,9 +42,9 @@ These methods are used at different points in the Checkout flow as well as when
 
 ![Payment Flows.jpg](https://i.imgur.com/WeDr0ph.jpg)
 
-## Create a Fulfillment Provider
+## Create a Payment Provider
 
-The first step to create a fulfillment provider is to create a file in `src/services` with the following content:
+The first step to create a payment provider is to create a file in `src/services` with the following content:
 
 ```jsx
 import { PaymentService } from "medusa-interfaces"

docs/content/advanced/backend/services/create-service.md

@@ -1,7 +1,5 @@
 ---
-
 title: Create a Service
-
 ---
 
 # Create a Service
@@ -31,7 +29,7 @@ To create a service, you should create a JavaScript file in `src/services` to ho
 For example, if you want to create a service `helloService`, create the file `hello.js` in `src/services` with the following content:
 
 ```js
-import { BaseService } from "medusa-interfaces";
+import { BaseService } from "medusa-interfaces"
 
 class HelloService extends BaseService {
   getMessage() {
@@ -39,7 +37,7 @@ class HelloService extends BaseService {
   }
 }
 
-export default HelloService;
+export default HelloService
 ```
 
 ## Service Constructor
@@ -85,10 +83,10 @@ constructor({ helloService }) {
 To use your custom service in an endpoint, you can use `req.scope.resolve` passing it the service’s registration name:
 
 ```js
-const helloService = req.scope.resolve('helloService');
+const helloService = req.scope.resolve("helloService")
 
 res.json({
-  message: helloService.getMessage()
+  message: helloService.getMessage(),
 })
 ```
 

docs/content/advanced/backend/upgrade-guides/1-3-1.md

@@ -0,0 +1,51 @@
+# v1.3.1
+
+Version 1.3.1 of Medusa introduces new features including the addition of Line Item Adjustments and a more advanced Promotions API. The changes do not affect the public APIs and require only running necessary data migrations.
+
+## Prerequisites
+
+Both the actions required for this update need you to set the following environment variables:
+
+```bash
+TYPEORM_CONNECTION=postgres
+TYPEORM_URL=<DATABASE_URL>
+TYPEORM_LOGGING=true
+TYPEORM_ENTITIES=./node_modules/@medusajs/medusa/dist/models/*.js
+TYPEORM_MIGRATIONS=./node_modules/@medusajs/medusa/dist/migrations/*.js
+```
+
+These environment variables are used in the data migration scripts in this upgrade. Make sure to replace `<DATABASE_URL>` with your PostgreSQL database URL.
+
+## Line Item Adjustments
+
+This new version of Medusa allows store operators to adjust line items in an order or a swap which provides more customization capabilities.
+
+It introduces a new model `LineItemAdjustment` which gives more flexibility to adjust the pricing of line items in a cart, order, or swap. A discount can be added, removed, or modified and the price will reflect on the total calculation of the cart, order, or swap.
+
+This also introduces an optimization to the calculation of totals, as it is no longer necessary to calculate the discounts every time the totals are retrieved.
+
+### Actions Required
+
+This new version adds a new data migration script that will go through your list of existing orders and add line item adjustments for each of the line items in the order.
+
+For that reason, it’s essential to run the data migration script after upgrading your server and before starting your Medusa server:
+
+```bash
+node ./node_modules/@medusajs/medusa/dist/scripts/line-item-adjustment-migration.js
+```
+
+## Advanced Discount Conditions
+
+This new version of Medusa holds advanced promotions functionalities to provide store operators with even more customization capabilities when creating discounts. You can now add even more conditions to your discounts to make them specific for a set of products, collections, customer groups, and more.
+
+This change required creating a new model `DiscountCondition` which belongs to `DiscountRule` and includes a few relationships with other models to make the aforementioned feature possible.
+
+### Actions Required
+
+To ensure your old discount rules play well with the new Promotions API and schema, this version includes a migration script that will go through your existing discount rules, create discount conditions for these rules, and move the former direct relationship between discount rules and products to become between discount conditions and products.
+
+For that reason, it’s essential to run the data migration script after upgrading your server and before starting your Medusa server:
+
+```bash
+node ./node_modules/@medusajs/medusa/dist/scripts/discount-rule-migration.js
+```

docs/content/how-to/create-medusa-app.md

@@ -55,7 +55,7 @@ For the walkthrough purposes, we assume that the selected starter is `medusa-sta
 
 ### Selecting a Storefront
 
-After selecting your Medusa starter you will be given the option to install one of our storefront starters. At the moment we have starters for Gatsby and Next.js:
+After selecting your Medusa starter, you will be given the option to install one of our storefront starters. At the moment, we have starters for Gatsby and Next.js:
 
 ```bash
 Which storefront starter would you like to install? …
@@ -74,7 +74,7 @@ Creating new project from git: https://github.com/medusajs/medusa-starter-defaul
 Installing packages...
 ```
 
-Once the installation has been completed you will have a Medusa backend, a demo storefront, and an admin dashboard.
+Once the installation has been completed, you will have a Medusa backend, a Demo storefront, and an Admin dashboard.
 
 ## What's inside
 
@@ -87,7 +87,7 @@ Inside the root folder which was specified at the beginning of the installation
   /admin // Medusa admin panel 
 ```
 
-`create-medusa-app` prints out the commands that are available to you after installation. When each project is started you can visit your storefront, complete the order, and view the order in Medusa admin.
+`create-medusa-app` prints out the commands that are available to you after installation. When each project is started, you can visit your storefront, complete the order, and view the order in Medusa admin.
 
 ```bash
 ⠴ Installing packages...
@@ -112,10 +112,10 @@ Create initial git commit in my-medusa-store/admin
 
 ## **What's next?**
 
-To learn more about Medusa to go through our docs to get some inspiration and guidance for the next steps and further development:
+To learn more about Medusa, go through our docs to get some inspiration and guidance for the next steps and further development:
 
 - [Find out how to set up a Medusa project with Gatsby and Contentful](https://docs.medusajs.com/how-to/headless-ecommerce-store-with-gatsby-contentful-medusa)
 - [Move your Medusa setup to the next level with some custom functionality](https://docs.medusajs.com/tutorial/adding-custom-functionality)
 - [Create your own Medusa plugin](https://docs.medusajs.com/guides/plugins)
 
-If you have any follow-up questions or want to chat directly with our engineering team we are always happy to meet you at our [Discord](https://discord.gg/DSHySyMu).
+If you have any follow-up questions or want to chat directly with our engineering team, we are always happy to meet you at our [Discord](https://discord.gg/DSHySyMu).

docs/content/how-to/deploying-on-heroku.md

@@ -4,7 +4,7 @@ title: "Deploying on Heroku"
 
 # Deploying on Heroku
 
-This is a guide for deploying a Medusa project on Heroku. Heroku is at PaaS that allows you to easily deploy your applications in the cloud.
+This is a guide for deploying a Medusa project on Heroku. Heroku is a PaaS (Platform as a Service) that allows you to easily deploy your applications in the cloud.
 
 <div>
   <video width="100%" height="100%" playsinline autoplay muted controls>
@@ -57,7 +57,7 @@ Follow the instructions on your terminal
 
 ### 3. Create an app on Heroku
 
-In your **Medusa project directory** run the following commands to create an app on Heroku and add it as a remote origin.
+In your **Medusa project directory**, run the following commands to create an app on Heroku and add it as a remote origin.
 
 ```bash
 heroku create medusa-test-app
@@ -70,13 +70,13 @@ Medusa requires a Postgres database and a Redis instance to work. These are adde
 
 :::tip
 
-In this below example, we initialize the resources on free plans. This is not a valid configuration for a production environment.
+In this example below, we initialize the resources on free plans. This is not a valid configuration for a production environment.
 
 :::
 
 #### Postgresql
 
-Add a Postgres addon to your Heroku app
+Add a Postgres add-on to your Heroku app
 
 ```bash
 heroku addons:create heroku-postgresql:hobby-dev
@@ -90,7 +90,7 @@ Add a Redis instance to your Heroku app
 
 :::note
 
-The addon `redistogo:nano` is free, but Heroku requires you to add a payment method to proceed.
+The add-on `redistogo:nano` is free, but Heroku requires you to add a payment method to proceed.
 
 :::
 
@@ -102,7 +102,7 @@ You can find more informations, plans and pricing about Redis To Go [here](https
 
 ### 5. Configure environment variables on Heroku
 
-Medusa requires a set of environment variables. From you project repository run the following commands:.
+Medusa requires a set of environment variables. From you project repository, run the following commands:.
 
 ```bash
 heroku config:set NODE_ENV=production

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

@@ -15,7 +15,7 @@ This article assumes you already have the Medusa project created and ready to be
 
 ## Getting started
 
-In order to get started let's open the terminal and use the following command to create an instance of your storefront:
+In order to get started, let's open the terminal and use the following command to create an instance of your storefront:
 
 ```zsh
     npx create-next-app -e https://github.com/medusajs/nextjs-starter-medusa my-medusa-storefront
@@ -31,7 +31,7 @@ Let's jump to these two.
 
 For this part, we should navigate to a `client.js` file which you can find in the utils folder.
 
-We don't need to do much in here, but to make sure that our storefront is pointing to the port, where the server is running
+We don't need to do much in here, but to make sure that our storefront is pointing to the port where the server is running
 
 ```js
 import Medusa from "@medusajs/medusa-js"
@@ -39,13 +39,13 @@ const BACKEND_URL = process.env.GATSBY_STORE_URL || "http://localhost:9000" // <
 export const createClient = () => new Medusa({ baseUrl: BACKEND_URL })
 ```
 
-By default the Medusa server is running at port 9000, so if you didn't change that we are good to go to our next step.
+By default, the Medusa server is running at port 9000. So if you didn't change that, we are good to go to our next step.
 
 ## Update the `STORE_CORS` variable
 
 Here let's navigate to your Medusa server and open `medusa-config.js`
 
-Let's locate the `STORE_CORS` variable and make sure it's the right port (which is 3000 by default for Next.js projects)
+Let's locate the `STORE_CORS` variable and make sure it's the right port (which is 3000 by default for Next.js projects).
 
 ```js
 /*

docs/content/introduction.md

@@ -1,7 +1,5 @@
 ---
-
 title: Introduction
-
 ---
 
 ## Architecture overview
@@ -18,11 +16,11 @@ Your Medusa server will include all functionalities related to your store’s ch
 
 ### Admin Dashboard
 
-The admin dashboard is accessible by store operators. Store operators can use the admin dashboard to view, create, and modify data such as orders and products. 
+The admin dashboard is accessible by store operators. Store operators can use the admin dashboard to view, create, and modify data such as orders and products.
 
-Medusa provides a beautiful [admin dashboard](https://demo.medusajs.com) that you can use right off the bat. Our admin dashboard provides a lot of functionalities to manage your store including Order management, product management, user management and more.
+Medusa provides a beautiful [admin dashboard](https://demo.medusajs.com) that you can use right off the bat. Our admin dashboard provides a lot of functionalities to manage your store including Order management, Product management, User management and more.
 
- You can also create your own admin dashboard by utilizing the [Admin REST APIs](https://docs.medusajs.com/api/admin/auth).
+You can also create your own admin dashboard by utilizing the [Admin REST APIs](https://docs.medusajs.com/api/admin/auth).
 
 ### Storefront
 

docs/content/quickstart/quick-start.md

@@ -1,6 +1,12 @@
 # Quickstart
 
-This quickstart is intended for experienced developers, that are accustomed with concepts like JavaScript, Node.js, SQL and the command line. For a more gentle introduction, see our tutorial on [how to set up your development environment](/tutorial/set-up-your-development-environment).
+This document will guide you through setting up your Medusa server in a few minutes.
+
+:::tip
+
+For a more detailed guide on how to set up your local environment to work with Medusa, check out the documentation on [how to set up your development environment](/tutorial/set-up-your-development-environment).
+
+:::
 
 ## Prerequisites
 
@@ -29,33 +35,29 @@ You can install Node from the [official website](https://nodejs.org/en/).
 3. **Start your Medusa engine**
 
    ```bash
+   cd my-medusa-store
    medusa develop
    ```
 
-4. **Use the API**
+After these 3 steps and in only a couple of minutes, you now have a complete commerce engine running locally. You can test it out by sending a request using a tool like Postman or through the command line:
 
-   ```bash
-   curl localhost:9000/store/products | python -m json.tool
-   ```
+```bash
+curl localhost:9000/store/products | python -m json.tool
+```
 
-After these four steps and only a couple of minutes, you now have a complete commerce engine running locally. You may now explore [the documentation](https://docs.medusajs.com/api) to learn how to interact with the Medusa API. You may also add [plugins](https://github.com/medusajs/medusa/tree/master/packages) to your Medusa store by specifying them in your `medusa-config.js` file.
-We have a prebuilt admin dashboard that you can use to configure and manage your store find it here: [Medusa Admin](https://github.com/medusajs/admin)
+:::note
 
-## What's next?
+This command uses Python to format the result of the request better in your command line. If you don't want to use Python you can simply send a request without the formatting:
 
-### Set up a storefront for your Medusa project
-
-We have created two starters for you that can help you lay a foundation for your storefront. The starters work with your new server with minimal configuration simply clone the starters from here:
-
-- [Nextjs Starter](https://github.com/medusajs/nextjs-starter-medusa)
-- [Gatsby Starter](https://github.com/medusajs/gatsby-starter-medusa)
-
-:::tip
-
-Medusa runs on port 9000 by default and the storefront starters are both configured to run on port 8000. If you wish to run your storefront starter on another port you should update your CORS settings in your project's `medusa-config.js`.
+```bash
+curl localhost:9000/store/products
+```
 
 :::
 
-<!-- ### Link you local development to Medusa Cloud (Coming soon!)
+## What's next :rocket:
 
-With your project in local development you can link your Medusa instance to Medusa Cloud - this will allow you to manage your store, view orders and test out the amazing functionalities that you are building. [Get started here](https://docs.medusajs.com/tutorial/linking-your-local-project-with-medusa-cloud). -->
+- Install our [Next.js](http://localhost:3000/starters/nextjs-medusa-starter) or [Gatsby](http://localhost:3000/starters/gatsby-medusa-starter) storefronts to set up your ecommerce storefront quickly.
+- Install the [Medusa Admin](../admin/quickstart.md) to supercharge your ecommerce experience with easy access to configurations and features.
+- Check our the [API reference](https://docs.medusajs.com/api) to learn more about available endpoints available on your Medusa server.
+- Install [plugins](https://github.com/medusajs/medusa/tree/master/packages) for features like Payment, CMS, Notifications, among other features.

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

@@ -6,15 +6,15 @@ title: Creating your Medusa server
 
 ## Introduction
 
-With the required software installed on your computer you are ready to start working on your first Medusa project.
+With the required software installed on your computer, you are ready to start working on your first Medusa project.
 
-In this part of the tutorial we will setup the skeleton for a Medusa store and will be making the first requests to your Medusa server.
+In this part of the tutorial, we will setup the skeleton for a Medusa store and will be making the first requests to your Medusa server.
 
-Once you have completed this part of the tutorial you will have a powerful backend for digital commerce experiences. The server will be capable of handling orders, ensuring payments are going through, keeping basic product and customer data in sync, etc. You can use one of the frontend starters to quickly hook up your server to a presentation layer ([Gatsby](https://github.com/medusajs/gatsby-starter-medusa) or [Next](https://github.com/medusajs/nextjs-starter-medusa)).
+Once you have completed this part of the tutorial, you will have a powerful backend for digital commerce experiences. The server will be capable of handling orders, ensuring payments are going through, keeping basic product and customer data in sync, etc. You can use one of the frontend starters to quickly hook up your server to a presentation layer ([Gatsby](https://github.com/medusajs/gatsby-starter-medusa) or [Next](https://github.com/medusajs/nextjs-starter-medusa)).
 
 ## Setup a Medusa project
 
-With Medusa CLI installed it is very easy to setup a new Medusa project, with the `new` command. In your command line run:
+With Medusa CLI installed, it is very easy to setup a new Medusa project, with the `new` command. In your command line run:
 
 ```shell
 medusa new my-medusa-server --seed
@@ -28,7 +28,7 @@ The command will do a number of things:
 - create a database in postgres with the name my-medusa-server
 - the `--seed` flag indicates that the database should be populated with some test data after the project has been set up
 
-If you navigate to the root folder of your new project you will see the following files in your directory:
+If you navigate to the root folder of your new project, you will see the following files in your directory:
 
 ```
 .
@@ -43,11 +43,11 @@ If you navigate to the root folder of your new project you will see the followin
 └── package.json
 ```
 
-There is not a lot of files needed to get your Medusa store setup and this is all due to the fact that the main Medusa core (`@medusajs/medusa`) is installed as a dependency in your project giving you all the fundamental needs for a digital commerce experience.
+There is not a lot of files needed to get your Medusa store setup and this is all due to the fact that the main Medusa core (`@medusajs/medusa`) is installed as a dependency in your project, giving you all the fundamental needs for a digital commerce experience.
 
 Much of Medusa's power lies in the `medusa-config.js` which is the file that configures your store and orchestrates the plugins that you wish to use together with your store. There are some different types of plugin categories such as payment plugins, notification plugins and fulfillment plugins, but plugins can contain any form of extension that enhances your store.
 
-For customizations that are more particular to your project you can extend your Medusa server by adding files in the `api` and `services` directories. More about customizing your server will follow in the following parts.
+For customizations that are more particular to your project, you can extend your Medusa server by adding files in the `api` and `services` directories. More about customizing your server will follow in the following parts.
 
 ## Starting your Medusa server
 
@@ -64,7 +64,7 @@ cd my-medusa-server
 medusa develop
 ```
 
-If you ran the new command with the `--seed` flag you will already have products available in your store. To view these you can run the following command in your command line:
+If you ran the new command with the `--seed` flag, you will already have products available in your store. To view these, you can run the following command in your command line:
 
 ```shell
 curl -X GET localhost:9000/store/products | python -m json.tool
@@ -78,19 +78,19 @@ Other options you could take are:
 
 ### Add a frontend to your server
 
-We have created two starters for you that can help you lay a foundation for your storefront. The starters work with your new server with minimal configuration simply clone the starters from here:
+We have created two starters for you that can help you lay a foundation for your storefront. The starters work with your new server with minimal configuration, simply clone the starters from here:
 
 - [Nextjs Starter](https://github.com/medusajs/nextjs-starter-medusa)
 - [Gatsby Starter](https://github.com/medusajs/gatsby-starter-medusa)
 
 ### Browse the API reference
 
-In the API reference docs you can find all the available requests that are exposed by your new Medusa server. Interacting with the API is the first step to creating truly unique experiences.
+In the API reference docs, you can find all the available requests that are exposed by your new Medusa server. Interacting with the API is the first step to creating truly unique experiences.
 
 ### 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 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.
+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
 
-In this part of the tutorial we have setup your first Medusa project using the `medusa new` command. You have now reached a key milestone as you are ready to start building your Medusa store; from here there are no limits to how you can use Medusa as you can customize and extend the functionality of the core. In the next part of the tutorial we will be exploring how you can add custom services and endpoints to fit your exact needs.
+In this part of the tutorial, we have setup your first Medusa project using the `medusa new` command. You have now reached a key milestone as you are ready to start building your Medusa store; from here there are no limits to how you can use Medusa, as you can customize and extend the functionality of the core. In the next part of the tutorial, we will be exploring how you can add custom services and endpoints to fit your exact needs.