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

* docs: rename Architectural Modules to Infrastructure Modules

* generate again

www/apps/resources/app/recipes/b2b/page.mdx

@@ -18,7 +18,7 @@ Medusa has a ready-to-use B2B starter that you install and use in [this GitHub r
 
 In a B2B store, you provide different types of customers with relevant pricing, products, shopping experience, and more.
 
-Medusa’s commerce modules, including Sales Channel, Customer, and Pricing modules facilitate implementing this setup. Medusa’s architecture and extendible nature allow you to customize your store based on your use case.
+Medusa’s Commerce Modules, including Sales Channel, Customer, and Pricing modules facilitate implementing this setup. Medusa’s architecture and extendible nature allow you to customize your store based on your use case.
 
 <Note title="Related use-case">
 

www/apps/resources/app/recipes/commerce-automation/page.mdx

@@ -37,7 +37,7 @@ You can use the Notification Module to send notifications when an action is trig
 
 <Note title="Tip">
 
-The [Events reference](../../events-reference/page.mdx) shows an extensive list of events triggered for each commerce module.
+The [Events reference](../../events-reference/page.mdx) shows an extensive list of events triggered for each Commerce Module.
 
 </Note>
 
@@ -45,7 +45,7 @@ Medusa also provides Notification Module Providers that integrate with third-par
 
 <CardList items={[
   {
-    href: "/architectural-modules/notification",
+    href: "/infrastructure-modules/notification",
     title: "Notification Module",
     text: "Learn about the Notification Module.",
     icon: AcademicCapSolid,
@@ -94,7 +94,7 @@ To handle events within an order flow and automate actions, create a subscriber.
   {
     href: "/events-reference",
     title: "Events Reference",
-    text: "Check out triggered events by each commerce module.",
+    text: "Check out triggered events by each Commerce Module.",
     icon: AcademicCapSolid,
   },
 ]} />
@@ -132,7 +132,7 @@ Medusa's commerce features are geared towards automating RMA flows and ensuring
 
 Businesses use customer segmentation to organize customers into different groups and then apply different price rules to these groups.
 
-Medusa's commerce modules provide the necessary features to implement this use case:
+Medusa's Commerce Modules provide the necessary features to implement this use case:
 
 - The Customer Module provides a customer groups feature to organize customers into customer groups.
 - The Pricing Module provides the features to specify prices based on a condition, such as the group of the customer.
@@ -164,7 +164,7 @@ For example, to group customers with over twenty orders:
   {
     href: "/events-reference",
     title: "Events Reference",
-    text: "Check out triggered events by each commerce module.",
+    text: "Check out triggered events by each Commerce Module.",
     icon: AcademicCapSolid,
   },
 ]} />

www/apps/resources/app/recipes/commerce-automation/restock-notification/page.mdx

@@ -31,7 +31,7 @@ export const metadata = {
 
 In this guide, you'll learn how to notify customers when a variant is restocked in Medusa.
 
-When you install a Medusa application, you get a fully-fledged commerce platform with a Framework for customization. The Medusa application's commerce features are built around [commerce modules](../../../commerce-modules/page.mdx) which are available out-of-the-box. These features include managing the inventory of product variants in different stock locations and sales channels.
+When you install a Medusa application, you get a fully-fledged commerce platform with a Framework for customization. The Medusa application's commerce features are built around [Commerce Modules](../../../commerce-modules/page.mdx) which are available out-of-the-box. These features include managing the inventory of product variants in different stock locations and sales channels.
 
 Customers browsing your store may be interested in a product that is currently out of stock. To keep the customer interested in your store and encourage them to purchase the product in the future, you can build customizations around Medusa's commerce features to subscribe customers to receive a notification when the product is restocked.
 
@@ -1088,9 +1088,9 @@ The `useQueryGraphStep` is from Medusa's workflows. So, you'll only implement th
 
 ### Optional Prerequisite: Notification Module Provider
 
-Within this workflow, you'll use Medusa's [Notification Module](../../../architectural-modules/notification/page.mdx) to send an email to the customer.
+Within this workflow, you'll use Medusa's [Notification Module](../../../infrastructure-modules/notification/page.mdx) to send an email to the customer.
 
-The module delegates the email sending to a module provider, such as [SendGrid](../../../architectural-modules/notification/sendgrid/page.mdx) or [Resend](../../../integrations/guides/resend/page.mdx). You can refer to their linked guides to set up either module providers.
+The module delegates the email sending to a module provider, such as [SendGrid](../../../infrastructure-modules/notification/sendgrid/page.mdx) or [Resend](../../../integrations/guides/resend/page.mdx). You can refer to their linked guides to set up either module providers.
 
 Alternatively, for development and debugging purposes, you can use the default Notification Module Provider that only logs a message in the terminal instead of sending an email. To do that, add the following to the `modules` array in `medusa-config.ts`:
 

www/apps/resources/app/recipes/digital-products/examples/standard/page.mdx

@@ -258,7 +258,7 @@ So, you can't have relations between data models in modules. Instead, you define
 
 Links are relations between data models of different modules that maintain the isolation between the modules.
 
-In this step, you’ll define links between your module’s data models and data models from Medusa’s commerce modules:
+In this step, you’ll define links between your module’s data models and data models from Medusa’s Commerce Modules:
 
 1. Link between the `DigitalProduct` model and the Product Module's `ProductVariant` model.
 2. Link between the `DigitalProductOrder` model and the Order Module's `Order` model.
@@ -791,7 +791,7 @@ To upload the digital product media files, use Medusa’s File Module.
 
 <Note>
 
-Your Medusa application uses the local file module provider by default, which uploads files to a local directory. However, you can use other file module providers, such as the [S3 module provider](../../../../architectural-modules/file/s3/page.mdx).
+Your Medusa application uses the local file module provider by default, which uploads files to a local directory. However, you can use other file module providers, such as the [S3 module provider](../../../../infrastructure-modules/file/s3/page.mdx).
 
 </Note>
 

www/apps/resources/app/recipes/digital-products/page.mdx

@@ -26,7 +26,7 @@ During development, you can use the Local File Module Provider, which is install
 
 <CardList items={[
   {
-    href: "/architectural-modules/file",
+    href: "/infrastructure-modules/file",
     title: "File Module Providers",
     text: "Check out available file module providers.",
     icon: PuzzleSolid,

www/apps/resources/app/recipes/marketplace/page.mdx

@@ -52,7 +52,7 @@ You can create a marketplace module that implements data models for vendors, the
 
 ## Define Module Links
 
-Since a vendor has products, orders, and other models based on your use case, define module links between your module's data models and the commerce module's data models.
+Since a vendor has products, orders, and other models based on your use case, define module links between your module's data models and the Commerce Module's data models.
 
 For example, if you defined a vendor data model in a marketplace module, you can define a module link between the vendor and the Product Module's product data model.
 

www/apps/resources/app/recipes/oms/page.mdx

@@ -13,7 +13,7 @@ This recipe provides an overview of Medusa's features and how to use it as an Or
 
 Building or integrating an OMS brings certain challenges: accepting orders from different sales channels, tracking inventory across the sales channels, integrating third-party fulfillment and payment providers with the OMS, and more.
 
-Medusa's commerce modules and customization toolkit lets you integrate it within a larger ecosystem. The commerce modules provide features to allow businesses to accept orders from any sales channel, benefit from multi-warehouse inventory features, and integrate third-party services for fulfillment, payment, and more.
+Medusa's Commerce Modules and customization toolkit lets you integrate it within a larger ecosystem. The Commerce Modules provide features to allow businesses to accept orders from any sales channel, benefit from multi-warehouse inventory features, and integrate third-party services for fulfillment, payment, and more.
 
 <Note title="Related use-case">
 

www/apps/resources/app/recipes/subscriptions/examples/standard/page.mdx

@@ -306,7 +306,7 @@ So, you can't have relations between data models in modules. Instead, you define
 
 Links are relations between data models of different modules that maintain the isolation between the modules.
 
-In this step, you’ll define links between the Subscription Module’s `Subscription` data model and the data models of Medusa’s commerce modules:
+In this step, you’ll define links between the Subscription Module’s `Subscription` data model and the data models of Medusa’s Commerce Modules:
 
 1. Link between the `Subscription` data model and the Cart Module's `Cart` model.
 2. Link between the `Subscription` data model and the Customer Module's `Customer` model.