From a8f06a49d78c88c77c00651f2f24fb44197f7640 Mon Sep 17 00:00:00 2001
From: ps-89 <91064940+ps-89@users.noreply.github.com>
Date: Wed, 22 Sep 2021 22:07:50 +0530
Subject: [PATCH] Fix typo in Plugins in Medusa doc (#414)

---
 docs/content/how-to/plugins.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/content/how-to/plugins.md b/docs/content/how-to/plugins.md
index 83dd41d30c..8d8c837123 100644
--- a/docs/content/how-to/plugins.md
+++ b/docs/content/how-to/plugins.md
@@ -10,7 +10,7 @@ The purpose of this guide is to give an introduction to the structure of a plugi
 
 Plugins offer a way to extend and integrate the core functionality of Medusa.
 
-In most commerce solutions, you can extend the basic features but it often comes with the expense of having to build standalone web applications. Our architecture is built such that plugins run within the same process as the core eliminating the need for extra server capacaity, infrastructure and maintenance. As a result, the plugins can use all other services as dependencies and access the database.
+In most commerce solutions, you can extend the basic features but it often comes with the expense of having to build standalone web applications. Our architecture is built such that plugins run within the same process as the core eliminating the need for extra server capacity, infrastructure and maintenance. As a result, the plugins can use all other services as dependencies and access the database.
 
 > You will notice that plugins vary in naming. The name should signal what functionality they provide.