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

* docs: rename provider module to module provider

* fix vale rule

* vale fixes
This commit is contained in:
Shahed Nasser authored and GitHub committed 2024-07-01 10:21:19 +03:00
1 parent 2833e3c4d0
commit 1842cd33cf
28 files changed
+117 -117

No files matched your search

@@ -97,7 +97,7 @@ In this document, you'll learn about the options of the Payment Module.
## providers
The `providers` option is an array of payment provider modules.
The `providers` option is an array of payment module providers.
When the Medusa application starts, these providers are registered and can be used to process payments.
@@ -130,6 +130,6 @@ module.exports = defineConfig({
The `providers` option is an array of objects that accept the following properties:
- `resolve`: A string indicating the package name of the payment provider module or the path to it relative to the `src` directory.
- `options`: An optional object of the payment provider module's options. The object must have the following property:
- `config`: An object whose key is the ID of the payment provider, and its value is an object of options to pass to the provider module.
- `resolve`: A string indicating the package name of the module provider or the path to it relative to the `src` directory.
- `options`: An optional object of the module provider's options. The object must have the following property:
- `config`: An object whose key is the ID of the module provider, and its value is an object of options to pass to the module provider.
@@ -1,22 +1,22 @@
import { ChildDocs } from "docs-ui"
export const metadata = {
title: `Payment Provider Module`,
title: `Payment Module Provider`,
}
# {metadata.title}
In this document, you’ll learn what a payment provider module is.
In this document, you’ll learn what a payment module provider is.
## What's a Payment Provider Module?
## What's a Payment Module Provider?
A payment provider module registers a payment provider that handles payment processing. It can integrate third-party payment providers, such as Stripe.
A payment module provider registers a payment provider that handles payment processing. It can integrate third-party payment providers, such as Stripe.
To authorize a payment amount with a payment provider, a payment session is created and associated with that payment provider. The payment provider is then used to handle the authorization.
After the payment session is authorized, the payment provider is associated with the resulting payment and handles its payment processing, such as to capture or refund payment.
### List of Payment Provider Modules
### List of Payment Module Providers
<ChildDocs type="item" />
@@ -5,12 +5,12 @@ sidebar_label: "Stripe"
import { Table } from "docs-ui"
export const metadata = {
title: `Stripe Provider Module`,
title: `Stripe Module Provider`,
}
# {metadata.title}
In this document, you’ll learn about the Stripe provider module and how to install and use it in the Payment Module.
In this document, you’ll learn about the Stripe Module Provider and how to install and use it in the Payment Module.
## Features
@@ -20,7 +20,7 @@ These features are also available in a safe test environment, allowing for a con
---
## Install the Stripe Provider Module
## Install the Stripe Module Provider
<Note type="check">
@@ -30,7 +30,7 @@ These features are also available in a safe test environment, allowing for a con
</Note>
To install the Stripe provider module, run the following command in the directory of your Medusa application:
To install the Stripe Module Provider, run the following command in the directory of your Medusa application:
```bash npm2yarn
npm install @medusajs/payment-stripe