asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: fix spelling and grammar (#13862)

Browse Source 
Fixed various spelling errors and grammatical issues across multiple .mdx documentation files.
This commit is contained in:
MBLVD
2025-10-27 10:48:59 +02:00
committed by GitHub
parent dbf8fb9bda
commit 799b57c396
47 changed files with 80 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/resources/app/how-to-tutorials/tutorials/loyalty-points/page.mdx
+3 -3
View File
@@ -971,7 +971,7 @@ Refer to the [Events and Subscribers](!docs!/learn/fundamentals/events-and-subsc
</Note>
Subscribers are created in a TypeScript or JavaScript file under the `src/subscribers` directory. So, to create a subscriber, create the fle `src/subscribers/order-placed.ts` with the following content:
Subscribers are created in a TypeScript or JavaScript file under the `src/subscribers` directory. So, to create a subscriber, create the file `src/subscribers/order-placed.ts` with the following content:
```ts title="src/subscribers/order-placed.ts"
import type {
@@ -1783,7 +1783,7 @@ The workflow will have the following steps:
{
type: "step",
name: "updatePromotionsStep",
description: "Deactive the loyalty promotion.",
description: "Deactivate the loyalty promotion.",
link: "/references/medusa-workflows/steps/updatePromotionsStep",
depth: 1,
},
@@ -2097,7 +2097,7 @@ completeCartWorkflow.hooks.validate(
)
```
Workflows have a special `hooks` property that includes all the hooks tht you can consume in that workflow. You consume the hook by invoking it from the workflow's `hooks` property.
Workflows have a special `hooks` property that includes all the hooks that you can consume in that workflow. You consume the hook by invoking it from the workflow's `hooks` property.
Since the hook is essentially a step function, it accepts the following parameters:
www/apps/resources/app/how-to-tutorials/tutorials/phone-auth/page.mdx
+2 -2
View File
@@ -361,7 +361,7 @@ export const authenticateHighlights = [
["13", "phone", "Extract from request body."],
["23", "retrieve", "Check that the user exists."],
["33", "generateOTP", "Generate a 6-digit OTP."],
["35", "update", "Store OTP in the provider metadat."],
["35", "update", "Store OTP in the provider metadata."],
["41", "emit", "Emit an event with the generated OTP."],
["51", "location", "Indicate that more actions are required."],
["55", "generateOTP", "A method to generate the OTP"],
@@ -1725,7 +1725,7 @@ export const registerPhoneHighlights = [
["24", "loading", "A boolean indicating whether the registration is in progress."],
["25", "enterOtp", "A boolean indicating whether to show the OTP form."],
["26", "countryCode", "The country code of the customer."],
["28", "handleSubmit", "Register customer on form submision."],
["28", "handleSubmit", "Register customer on form submission."],
["45", "enterOtp", "Show the OTP form after successful registration."],
]
www/apps/resources/app/how-to-tutorials/tutorials/product-builder/page.mdx
+3 -3
View File
@@ -3915,7 +3915,7 @@ You display a separate section for each custom field, complementary product, and
When a customer chooses complementary and addon products, the price shown on the product page should reflect that selection. So, you need to modify the pricing component to accept the builder configuration, and update the displayed price accordingly.
In `src/modules/products/components/product-price/index.tsx`, add the followng imports at the top of the file:
In `src/modules/products/components/product-price/index.tsx`, add the following imports at the top of the file:
```tsx title="src/modules/products/components/product-price/index.tsx" badgeLabel="Storefront" badgeColor="blue"
import { BuilderConfiguration } from "../../../../types/global"
@@ -4296,7 +4296,7 @@ npm run dev
You should see the custom fields, complementary products, and addons on the product's page.
![Product details page with builder configuations](https://res.cloudinary.com/dza7lstvk/image/upload/v1755101580/Medusa%20Resources/CleanShot_2025-08-13_at_19.12.48_2x_tf4goa.png)
![Product details page with builder configurations](https://res.cloudinary.com/dza7lstvk/image/upload/v1755101580/Medusa%20Resources/CleanShot_2025-08-13_at_19.12.48_2x_tf4goa.png)
While you can enter custom values and select variants, you still can't add the product variant with its builder configurations to the cart. You'll support that in the next step.
@@ -5274,7 +5274,7 @@ You changed the `text-ui-fg-muted` class in the wrapper `div` to `text-ui-fg-sub
#### Update Item Component
Next, you'll update the component showing a line item row. This component is used in mutliple places, including the cart and checkout pages.
Next, you'll update the component showing a line item row. This component is used in multiple places, including the cart and checkout pages.
You'll update the component to ignore addon products. Instead, you'll show them as part of the main product line item. You'll also display the custom field values of the main product.
www/apps/resources/app/how-to-tutorials/tutorials/product-reviews/page.mdx
+1 -1
View File
@@ -1589,7 +1589,7 @@ Finally, you return the reviews with pagination fields and the average rating of
### Apply Query Configurations Middleware
The last step is to add a middleware that validates the query parameters passed to the request, and sets the default Query configuations.
The last step is to add a middleware that validates the query parameters passed to the request, and sets the default Query configurations.
In `src/api/middlewares.ts`, add a new middleware: