docs: fix spelling and grammar (#13862)
Fixed various spelling errors and grammatical issues across multiple .mdx documentation files.
This commit is contained in:
MBLVD authored and 
GitHub committed
1 parent
dbf8fb9bda
commit
799b57c396
47 files changed
+80
-80
No files matched your search
@@ -51,7 +51,7 @@ Start by creating a workflow that does two things:
|
||||
For example, create the file `src/workflows/create-manager.ts`. with the following content:
|
||||
|
||||
export const workflowHighlights = [
|
||||
["21", "createManagerStep", "Thi step creates a manager."],
|
||||
["21", "createManagerStep", "This step creates a manager."],
|
||||
["38", "createManagerWorkflow", "The workflow used to create a manager and set its auth identity's actor type."],
|
||||
["45", "setAuthAppMetadataStep", "Set the actor type of the manager's associated auth identity."],
|
||||
["47", '"manager"', "The actor type of the manager."]
|
||||
@@ -177,7 +177,7 @@ export async function POST(
|
||||
|
||||
Since the manager must be associated with an `AuthIdentity` record, the request is expected to be authenticated, even if the manager isn’t created yet. This can be achieved by:
|
||||
|
||||
1. Obtaining a token usng the [/auth route](../authentication-route/page.mdx).
|
||||
1. Obtaining a token using the [/auth route](../authentication-route/page.mdx).
|
||||
2. Passing the token in the bearer header of the request to this route.
|
||||
|
||||
In the API route, you create the manager using the workflow from the previous section and return it in the response.
|
||||
|
||||
@@ -25,7 +25,7 @@ Learn more about why modules are isolated in [this documentation](!docs!/learn/f
|
||||
- [Basic User Authentication](./authentication-route/page.mdx#1-basic-authentication-flow): Authenticate users using their email and password credentials.
|
||||
- [Third-Party and Social Authentication](./authentication-route/page.mdx#2-third-party-service-authenticate-flow): Authenticate users using third-party services and social platforms, such as [Google](./auth-providers/google/page.mdx) and [GitHub](./auth-providers/github/page.mdx).
|
||||
- [Authenticate Custom Actor Types](./create-actor-type/page.mdx): Create custom user or actor types, such as managers, authenticate them in your application, and guard routes based on the custom user types.
|
||||
- [Custom Authentication Providers](/references/auth/provider): Integrate third-party services with custom authentication providors.
|
||||
- [Custom Authentication Providers](/references/auth/provider): Integrate third-party services with custom authentication providers.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ In this document, you’ll learn about the main concepts related to carts in Med
|
||||
|
||||
A cart is the selection of product variants that a customer intends to purchase. It is represented by the [Cart data model](/references/cart/models/Cart).
|
||||
|
||||
A cart holds informations about:
|
||||
A cart holds information about:
|
||||
|
||||
- The items the customer wants to buy.
|
||||
- The customer's shipping and billing addresses.
|
||||
|
||||
@@ -153,7 +153,7 @@ export default defineMiddlewares({
|
||||
})
|
||||
```
|
||||
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validaiton rules.
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validation rules.
|
||||
|
||||
In the snippet above, you add a validation rule indicating that `custom_name` is a string that can be passed in the `additional_data` object.
|
||||
|
||||
|
||||
@@ -159,7 +159,7 @@ export default defineMiddlewares({
|
||||
})
|
||||
```
|
||||
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validaiton rules.
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validation rules.
|
||||
|
||||
In the snippet above, you add a validation rule indicating that `custom_name` is a string that can be passed in the `additional_data` object.
|
||||
|
||||
|
||||
@@ -127,7 +127,7 @@ import { createPaymentSessionsWorkflow } from "@medusajs/medusa/core-flows"
|
||||
|
||||
// ...
|
||||
|
||||
const { result: paymentSesion } = await createPaymentSessionsWorkflow(container)
|
||||
const { result: paymentSession } = await createPaymentSessionsWorkflow(container)
|
||||
.run({
|
||||
input: {
|
||||
payment_collection_id: "paycol_123",
|
||||
|
||||
@@ -181,7 +181,7 @@ Each rule of a price is represented by the [PriceRule data model](/references/pr
|
||||
|
||||
The `Price` data model has a `rules_count` property, which indicates how many rules, represented by `PriceRule`, are applied to the price.
|
||||
|
||||
For exmaple, you create a price restricted to `10557` zip codes.
|
||||
For example, you create a price restricted to `10557` zip codes.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -29,6 +29,6 @@ This reference shows all the injection zones in the Medusa Admin related to the
|
||||
|
||||
---
|
||||
|
||||
## Product Catgory Pages
|
||||
## Product Category Pages
|
||||
|
||||
<ProductCategoryContent />
|
||||
@@ -159,7 +159,7 @@ export default defineMiddlewares({
|
||||
})
|
||||
```
|
||||
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validaiton rules.
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validation rules.
|
||||
|
||||
In the snippet above, you add a validation rule indicating that `custom_name` is a string that can be passed in the `additional_data` object.
|
||||
|
||||
@@ -339,7 +339,7 @@ Make sure to replace `{token}` with an admin user's JWT token. Learn how to retr
|
||||
|
||||
Also, make sure to replace `{shipping_profile_id}` with an existing shipping profile's ID. You can retrieve one either from the Medusa Admin dashboard or using the [List Shipping Profiles API Route](!api!/admin#shipping-profiles_getshippingprofiles).
|
||||
|
||||
The request will return the product's details. You'll learn how to retreive the `custom_name` property with the product's details in the next section.
|
||||
The request will return the product's details. You'll learn how to retrieve the `custom_name` property with the product's details in the next section.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -159,7 +159,7 @@ export default defineMiddlewares({
|
||||
})
|
||||
```
|
||||
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validaiton rules.
|
||||
The `additional_data` parameter validation is customized using `defineMiddlewares`. In the routes middleware configuration object, the `additionalDataValidator` property accepts [Zod](https://zod.dev/) validation rules.
|
||||
|
||||
In the snippet above, you add a validation rule indicating that `custom_name` is a string that can be passed in the `additional_data` object.
|
||||
|
||||
|
||||
Reference in new issue
Block a user