docs: rename Architectural Modules to Infrastructure Modules (#12212)

* docs: rename Architectural Modules to Infrastructure Modules * generate again
2025-04-17 13:20:43 +03:00
parent 8618e6ee38
commit eb73bdb478
149 changed files with 12165 additions and 12145 deletions
@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the API Key Module and other commerce modules.
+This document showcases the module links defined between the API Key Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/developer) to learn

 </Note>

-Medusa has API-key related features available out-of-the-box through the API Key Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this API Key Module.
+Medusa has API-key related features available out-of-the-box through the API Key Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this API Key Module.

 <Note>

@@ -33,7 +33,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the API Key Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -8,7 +8,7 @@ export const metadata = {

 In this section of the documentation, you will find resources to learn more about the Auth Module and how to use it in your application.

-Medusa has auth related features available out-of-the-box through the Auth Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Auth Module.
+Medusa has auth related features available out-of-the-box through the Auth Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Auth Module.

 <Note>

@@ -27,7 +27,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Auth Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -28,7 +28,7 @@ You'll create a subscriber that listens to the event. When the event is emitted,
  items={[
    {
      text: "A notification provider module, such as SendGrid",
-      link: "/architectural-modules/notification/sendgrid"
+      link: "/infrastructure-modules/notification/sendgrid"
    }
  ]}
 />
@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Cart Module and other commerce modules.
+This document showcases the module links defined between the Cart Module and other Commerce Modules.

 ## Summary

@@ -8,7 +8,7 @@ export const metadata = {

 In this section of the documentation, you will find resources to learn more about the Cart Module and how to use it in your application.

-Medusa has cart related features available out-of-the-box through the Cart Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Cart Module.
+Medusa has cart related features available out-of-the-box through the Cart Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Cart Module.

 <Note>

@@ -21,13 +21,13 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f
 - [Cart Management](./concepts/page.mdx): Store and manage carts, including their addresses, line items, shipping methods, and more.
 - [Apply Promotion Adjustments](./promotions/page.mdx): Apply promotions or discounts to line items and shipping methods by adding adjustment lines that are factored into their subtotals.
 - [Apply Tax Lines](./tax-lines/page.mdx): Apply tax lines to line items and shipping methods.
- [Cart Scoping](./links-to-other-modules/page.mdx): When used in the Medusa application, Medusa creates links to other commerce modules, scoping a cart to a sales channel, region, and a customer.
+- [Cart Scoping](./links-to-other-modules/page.mdx): When used in the Medusa application, Medusa creates links to other Commerce Modules, scoping a cart to a sales channel, region, and a customer.

 ---

 ## How to Use the Cart Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Currency Module and other commerce modules.
+This document showcases the module links defined between the Currency Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/store) to learn how

 </Note>

-Medusa has currency related features available out-of-the-box through the Currency Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Currency Module.
+Medusa has currency related features available out-of-the-box through the Currency Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Currency Module.

 <Note>

@@ -25,13 +25,13 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f
 ## Currency Features

 - [Currency Management and Retrieval](/references/currency/listAndCountCurrencies): This module adds all common currencies to your application and allows you to retrieve them.
- [Support Currencies in Modules](./links-to-other-modules/page.mdx): Other commerce modules use currency codes in their data models or operations. Use the Currency Module to retrieve a currency code and its details.
+- [Support Currencies in Modules](./links-to-other-modules/page.mdx): Other Commerce Modules use currency codes in their data models or operations. Use the Currency Module to retrieve a currency code and its details.

 ---

 ## How to Use the Currency Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Customer Module and other commerce modules.
+This document showcases the module links defined between the Customer Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/customers) to learn how to m

 </Note>

-Medusa has customer related features available out-of-the-box through the Customer Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Customer Module.
+Medusa has customer related features available out-of-the-box through the Customer Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Customer Module.

 <Note>

@@ -31,7 +31,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Customer Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Fulfillment Module and other commerce modules.
+This document showcases the module links defined between the Fulfillment Module and other Commerce Modules.

 ## Summary

@@ -17,7 +17,7 @@ Refer to the Medusa Admin User Guide to learn how to use the dashboard to:

 </Note>

-Medusa has fulfillment related features available out-of-the-box through the Fulfillment Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Fulfillment Module.
+Medusa has fulfillment related features available out-of-the-box through the Fulfillment Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Fulfillment Module.

 <Note>

@@ -36,7 +36,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Fulfillment Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Inventory Module and other commerce modules.
+This document showcases the module links defined between the Inventory Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/inventory) to learn how to m

 </Note>

-Medusa has inventory related features available out-of-the-box through the Inventory Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Inventory Module.
+Medusa has inventory related features available out-of-the-box through the Inventory Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Inventory Module.

 <Note>

@@ -34,7 +34,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Inventory Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Order Module and other commerce modules.
+This document showcases the module links defined between the Order Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/orders) to learn how to mana

 </Note>

-Medusa has order related features available out-of-the-box through the Order Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Order Module.
+Medusa has order related features available out-of-the-box through the Order Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Order Module.

 <Note>

@@ -34,7 +34,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Order Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,11 +6,11 @@ export const metadata = {

 # {metadata.title}

-In this section of the documentation, you'll find guides and references related to Medusa's commerce modules.
+In this section of the documentation, you'll find guides and references related to Medusa's Commerce Modules.

-A commerce module provides features for a commerce domain within its service. The Medusa application exposes these features in its API routes to clients.
+A Commerce Module provides features for a commerce domain within its service. The Medusa application exposes these features in its API routes to clients.

-A commerce module also defines data models, representing tables in the database. The Medusa Framework and tools allow you to extend these data models to add custom fields.
+A Commerce Module also defines data models, representing tables in the database. The Medusa Framework and tools allow you to extend these data models to add custom fields.

 ## Commerce Modules List

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Payment Module and other commerce modules.
+This document showcases the module links defined between the Payment Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/orders/payments) to learn ho

 </Note>

-Medusa has payment related features available out-of-the-box through the Payment Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Payment Module.
+Medusa has payment related features available out-of-the-box through the Payment Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Payment Module.

 <Note>

@@ -34,7 +34,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Payment Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Pricing Module and other commerce modules.
+This document showcases the module links defined between the Pricing Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/price-lists) to learn how to

 </Note>

-Medusa has pricing related features available out-of-the-box through the Pricing Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Pricing Module.
+Medusa has pricing related features available out-of-the-box through the Pricing Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Pricing Module.

 <Note>

@@ -34,7 +34,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Pricing Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Product Module and other commerce modules.
+This document showcases the module links defined between the Product Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/products) to learn how to ma

 </Note>

-Medusa has product related features available out-of-the-box through the Product Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Product Module.
+Medusa has product related features available out-of-the-box through the Product Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Product Module.

 <Note>

@@ -32,7 +32,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Product Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Promotion Module and other commerce modules.
+This document showcases the module links defined between the Promotion Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/promotions) to learn how to

 </Note>

-Medusa has promotion related features available out-of-the-box through the Promotion Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Promotion Module.
+Medusa has promotion related features available out-of-the-box through the Promotion Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Promotion Module.

 <Note>

@@ -33,7 +33,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use the Promotion Module

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Region Module and other commerce modules.
+This document showcases the module links defined between the Region Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/regions) to learn h

 </Note>

-Medusa has region related features available out-of-the-box through the Region Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Region Module.
+Medusa has region related features available out-of-the-box through the Region Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Region Module.

 <Note>

@@ -34,7 +34,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use Region Module's Service

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Sales Channel Module and other commerce modules.
+This document showcases the module links defined between the Sales Channel Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/sales-channels) to

 </Note>

-Medusa has sales channel related features available out-of-the-box through the Sales Channel Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Sales Channel Module.
+Medusa has sales channel related features available out-of-the-box through the Sales Channel Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Sales Channel Module.

 <Note>

@@ -45,7 +45,7 @@ Some use case examples for using a sales channel:

 ## How to Use Sales Channel Module's Service

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Stock Location Module and other commerce modules.
+This document showcases the module links defined between the Stock Location Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/locations-and-shipp

 </Note>

-Medusa has stock location related features available out-of-the-box through the Stock Location Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Stock Location Module.
+Medusa has stock location related features available out-of-the-box through the Stock Location Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Stock Location Module.

 <Note>

@@ -31,7 +31,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use Stock Location Module's Service

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -6,7 +6,7 @@ export const metadata = {

 # {metadata.title}

-This document showcases the module links defined between the Store Module and other commerce modules.
+This document showcases the module links defined between the Store Module and other Commerce Modules.

 ## Summary

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/store) to learn how

 </Note>

-Medusa has store related features available out-of-the-box through the Store Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Store Module.
+Medusa has store related features available out-of-the-box through the Store Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Store Module.

 <Note>

@@ -31,7 +31,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use Store Module's Service

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/tax-regions) to lea

 </Note>

-Medusa has tax related features available out-of-the-box through the Tax Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this Tax Module.
+Medusa has tax related features available out-of-the-box through the Tax Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this Tax Module.

 <Note>

@@ -32,7 +32,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use Tax Module's Service

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.

@@ -14,7 +14,7 @@ Refer to the [Medusa Admin User Guide](!user-guide!/settings/users) to learn how

 </Note>

-Medusa has user related features available out-of-the-box through the User Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in commerce modules, such as this User Module.
+Medusa has user related features available out-of-the-box through the User Module. A [module](!docs!/learn/fundamentals/modules) is a standalone package that provides features for a single domain. Each of Medusa's commerce features are placed in Commerce Modules, such as this User Module.

 <Note>

@@ -31,7 +31,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f

 ## How to Use User Module's Service

-In your Medusa application, you build flows around commerce modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 
+In your Medusa application, you build flows around Commerce Modules. A flow is built as a [Workflow](!docs!/learn/fundamentals/workflows), which is a special function composed of a series of steps that guarantees data consistency and reliable roll-back mechanism. 

 You can build custom workflows and steps. You can also re-use Medusa's workflows and steps, which are provided by the `@medusajs/medusa/core-flows` package.