docs: rename provider module to module provider (#7869)

* docs: rename provider module to module provider

* fix vale rule

* vale fixes

www/apps/resources/app/architectural-modules/file/local/page.mdx

@@ -1,12 +1,12 @@
 import { Table } from "docs-ui"
 
 export const metadata = {
-  title: `Local File Provider Module`,
+  title: `Local File Module Provider`,
 }
 
 # {metadata.title}
 
-The Local File Provider Module stores files uploaded to your Medusa application in the `/uploads` directory.
+The Local File Module Provider stores files uploaded to your Medusa application in the `/uploads` directory.
 
 ---
 
@@ -18,7 +18,7 @@ The Local File Module is installed by default in your application.
 
 </Note>
 
-To install the Local File Provider Module, run the following command in the directory of your Medusa application:
+To install the Local File Module Provider, run the following command in the directory of your Medusa application:
 
 ```bash npm2yarn
 npm install @medusajs/file-local-next

www/apps/resources/app/architectural-modules/file/page.mdx

@@ -1,7 +1,7 @@
 import { ChildDocs } from "docs-ui"
 
 export const metadata = {
-  title: `File Provider Modules`,
+  title: `File Module Providers`,
 }
 
 # {metadata.title}
@@ -10,9 +10,9 @@ A File Module exposes the functionalities to upload assets, such as product imag
 
 ---
 
-## What is a File Provider Module?
+## What is a File Module Provider?
 
-A file provider module implements the logic of handling uploads and downloads. The File Module must have one file provider module configured.
+A file module provider implements the logic of handling uploads and downloads. The File Module must have one file module provider configured.
 
 By default, Medusa uses the Local File Module. This module uploads files to the `uploads` directory of your Medusa application.
 
@@ -22,6 +22,6 @@ This is useful for development. However, for production, it’s highly recommend
 
 ---
 
-## Create a File Provider Module
+## Create a File Module Provider
 
-To create a file provider module, refer to [this guide](/references/file-provider-module).
+To create a file module provider, refer to [this guide](/references/file-provider-module).

www/apps/resources/app/architectural-modules/file/s3/page.mdx

@@ -1,12 +1,12 @@
 import { Table, Tabs, TabsList, TabsContent, TabsContentWrapper, TabsTrigger } from "docs-ui"
 
 export const metadata = {
-  title: `S3 File Provider Module`,
+  title: `S3 File Module Provider`,
 }
 
 # {metadata.title}
 
-The S3 File Provider Module integrates Amazon S3 and services following a compatible API (such as MinIO or DigitalOcean Spaces) to store files uploaded to your Medusa application.
+The S3 File Module Provider integrates Amazon S3 and services following a compatible API (such as MinIO or DigitalOcean Spaces) to store files uploaded to your Medusa application.
 
 ---
 
@@ -70,7 +70,7 @@ The S3 File Provider Module integrates Amazon S3 and services following a compat
 
 ## Install the S3 File Module
 
-To install the S3 File Provider Module, run the following command in the directory of your Medusa application:
+To install the S3 File Module Provider, run the following command in the directory of your Medusa application:
 
 ```bash npm2yarn
 npm install @medusajs/file-s3