From 799b57c3965da2b933c5d73955d34b1143a71573 Mon Sep 17 00:00:00 2001 From: MBLVD <149737198+MBLVD@users.noreply.github.com> Date: Mon, 27 Oct 2025 09:48:59 +0100 Subject: [PATCH] docs: fix spelling and grammar (#13862) Fixed various spelling errors and grammatical issues across multiple .mdx documentation files. --- .../app/admin-components/components/header/page.mdx | 2 +- .../commerce-modules/auth/create-actor-type/page.mdx | 4 ++-- www/apps/resources/app/commerce-modules/auth/page.mdx | 2 +- .../app/commerce-modules/cart/concepts/page.mdx | 2 +- .../app/commerce-modules/cart/extend/page.mdx | 2 +- .../app/commerce-modules/customer/extend/page.mdx | 2 +- .../app/commerce-modules/payment/payment-flow/page.mdx | 2 +- .../app/commerce-modules/pricing/price-rules/page.mdx | 2 +- .../product/admin-widget-zones/page.mdx | 2 +- .../app/commerce-modules/product/extend/page.mdx | 4 ++-- .../app/commerce-modules/promotion/extend/page.mdx | 2 +- .../app/data-model-repository-reference/page.mdx | 2 +- .../app/examples/guides/quote-management/page.mdx | 10 +++++----- www/apps/resources/app/examples/page.mdx | 4 ++-- .../how-to-tutorials/tutorials/loyalty-points/page.mdx | 6 +++--- .../app/how-to-tutorials/tutorials/phone-auth/page.mdx | 4 ++-- .../tutorials/product-builder/page.mdx | 6 +++--- .../tutorials/product-reviews/page.mdx | 2 +- .../caching/guides/memcached/page.mdx | 4 ++-- .../app/infrastructure-modules/file/local/page.mdx | 2 +- .../notification/sendgrid/page.mdx | 2 +- www/apps/resources/app/infrastructure-modules/page.mdx | 4 ++-- .../resources/app/integrations/guides/algolia/page.mdx | 4 ++-- .../app/integrations/guides/contentful/page.mdx | 6 +++--- .../resources/app/integrations/guides/magento/page.mdx | 4 ++-- .../resources/app/integrations/guides/resend/page.mdx | 2 +- .../resources/app/integrations/guides/sanity/page.mdx | 4 ++-- .../app/integrations/guides/shipstation/page.mdx | 6 +++--- www/apps/resources/app/js-sdk/auth/overview/page.mdx | 2 +- .../resources/app/medusa-cli/commands/new/page.mdx | 2 +- .../resources/app/plugins/guides/wishlist/page.mdx | 6 +++--- .../bundled-products/examples/standard/page.mdx | 2 +- .../commerce-automation/restock-notification/page.mdx | 2 +- www/apps/resources/app/recipes/ecommerce/page.mdx | 2 +- .../app/recipes/marketplace/examples/vendors/page.mdx | 6 +++--- .../recipes/subscriptions/examples/standard/page.mdx | 4 ++-- .../app/storefront-development/cart/update/page.mdx | 2 +- .../checkout/complete-cart/page.mdx | 4 ++-- .../storefront-development/checkout/payment/page.mdx | 4 ++-- .../checkout/payment/stripe/page.mdx | 2 +- .../storefront-development/customers/login/page.mdx | 4 ++-- .../storefront-development/customers/register/page.mdx | 10 +++++----- .../guides/express-checkout/page.mdx | 2 +- .../_sections/api-routes/additional-data.mdx | 2 +- .../api-routes/additional-data-error/page.mdx | 2 +- .../troubleshooting/subscribers/not-working/page.mdx | 2 +- .../troubleshooting/workflow-errors/when-then/page.mdx | 2 +- 47 files changed, 80 insertions(+), 80 deletions(-) diff --git a/www/apps/resources/app/admin-components/components/header/page.mdx b/www/apps/resources/app/admin-components/components/header/page.mdx index 9669889f2f..ca959ea6fd 100644 --- a/www/apps/resources/app/admin-components/components/header/page.mdx +++ b/www/apps/resources/app/admin-components/components/header/page.mdx @@ -128,7 +128,7 @@ It accepts the following props: name: "props", type: "object", optional: false, - description: `This property is only accepted if \`type\` is \`button\` or \`action-menu\`. If \`type\` is \`button\`, it accepts the [props to pass to the UI Button component](https://docs.medusajs.com/components/button). If \`type\` is \`action-menu\`, it accepts the props to pass to the action menu, explaind in [this guide](../action-menu/page.mdx).`, + description: `This property is only accepted if \`type\` is \`button\` or \`action-menu\`. If \`type\` is \`button\`, it accepts the [props to pass to the UI Button component](https://docs.medusajs.com/components/button). If \`type\` is \`action-menu\`, it accepts the props to pass to the action menu, explained in [this guide](../action-menu/page.mdx).`, }, { name: "link", diff --git a/www/apps/resources/app/commerce-modules/auth/create-actor-type/page.mdx b/www/apps/resources/app/commerce-modules/auth/create-actor-type/page.mdx index 8f850764d9..68ec70e12d 100644 --- a/www/apps/resources/app/commerce-modules/auth/create-actor-type/page.mdx +++ b/www/apps/resources/app/commerce-modules/auth/create-actor-type/page.mdx @@ -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. diff --git a/www/apps/resources/app/commerce-modules/auth/page.mdx b/www/apps/resources/app/commerce-modules/auth/page.mdx index 5319067836..c544751e0c 100644 --- a/www/apps/resources/app/commerce-modules/auth/page.mdx +++ b/www/apps/resources/app/commerce-modules/auth/page.mdx @@ -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. --- diff --git a/www/apps/resources/app/commerce-modules/cart/concepts/page.mdx b/www/apps/resources/app/commerce-modules/cart/concepts/page.mdx index d28f42c42e..73c76e3263 100644 --- a/www/apps/resources/app/commerce-modules/cart/concepts/page.mdx +++ b/www/apps/resources/app/commerce-modules/cart/concepts/page.mdx @@ -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. diff --git a/www/apps/resources/app/commerce-modules/cart/extend/page.mdx b/www/apps/resources/app/commerce-modules/cart/extend/page.mdx index 6d1e7ca2eb..8de8cccb2b 100644 --- a/www/apps/resources/app/commerce-modules/cart/extend/page.mdx +++ b/www/apps/resources/app/commerce-modules/cart/extend/page.mdx @@ -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. diff --git a/www/apps/resources/app/commerce-modules/customer/extend/page.mdx b/www/apps/resources/app/commerce-modules/customer/extend/page.mdx index f4c3ab4cf1..6e500fd0fc 100644 --- a/www/apps/resources/app/commerce-modules/customer/extend/page.mdx +++ b/www/apps/resources/app/commerce-modules/customer/extend/page.mdx @@ -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. diff --git a/www/apps/resources/app/commerce-modules/payment/payment-flow/page.mdx b/www/apps/resources/app/commerce-modules/payment/payment-flow/page.mdx index e6db64399a..ee8928d6aa 100644 --- a/www/apps/resources/app/commerce-modules/payment/payment-flow/page.mdx +++ b/www/apps/resources/app/commerce-modules/payment/payment-flow/page.mdx @@ -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", diff --git a/www/apps/resources/app/commerce-modules/pricing/price-rules/page.mdx b/www/apps/resources/app/commerce-modules/pricing/price-rules/page.mdx index 022e9341f4..0eca10b876 100644 --- a/www/apps/resources/app/commerce-modules/pricing/price-rules/page.mdx +++ b/www/apps/resources/app/commerce-modules/pricing/price-rules/page.mdx @@ -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. ![A diagram showcasing the relation between the PriceRule and Price](https://res.cloudinary.com/dza7lstvk/image/upload/v1709648772/Medusa%20Resources/price-rule-1_vy8bn9.jpg) diff --git a/www/apps/resources/app/commerce-modules/product/admin-widget-zones/page.mdx b/www/apps/resources/app/commerce-modules/product/admin-widget-zones/page.mdx index 07f9efd04f..796380daa2 100644 --- a/www/apps/resources/app/commerce-modules/product/admin-widget-zones/page.mdx +++ b/www/apps/resources/app/commerce-modules/product/admin-widget-zones/page.mdx @@ -29,6 +29,6 @@ This reference shows all the injection zones in the Medusa Admin related to the --- -## Product Catgory Pages +## Product Category Pages \ No newline at end of file diff --git a/www/apps/resources/app/commerce-modules/product/extend/page.mdx b/www/apps/resources/app/commerce-modules/product/extend/page.mdx index 2b002959d6..4da511c745 100644 --- a/www/apps/resources/app/commerce-modules/product/extend/page.mdx +++ b/www/apps/resources/app/commerce-modules/product/extend/page.mdx @@ -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. --- diff --git a/www/apps/resources/app/commerce-modules/promotion/extend/page.mdx b/www/apps/resources/app/commerce-modules/promotion/extend/page.mdx index 8fad32c9a5..5d7f19d455 100644 --- a/www/apps/resources/app/commerce-modules/promotion/extend/page.mdx +++ b/www/apps/resources/app/commerce-modules/promotion/extend/page.mdx @@ -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. diff --git a/www/apps/resources/app/data-model-repository-reference/page.mdx b/www/apps/resources/app/data-model-repository-reference/page.mdx index 18a302a8e0..c16884f2bc 100644 --- a/www/apps/resources/app/data-model-repository-reference/page.mdx +++ b/www/apps/resources/app/data-model-repository-reference/page.mdx @@ -16,7 +16,7 @@ Learn more about the data model repository in the [Database Operations](!docs!/l ## When to Use the Data Model Repository? -If your module has data models, then you should always extend the [service factory](!docs!/learn/fundamentals/modules/service-factory). It generates basic data-mangement operations for your module's data models. +If your module has data models, then you should always extend the [service factory](!docs!/learn/fundamentals/modules/service-factory). It generates basic data-management operations for your module's data models. However, there are some cases where you might need to perform more complex database operations and need more control over the parameters you're passing. diff --git a/www/apps/resources/app/examples/guides/quote-management/page.mdx b/www/apps/resources/app/examples/guides/quote-management/page.mdx index fc6c3e86b8..89b5701df1 100644 --- a/www/apps/resources/app/examples/guides/quote-management/page.mdx +++ b/www/apps/resources/app/examples/guides/quote-management/page.mdx @@ -706,7 +706,7 @@ In the workflow's constructor function, you use `useQueryGraphStep` to retrieve -`useQueryGraphStep` uses [Query](!docs!/learn/fundamentals/module-links/query), whic allows you to retrieve data across modules. For example, in the above snippet you're retrieving the cart's promotions, which are managed in the [Promotion Module](../../../commerce-modules/promotion/page.mdx), by passing `promotions.code` to the `fields` array. +`useQueryGraphStep` uses [Query](!docs!/learn/fundamentals/module-links/query), which allows you to retrieve data across modules. For example, in the above snippet you're retrieving the cart's promotions, which are managed in the [Promotion Module](../../../commerce-modules/promotion/page.mdx), by passing `promotions.code` to the `fields` array. @@ -1536,7 +1536,7 @@ export type AdminQuoteResponse = { You define the following types: - `AdminQuote`: Represents a quote. -- `QuoteQueryParams`: Represents the query parameters that can be passed when retrieving qoutes. +- `QuoteQueryParams`: Represents the query parameters that can be passed when retrieving quotes. - `AdminQuotesResponse`: Represents the response when retrieving a list of quotes. - `AdminQuoteResponse`: Represents the response when retrieving a single quote, which you'll implement later in this guide. @@ -1628,9 +1628,9 @@ export const config = defineRouteConfig({ export default Quotes ``` -The route file must export a React component that implements the content of the page. To show a link to the route in the sidebar, you can also export a configuation object created with `defineRouteConfig` that specifies the label and icon of the route in the Medusa Admin sidebar. +The route file must export a React component that implements the content of the page. To show a link to the route in the sidebar, you can also export a configuration object created with `defineRouteConfig` that specifies the label and icon of the route in the Medusa Admin sidebar. -In the `Quotes` component, you'll show a table of quotes using the [DataTable component](!ui!/components/data-table) from Medusa UI. This componet requires you first define the columns of the table. +In the `Quotes` component, you'll show a table of quotes using the [DataTable component](!ui!/components/data-table) from Medusa UI. This component requires you first define the columns of the table. To define the table's columns, add in the same file and before the `Quotes` component the following: @@ -1754,7 +1754,7 @@ In the component, you use the `useQuotes` hook to fetch the quotes from the Medu Next, you use the `useDataTable` hook to create a table instance with the columns you defined. You pass the fetched quotes to the `DataTable` component, along with configurations related to pagination and loading. -Notice that as part of the `useDataTable` configurations you naviagte to the `/quotes/:id` UI route when a row is clicked. You'll create that route in a later step. +Notice that as part of the `useDataTable` configurations you navigate to the `/quotes/:id` UI route when a row is clicked. You'll create that route in a later step. Finally, you render the `DataTable` component to display the quotes in a table. diff --git a/www/apps/resources/app/examples/page.mdx b/www/apps/resources/app/examples/page.mdx index 71f0a722dc..d097ff4e25 100644 --- a/www/apps/resources/app/examples/page.mdx +++ b/www/apps/resources/app/examples/page.mdx @@ -2539,7 +2539,7 @@ const { transaction } = await myLongRunningWorkflow(req.scope) .run() ``` -2. In an API route, workflow, or other resource, change a step's status to successful using the [Worfklow Engine Module](../infrastructure-modules/workflow-engine/page.mdx): +2. In an API route, workflow, or other resource, change a step's status to successful using the [Workflow Engine Module](../infrastructure-modules/workflow-engine/page.mdx): export const stepSuccessHighlights = [ ["5", "setStepSuccess", "Change a step's status to success"], @@ -2995,7 +2995,7 @@ You can customize the Medusa Admin to inject widgets in existing pages, or creat -For a list of components to use in the admin dashboard, refere to [this documentation](../admin-components/page.mdx). +For a list of components to use in the admin dashboard, refer to [this documentation](../admin-components/page.mdx). diff --git a/www/apps/resources/app/how-to-tutorials/tutorials/loyalty-points/page.mdx b/www/apps/resources/app/how-to-tutorials/tutorials/loyalty-points/page.mdx index 31704c391e..56f642d9f8 100644 --- a/www/apps/resources/app/how-to-tutorials/tutorials/loyalty-points/page.mdx +++ b/www/apps/resources/app/how-to-tutorials/tutorials/loyalty-points/page.mdx @@ -971,7 +971,7 @@ Refer to the [Events and Subscribers](!docs!/learn/fundamentals/events-and-subsc -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: diff --git a/www/apps/resources/app/how-to-tutorials/tutorials/phone-auth/page.mdx b/www/apps/resources/app/how-to-tutorials/tutorials/phone-auth/page.mdx index 6dd23b5719..d53e6812f6 100644 --- a/www/apps/resources/app/how-to-tutorials/tutorials/phone-auth/page.mdx +++ b/www/apps/resources/app/how-to-tutorials/tutorials/phone-auth/page.mdx @@ -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."], ] diff --git a/www/apps/resources/app/how-to-tutorials/tutorials/product-builder/page.mdx b/www/apps/resources/app/how-to-tutorials/tutorials/product-builder/page.mdx index d704ab07eb..8a9ffdfaa5 100644 --- a/www/apps/resources/app/how-to-tutorials/tutorials/product-builder/page.mdx +++ b/www/apps/resources/app/how-to-tutorials/tutorials/product-builder/page.mdx @@ -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. diff --git a/www/apps/resources/app/how-to-tutorials/tutorials/product-reviews/page.mdx b/www/apps/resources/app/how-to-tutorials/tutorials/product-reviews/page.mdx index 9c0ce5955a..53205f2c58 100644 --- a/www/apps/resources/app/how-to-tutorials/tutorials/product-reviews/page.mdx +++ b/www/apps/resources/app/how-to-tutorials/tutorials/product-reviews/page.mdx @@ -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: diff --git a/www/apps/resources/app/infrastructure-modules/caching/guides/memcached/page.mdx b/www/apps/resources/app/infrastructure-modules/caching/guides/memcached/page.mdx index cc2bbacc4a..b2c3640a0a 100644 --- a/www/apps/resources/app/infrastructure-modules/caching/guides/memcached/page.mdx +++ b/www/apps/resources/app/infrastructure-modules/caching/guides/memcached/page.mdx @@ -495,9 +495,9 @@ class MemcachedCachingProviderService implements ICachingProviderService { const tagResult = tagResults[i] if (tagResult.value) { - const currrentTag = tagResult.value.toString() + const currentTag = tagResult.value.toString() // If the namespace has changed since the key was stored, it's invalid - if (currrentTag !== storedTags[tag]) { + if (currentTag !== storedTags[tag]) { return false } } else { diff --git a/www/apps/resources/app/infrastructure-modules/file/local/page.mdx b/www/apps/resources/app/infrastructure-modules/file/local/page.mdx index c212c0dde5..3594b0aa0d 100644 --- a/www/apps/resources/app/infrastructure-modules/file/local/page.mdx +++ b/www/apps/resources/app/infrastructure-modules/file/local/page.mdx @@ -78,7 +78,7 @@ module.exports = { - The directory to upload files to. Medusa exposes the content of the `static` directory publically. If you change the directory, it must be served and publically accessible. + The directory to upload files to. Medusa exposes the content of the `static` directory publicly. If you change the directory, it must be served and publicly accessible. diff --git a/www/apps/resources/app/infrastructure-modules/notification/sendgrid/page.mdx b/www/apps/resources/app/infrastructure-modules/notification/sendgrid/page.mdx index 0688d9d2fa..e8c62b6c6c 100644 --- a/www/apps/resources/app/infrastructure-modules/notification/sendgrid/page.mdx +++ b/www/apps/resources/app/infrastructure-modules/notification/sendgrid/page.mdx @@ -188,7 +188,7 @@ Refer to the [Events Reference](/references/events) for a complete list of event You can also send an email using SendGrid in any [workflow](!docs!/learn/fundamentals/workflows). This allows you to send emails within your custom flows. -You can use the [sendNotifcationStep](/references/medusa-workflows/steps/sendNotificationsStep) in your workflow to send an email using SendGrid. +You can use the [sendNotificationsStep](/references/medusa-workflows/steps/sendNotificationsStep) in your workflow to send an email using SendGrid. For example: diff --git a/www/apps/resources/app/infrastructure-modules/page.mdx b/www/apps/resources/app/infrastructure-modules/page.mdx index 5ab0766a22..d6a07ec46e 100644 --- a/www/apps/resources/app/infrastructure-modules/page.mdx +++ b/www/apps/resources/app/infrastructure-modules/page.mdx @@ -168,7 +168,7 @@ The Locking Module uses module providers that implement the underlying logic of ## Notification Module -The Notification Module handles sending notifications to users or customers, such as reset password instructions or newsletters. Refer to the [Notifcation Module documentation](./notification/page.mdx) to learn more about it. +The Notification Module handles sending notifications to users or customers, such as reset password instructions or newsletters. Refer to the [Notification Module documentation](./notification/page.mdx) to learn more about it. The Notification Module has module providers that implement the underlying logic of sending notifications, typically through integrating a third-party service. The following modules are provided by Medusa. You can also create a custom provider as explained in the [Create Notification Module Provider guide](/references/notification-provider-module). @@ -220,7 +220,7 @@ The Notification Module has module providers that implement the underlying logic ## Workflow Engine Module -A Workflow Engine Module handles tracking and recording the transactions and statuses of workflows and their steps. Learn more about it in the [Worklow Engine Module documentation](./workflow-engine/page.mdx). +A Workflow Engine Module handles tracking and recording the transactions and statuses of workflows and their steps. Learn more about it in the [Workflow Engine Module documentation](./workflow-engine/page.mdx). The following Workflow Engine modules are provided by Medusa. diff --git a/www/apps/resources/app/integrations/guides/algolia/page.mdx b/www/apps/resources/app/integrations/guides/algolia/page.mdx index 2453bb979c..44aab68f5f 100644 --- a/www/apps/resources/app/integrations/guides/algolia/page.mdx +++ b/www/apps/resources/app/integrations/guides/algolia/page.mdx @@ -191,7 +191,7 @@ A module has a container that holds all resources registered in that module, and #### Index Data Method -The first method you need to add to the servie is a method that receives an array of data to add or update in Algolia's index. +The first method you need to add to the service is a method that receives an array of data to add or update in Algolia's index. Add the following methods to the `AlgoliaModuleService` class: @@ -521,7 +521,7 @@ In the compensation function, you resolve the Algolia Module's service from the ### Add Sync Products Workflow -You can now create the worklow that syncs the products to Algolia. +You can now create the workflow that syncs the products to Algolia. To create the workflow, create the file `src/workflows/sync-products.ts` with the following content: diff --git a/www/apps/resources/app/integrations/guides/contentful/page.mdx b/www/apps/resources/app/integrations/guides/contentful/page.mdx index afebb71038..aa26572adb 100644 --- a/www/apps/resources/app/integrations/guides/contentful/page.mdx +++ b/www/apps/resources/app/integrations/guides/contentful/page.mdx @@ -1029,7 +1029,7 @@ Finally, add the method to create the product: export const createProductHighlights = [ ["7", "product", "The product to create in Contentful."], ["11", "get", "Try to retrieve the existing product entry in Contentful."], - ["16", "productEntry", "Return the existng product entry."], + ["16", "productEntry", "Return the existing product entry."], ["20", "createWithId", "Create a new entry in Contentful for the product."], ["65", "createProductOption", "Create the product's options in Contentful."], ["70", "createProductVariant", "Create the product's variants in Contentful."], @@ -2360,7 +2360,7 @@ Then, you format the retrieved products to: -To paginate the retrieved products, implemet a `listAndCount` method as explained in the [Query Context](!docs!/learn/fundamentals/module-links/query-context#using-pagination-with-query) documentation. +To paginate the retrieved products, implement a `listAndCount` method as explained in the [Query Context](!docs!/learn/fundamentals/module-links/query-context#using-pagination-with-query) documentation. @@ -3037,7 +3037,7 @@ In the workflow, you: -You can't perform data manipulation in a workflow's constructor function. Instead, the Workflows SDK includes utility functions like `when` to perform typical operations that requires accessing data values. Learn more about workflow constraints in the [Workflow Constraints](!docs!/learn/fundamentals/workflows/constructor-constraints) documetation. +You can't perform data manipulation in a workflow's constructor function. Instead, the Workflows SDK includes utility functions like `when` to perform typical operations that requires accessing data values. Learn more about workflow constraints in the [Workflow Constraints](!docs!/learn/fundamentals/workflows/constructor-constraints) documentation. diff --git a/www/apps/resources/app/integrations/guides/magento/page.mdx b/www/apps/resources/app/integrations/guides/magento/page.mdx index 70f01db2ce..bc72e9f658 100644 --- a/www/apps/resources/app/integrations/guides/magento/page.mdx +++ b/www/apps/resources/app/integrations/guides/magento/page.mdx @@ -828,7 +828,7 @@ export const migrateProductsFromMagentoWorkflow = createWorkflow( You create a workflow using `createWorkflow` from the Workflows SDK. It accepts two parameters: 1. An object with the workflow's configuration, including the name and whether to store the workflow's executions. You enable storing the workflow execution so that you can view it later in the Medusa Admin dashboard. -2. A worflow constructor function, which holds the workflow's implementation. The function receives the input data for the workflow, which is the pagination parameters. +2. A workflow constructor function, which holds the workflow's implementation. The function receives the input data for the workflow, which is the pagination parameters. In the workflow constructor function, you use the `getMagentoProductsStep` step to retrieve the products from Magento, passing it the pagination parameters from the workflow's input. @@ -860,7 +860,7 @@ const { data: shippingProfiles } = useQueryGraphStep({ You use the `useQueryGraphStep` step to retrieve the store details and shipping profiles. `useQueryGraphStep` is a Medusa step that wraps [Query](!docs!/learn/fundamentals/module-links/query), allowing you to use it in a workflow. Query is a tool that retrieves data across modules. -Whe retrieving the store details, you specifically retrieve its supported currencies and default sales channel ID. You'll associate the products with the store's default sales channel, and set their variant prices in the supported currencies. You'll also associate the products with a shipping profile. +When retrieving the store details, you specifically retrieve its supported currencies and default sales channel ID. You'll associate the products with the store's default sales channel, and set their variant prices in the supported currencies. You'll also associate the products with a shipping profile. Next, you'll retrieve products that were previously migrated from Magento to determine which products to create or update. Replace the `TODO` with the following: diff --git a/www/apps/resources/app/integrations/guides/resend/page.mdx b/www/apps/resources/app/integrations/guides/resend/page.mdx index 68d4e8b53f..a78f93a301 100644 --- a/www/apps/resources/app/integrations/guides/resend/page.mdx +++ b/www/apps/resources/app/integrations/guides/resend/page.mdx @@ -1334,7 +1334,7 @@ A subscriber file exports: - An asynchronous function that's executed whenever the associated event is emitted, which is the `order.placed` event. - A configuration object with an `event` property indicating the event the subscriber is listening to. -The subscriber function accepts the event's details as a first paramter which has a `data` property that holds the data payload of the event. For example, Medusa emits the `order.placed` event with the order's ID in the data payload. The function also accepts as a second parameter the [Medusa container](!docs!/learn/fundamentals/medusa-container). +The subscriber function accepts the event's details as a first parameter which has a `data` property that holds the data payload of the event. For example, Medusa emits the `order.placed` event with the order's ID in the data payload. The function also accepts as a second parameter the [Medusa container](!docs!/learn/fundamentals/medusa-container). In the function, you execute the `sendOrderConfirmationWorkflow` by invoking it, passing it the `container`, then using its `run` method. The `run` method accepts an object having an `input` property, which is the input to pass to the workflow. You pass the ID of the placed order as received in the event's data payload. diff --git a/www/apps/resources/app/integrations/guides/sanity/page.mdx b/www/apps/resources/app/integrations/guides/sanity/page.mdx index 8021ceb5d5..440df5fd2c 100644 --- a/www/apps/resources/app/integrations/guides/sanity/page.mdx +++ b/www/apps/resources/app/integrations/guides/sanity/page.mdx @@ -574,7 +574,7 @@ Where: - Enter a name for the API token, choose "Editor" for the permissions, then click Save. -![In the Token form, enter the name and choose "Editor" for permisions.](https://res.cloudinary.com/dza7lstvk/image/upload/v1732091811/Medusa%20Resources/Screenshot_2024-11-20_at_10.36.25_AM_nqxa5y.png) +![In the Token form, enter the name and choose "Editor" for permissions.](https://res.cloudinary.com/dza7lstvk/image/upload/v1732091811/Medusa%20Resources/Screenshot_2024-11-20_at_10.36.25_AM_nqxa5y.png) - `SANITY_PROJECT_ID`: The ID of the project, which you can find at the top section of your Sanity project's dashboard. @@ -1816,7 +1816,7 @@ export const useSanitySyncs = ( The `useTriggerSanitySync` hook creates a mutation that, when executed, sends a request to the trigger sync API route you created earlier to sync all products. -The `useSanitySyncs` hook sends a request to the retrieve sync executions API route that you created earlier to retrieve the workflow's exections. +The `useSanitySyncs` hook sends a request to the retrieve sync executions API route that you created earlier to retrieve the workflow's executions. Finally, to create the UI route, create the file `src/admin/routes/sanity/page.tsx` with the following content: diff --git a/www/apps/resources/app/integrations/guides/shipstation/page.mdx b/www/apps/resources/app/integrations/guides/shipstation/page.mdx index 53ceb577e9..87f262a833 100644 --- a/www/apps/resources/app/integrations/guides/shipstation/page.mdx +++ b/www/apps/resources/app/integrations/guides/shipstation/page.mdx @@ -275,7 +275,7 @@ export class ShipStationClient { if (typeof resp !== "string" && resp.errors?.length) { throw new MedusaError( MedusaError.Types.INVALID_DATA, - `An error occured while sending a request to ShipStation: ${ + `An error occurred while sending a request to ShipStation: ${ resp.errors.map((error) => error.message) }` ) @@ -630,7 +630,7 @@ export class ShipStationClient { if (resp.rate_response.errors?.length) { throw new MedusaError( MedusaError.Types.INVALID_DATA, - `An error occured while retrieving rates from ShipStation: ${ + `An error occurred while retrieving rates from ShipStation: ${ resp.rate_response.errors.map((error) => error.message) }` ) @@ -1281,7 +1281,7 @@ Where `SHIPSTATION_API_KEY` is the ShipStation API key, which you can retrieve o ![The sidebar has an Account expandable. When you click on it, more items will show. Click on the API Settings](https://res.cloudinary.com/dza7lstvk/image/upload/v1734352145/Medusa%20Resources/Screenshot_2024-12-16_at_2.28.32_PM_wwfc1s.png). -- On the API Settings page, make sure V2 API is selected for "Select API Verion" field, then click the "Generate API Key" button. +- On the API Settings page, make sure V2 API is selected for "Select API Version" field, then click the "Generate API Key" button. ![Make sure V2 API is selected in the Select API Version dropdown, then click on the "Generate API Key" button.](https://res.cloudinary.com/dza7lstvk/image/upload/v1734352261/Medusa%20Resources/Screenshot_2024-12-16_at_2.30.31_PM_vbkz4i.png) diff --git a/www/apps/resources/app/js-sdk/auth/overview/page.mdx b/www/apps/resources/app/js-sdk/auth/overview/page.mdx index d963371226..5b795d76b2 100644 --- a/www/apps/resources/app/js-sdk/auth/overview/page.mdx +++ b/www/apps/resources/app/js-sdk/auth/overview/page.mdx @@ -202,7 +202,7 @@ export const sdk = new Medusa({ auth: { type: "jwt", jwtTokenStorageMethod: "custom", - storge: AsyncStorage, + storage: AsyncStorage, }, }) ``` diff --git a/www/apps/resources/app/medusa-cli/commands/new/page.mdx b/www/apps/resources/app/medusa-cli/commands/new/page.mdx index 36a3d3dcea..0398560daa 100644 --- a/www/apps/resources/app/medusa-cli/commands/new/page.mdx +++ b/www/apps/resources/app/medusa-cli/commands/new/page.mdx @@ -94,7 +94,7 @@ medusa new [ []] - Skip all prompts, such as databaes prompts. A database might not be created if default PostgreSQL credentials don't work. + Skip all prompts, such as database prompts. A database might not be created if default PostgreSQL credentials don't work. diff --git a/www/apps/resources/app/plugins/guides/wishlist/page.mdx b/www/apps/resources/app/plugins/guides/wishlist/page.mdx index 62a86ccfef..e7ad1d4adb 100644 --- a/www/apps/resources/app/plugins/guides/wishlist/page.mdx +++ b/www/apps/resources/app/plugins/guides/wishlist/page.mdx @@ -609,7 +609,7 @@ The second step in the workflow will create a wishlist for the customer. To crea ![Directory structure after adding the step file](https://res.cloudinary.com/dza7lstvk/image/upload/v1737467998/Medusa%20Resources/wishlist-10_xex4d0.jpg) -export const createWishlistStepHiglights = [ +export const createWishlistStepHighlights = [ ["13", "wishlistModuleService", "Resolve the Wishlist Module's service from the container."], ["16", "createWishlists", "Create the wishlist."], ["18", "wishlist", "Return the wishlist"], @@ -617,7 +617,7 @@ export const createWishlistStepHiglights = [ ["24", "deleteWishlists", "Delete the wishlist if an error occurs in the workflow."] ] -```ts title="src/workflows/steps/create-wishlist.ts" highlights={createWishlistStepHiglights} +```ts title="src/workflows/steps/create-wishlist.ts" highlights={createWishlistStepHighlights} import { createStep, StepResponse } from "@medusajs/framework/workflows-sdk" import { WISHLIST_MODULE } from "../../modules/wishlist" import WishlistModuleService from "../../modules/wishlist/service" @@ -1979,7 +1979,7 @@ export default class WishlistModuleService extends MedusaService({ To perform queries on the database in a method, add the `@InjectManager` decorator to the method. This will inject a [forked MikroORM entity manager](https://mikro-orm.io/docs/identity-map#forking-entity-manager) that you can use in your method. -Methods with the `@InjectManager` decorator accept as a last parameter a context object that has the `@MedusaContext` decorator. The entity manager is injected into the `manager` property of this paramter. +Methods with the `@InjectManager` decorator accept as a last parameter a context object that has the `@MedusaContext` decorator. The entity manager is injected into the `manager` property of this parameter. The method accepts an array of variant IDs as a parameter. In the method, you use the `createQueryBuilder` to construct a query, passing it the name of the `WishlistItem`'s table. You then select distinct `wishlist_id`s where the `product_variant_id` of the wishlist item is in the array of variant IDs. diff --git a/www/apps/resources/app/recipes/bundled-products/examples/standard/page.mdx b/www/apps/resources/app/recipes/bundled-products/examples/standard/page.mdx index 3251bd9976..db00f01bb8 100644 --- a/www/apps/resources/app/recipes/bundled-products/examples/standard/page.mdx +++ b/www/apps/resources/app/recipes/bundled-products/examples/standard/page.mdx @@ -3040,7 +3040,7 @@ Now that you have a working bundled product feature, you can customize it furthe - Add API routes to update the bundled product and its items in the cart. - Add more CRUD management features to the Bundled Products page in the Medusa Admin. -- Customize the Next.js Starter Storefront to show the bundled products together in the cart, rather than seperately. +- Customize the Next.js Starter Storefront to show the bundled products together in the cart, rather than separately. - Use custom logic to set the price of the bundled product. If you're new to Medusa, check out the [main documentation](!docs!/learn), where you'll get a more in-depth learning of all the concepts you've used in this guide and more. diff --git a/www/apps/resources/app/recipes/commerce-automation/restock-notification/page.mdx b/www/apps/resources/app/recipes/commerce-automation/restock-notification/page.mdx index bd7eea1cea..27a8ba2747 100644 --- a/www/apps/resources/app/recipes/commerce-automation/restock-notification/page.mdx +++ b/www/apps/resources/app/recipes/commerce-automation/restock-notification/page.mdx @@ -1153,7 +1153,7 @@ export default RestockModuleService To perform queries on the database in a method, add the `@InjectManager` decorator to the method. This will inject a [forked MikroORM entity manager](https://mikro-orm.io/docs/identity-map#forking-entity-manager) that you can use in your method. -Methods with the `@InjectManager` decorator accept as a last parameter a context object that has the `@MedusaContext` decorator. The entity manager is injected into the `manager` property of this paramter. +Methods with the `@InjectManager` decorator accept as a last parameter a context object that has the `@MedusaContext` decorator. The entity manager is injected into the `manager` property of this parameter. In the method, you use the `createQueryBuilder` to construct a query, passing it the name of the `RestockSubscription`'s table. You then select distinct `variant_id` and `sales_channel` pairings, and execute and return the query's result. diff --git a/www/apps/resources/app/recipes/ecommerce/page.mdx b/www/apps/resources/app/recipes/ecommerce/page.mdx index 9295e4533d..af46cead58 100644 --- a/www/apps/resources/app/recipes/ecommerce/page.mdx +++ b/www/apps/resources/app/recipes/ecommerce/page.mdx @@ -92,4 +92,4 @@ Our documentation also provides a step-by-step guides to deploy your Medusa appl Along with the extensive ecommerce features, Medusa also provides the architecture and Framework to customize your application and build custom features that are tailored for your business use case. -To learn how to develop customziations with Medusa, refer to the [Get Started](!docs!/learn) documentation. +To learn how to develop customizations with Medusa, refer to the [Get Started](!docs!/learn) documentation. diff --git a/www/apps/resources/app/recipes/marketplace/examples/vendors/page.mdx b/www/apps/resources/app/recipes/marketplace/examples/vendors/page.mdx index d3e0ee9776..dbc0d129e4 100644 --- a/www/apps/resources/app/recipes/marketplace/examples/vendors/page.mdx +++ b/www/apps/resources/app/recipes/marketplace/examples/vendors/page.mdx @@ -672,7 +672,7 @@ In the workflow function, you run the following steps: 1. `createVendorStep` to create the vendor. 2. `createVendorAdminStep` to create the vendor admin. - - Notice that you use `transform` from the Workflows SDK to prepare the data you pass into the step. Medusa doesn't allow direct manipulation of variables within the worflow's constructor function. Learn more in the [Data Manipulation in Workflows documentation](!docs!/learn/fundamentals/workflows/variable-manipulation). + - Notice that you use `transform` from the Workflows SDK to prepare the data you pass into the step. Medusa doesn't allow direct manipulation of variables within the workflow's constructor function. Learn more in the [Data Manipulation in Workflows documentation](!docs!/learn/fundamentals/workflows/variable-manipulation). 3. `setAuthAppMetadataStep` to associate the vendor admin with its auth identity of actor type `vendor`. This will allow the vendor admin to send authenticated requests afterwards. 4. `useQueryGraphStep` to retrieve the created vendor with its admins using [Query](!docs!/learn/fundamentals/module-links/query). Query allows you to retrieve data across modules. @@ -1547,7 +1547,7 @@ try { ) } catch (e) { return StepResponse.permanentFailure( - `An error occured while creating vendor orders: ${e}`, + `An error occurred while creating vendor orders: ${e}`, { created_orders: createdOrders, } @@ -1831,7 +1831,7 @@ In the next step, you'll create an API route to retrieve the vendor's orders, al In this step, you’ll create an API route that retrieves a vendor’s orders. Create the file `src/api/vendors/orders/route.ts` with the following content: export const getOrderHighlights = [ - ["11", "graph", "Retrive the vendor admin's vendor and orders."], + ["11", "graph", "Retrieve the vendor admin's vendor and orders."], ["19", "getOrdersListWorkflow", "Use Medusa's workflow to retrieve the list of orders."], ] diff --git a/www/apps/resources/app/recipes/subscriptions/examples/standard/page.mdx b/www/apps/resources/app/recipes/subscriptions/examples/standard/page.mdx index f373b5b328..18c9bb14eb 100644 --- a/www/apps/resources/app/recipes/subscriptions/examples/standard/page.mdx +++ b/www/apps/resources/app/recipes/subscriptions/examples/standard/page.mdx @@ -597,7 +597,7 @@ Create the file `src/workflows/create-subscription/steps/create-subscription.ts` export const createSubscriptionsHighlights = [ ["28", "linkDefs", "An array of links to be created later."], ["30", "createSubscriptions", "Create the subscription."], - ["33", "main_order_id", "Store the ID of the order created for the subscription purhcase."], + ["33", "main_order_id", "Store the ID of the order created for the subscription purchase."], ["43", "subscription", "Pass the subscription to the compensation function."] ] @@ -1772,7 +1772,7 @@ You create a `getLatestPaymentMethod` function that receives an array of payment Then, you create the `getPaymentMethodStep` that receives the customer's data and account holder as an input. -Next, you'll add the implemenation of the step. Replace `getPaymentMethodStep` with the following: +Next, you'll add the implementation of the step. Replace `getPaymentMethodStep` with the following: ```tsx title="src/workflows/create-subscription-order/steps/get-payment-method.ts" export const getPaymentMethodStep = createStep( diff --git a/www/apps/resources/app/storefront-development/cart/update/page.mdx b/www/apps/resources/app/storefront-development/cart/update/page.mdx index d8ae8771dc..97db012d77 100644 --- a/www/apps/resources/app/storefront-development/cart/update/page.mdx +++ b/www/apps/resources/app/storefront-development/cart/update/page.mdx @@ -58,7 +58,7 @@ The [Update Cart API route](!api!/store#carts_postcartsid) accepts a `region_id` You might need to change the cart's customer in two cases: - You created the cart for the customer as a guest, then they logged-in, so you want to associate the cart with them as a registered customer. -- You're transfering the cart from one customer to another, which is useful in company setups, such as when implementing B2B commerce applicatons. +- You're transferring the cart from one customer to another, which is useful in company setups, such as when implementing B2B commerce applications. To set or change the cart's customer, send an authenticated `POST` request to the Set Cart's Customer API route: diff --git a/www/apps/resources/app/storefront-development/checkout/complete-cart/page.mdx b/www/apps/resources/app/storefront-development/checkout/complete-cart/page.mdx index 797a7e492a..ada8add965 100644 --- a/www/apps/resources/app/storefront-development/checkout/complete-cart/page.mdx +++ b/www/apps/resources/app/storefront-development/checkout/complete-cart/page.mdx @@ -36,7 +36,7 @@ Learn how to install and configure the JS SDK in the [JS SDK documentation](../. sdk.store.cart.complete(cart.id) .then((data) => { if (data.type === "cart" && data.cart) { - // an error occured + // an error occurred console.error(data.error) } else if (data.type === "order" && data.order) { // TODO redirect to order success page @@ -106,7 +106,7 @@ export default function SystemDefaultPayment() { sdk.store.cart.complete(cart.id) .then((data) => { if (data.type === "cart" && data.cart) { - // an error occured + // an error occurred console.error(data.error) } else if (data.type === "order" && data.order) { // TODO redirect to order success page diff --git a/www/apps/resources/app/storefront-development/checkout/payment/page.mdx b/www/apps/resources/app/storefront-development/checkout/payment/page.mdx index c797040ede..540e3e4187 100644 --- a/www/apps/resources/app/storefront-development/checkout/payment/page.mdx +++ b/www/apps/resources/app/storefront-development/checkout/payment/page.mdx @@ -59,7 +59,7 @@ export const highlights = [ ["57", "activePaymentSession", "The active session is the first in the payment collection's sessions."], ["62", "", "Test which payment provider is chosen based on the prefix of the provider ID."], ["63", `"pp_stripe_"`, "Check if the chosen provider is Stripe."], - ["71", `"pp_system_default"`, "Check if the chosen provider is the default systen provider."], + ["71", `"pp_system_default"`, "Check if the chosen provider is the default system provider."], ["77", "default", "Handle unrecognized providers."], ["112", "getPaymentUi", "If a provider is chosen, render its UI."] ] @@ -195,7 +195,7 @@ export const fetchHighlights = [ ["32", "activePaymentSession", "The active session is the first in the payment collection's sessions."], ["38", "", "Test which payment provider is chosen based on the prefix of the provider ID."], ["39", `"pp_stripe_"`, "Check if the chosen provider is Stripe."], - ["43", `"pp_system_default"`, "Check if the chosen provider is the default systen provider."], + ["43", `"pp_system_default"`, "Check if the chosen provider is the default system provider."], ["45", "default", "Handle unrecognized providers."], ["52", "handlePayment", "The function that handles the payment process using the above functions."] ] diff --git a/www/apps/resources/app/storefront-development/checkout/payment/stripe/page.mdx b/www/apps/resources/app/storefront-development/checkout/payment/stripe/page.mdx index f66e60450c..0b35eff74d 100644 --- a/www/apps/resources/app/storefront-development/checkout/payment/stripe/page.mdx +++ b/www/apps/resources/app/storefront-development/checkout/payment/stripe/page.mdx @@ -185,7 +185,7 @@ const StripeForm = ({ sdk.store.cart.complete(cart.id) .then((data) => { if (data.type === "cart" && data.cart) { - // an error occured + // an error occurred console.error(data.error) } else if (data.type === "order" && data.order) { // TODO redirect to order success page diff --git a/www/apps/resources/app/storefront-development/customers/login/page.mdx b/www/apps/resources/app/storefront-development/customers/login/page.mdx index 3148413b3c..263aa80b14 100644 --- a/www/apps/resources/app/storefront-development/customers/login/page.mdx +++ b/www/apps/resources/app/storefront-development/customers/login/page.mdx @@ -137,7 +137,7 @@ export const highlights = [ password, }) } catch (error) { - alert(`An error occured while logging in: ${error}`) + alert(`An error occurred while logging in: ${error}`) return } @@ -200,7 +200,7 @@ export const fetchHighlights = [ password, }) } catch (error) { - alert(`An error occured while logging in: ${error}`) + alert(`An error occurred while logging in: ${error}`) return } diff --git a/www/apps/resources/app/storefront-development/customers/register/page.mdx b/www/apps/resources/app/storefront-development/customers/register/page.mdx index 889433eb90..6d8b22b8d7 100644 --- a/www/apps/resources/app/storefront-development/customers/register/page.mdx +++ b/www/apps/resources/app/storefront-development/customers/register/page.mdx @@ -47,7 +47,7 @@ Learn how to install and configure the JS SDK in the [JS SDK documentation](../. ## How to Implement the Register Customer Flow -An example implemetation of the registration flow in a storefront: +An example implementation of the registration flow in a storefront: @@ -95,7 +95,7 @@ export const highlights = [ const fetchError = error as FetchError if (fetchError.statusText !== "Unauthorized" || fetchError.message !== "Identity with email already exists") { - alert(`An error occured while creating account: ${fetchError}`) + alert(`An error occurred while creating account: ${fetchError}`) return } // another identity (for example, admin user) @@ -105,7 +105,7 @@ export const highlights = [ email, password, }).catch((e) => { - alert(`An error occured while creating account: ${e}`) + alert(`An error occurred while creating account: ${e}`) })) if (!loginResponse) { @@ -206,7 +206,7 @@ export const fetchHighlights = [ const fetchError = error as FetchError if (fetchError.statusText !== "Unauthorized" || fetchError.message !== "Identity with email already exists") { - alert(`An error occured while creating account: ${fetchError}`) + alert(`An error occurred while creating account: ${fetchError}`) return } // another identity (for example, admin user) @@ -216,7 +216,7 @@ export const fetchHighlights = [ email, password, }).catch((e) => { - alert(`An error occured while creating account: ${e}`) + alert(`An error occurred while creating account: ${e}`) })) if (!loginResponse) { diff --git a/www/apps/resources/app/storefront-development/guides/express-checkout/page.mdx b/www/apps/resources/app/storefront-development/guides/express-checkout/page.mdx index d97ad31c55..66bb5577ef 100644 --- a/www/apps/resources/app/storefront-development/guides/express-checkout/page.mdx +++ b/www/apps/resources/app/storefront-development/guides/express-checkout/page.mdx @@ -1440,7 +1440,7 @@ const handleAddToCart = () => { You add a `handleAddToCart` function that first checks that a variant is selected, that it's in stock, and that the customer has set a quantity greater than `0`. -If the conditions are satisifed, you set `loading` to `true`, then call the `addToCart` function from the cart context, passing the selected variant's ID and the quantity as arguments. +If the conditions are satisfied, you set `loading` to `true`, then call the `addToCart` function from the cart context, passing the selected variant's ID and the quantity as arguments. After the product is added to the cart, you navigate to the address step, which you'll create later. diff --git a/www/apps/resources/app/troubleshooting/_sections/api-routes/additional-data.mdx b/www/apps/resources/app/troubleshooting/_sections/api-routes/additional-data.mdx index e617f07a39..0815a12574 100644 --- a/www/apps/resources/app/troubleshooting/_sections/api-routes/additional-data.mdx +++ b/www/apps/resources/app/troubleshooting/_sections/api-routes/additional-data.mdx @@ -7,7 +7,7 @@ If you send a request to an API route and receive the following error: } ``` -## Why this Error Occured +## Why this Error Occurred This error occurs when you send the `additional_data` request body parameter to a route that doesn't support it. diff --git a/www/apps/resources/app/troubleshooting/api-routes/additional-data-error/page.mdx b/www/apps/resources/app/troubleshooting/api-routes/additional-data-error/page.mdx index 3597ffa2b3..fa382e6489 100644 --- a/www/apps/resources/app/troubleshooting/api-routes/additional-data-error/page.mdx +++ b/www/apps/resources/app/troubleshooting/api-routes/additional-data-error/page.mdx @@ -1,7 +1,7 @@ import AdditionalDataError from "../../_sections/api-routes/additional-data.mdx" export const metadata = { - title: `Unrecognized fields \`additiona_data\` Error`, + title: `Unrecognized fields \`additional_data\` Error`, } # {metadata.title} diff --git a/www/apps/resources/app/troubleshooting/subscribers/not-working/page.mdx b/www/apps/resources/app/troubleshooting/subscribers/not-working/page.mdx index 957efd443c..89ada62938 100644 --- a/www/apps/resources/app/troubleshooting/subscribers/not-working/page.mdx +++ b/www/apps/resources/app/troubleshooting/subscribers/not-working/page.mdx @@ -74,7 +74,7 @@ If the event is not being emitted, check the logic in your code to ensure that t Make sure that your subscriber is correctly set up to listen to the event you're emitting. Check the following: 1. The subscriber is created under the `src/subscribers` directory. -2. The subscriber exports an asynchronus function that handles the event. For example: +2. The subscriber exports an asynchronous function that handles the event. For example: ```ts title="src/subscribers/your-subscriber.ts" import { SubscriberArgs, type SubscriberConfig } from "@medusajs/framework" diff --git a/www/apps/resources/app/troubleshooting/workflow-errors/when-then/page.mdx b/www/apps/resources/app/troubleshooting/workflow-errors/when-then/page.mdx index c1827833b8..c973fd5cd4 100644 --- a/www/apps/resources/app/troubleshooting/workflow-errors/when-then/page.mdx +++ b/www/apps/resources/app/troubleshooting/workflow-errors/when-then/page.mdx @@ -10,7 +10,7 @@ The following error may occur in production if you use a `when-then` block in yo custom-workflow:when-then-01JE8Z0M1FXSE2NCK1G04S0RR2:invoke - Handler for action \"when-then-01JE8Z0M1FXSE2NCK1G04S0RR2\" not found... ``` -## Why this Error Occured +## Why this Error Occurred This error occurs if the `when-then` block doesn't return a step's result and doesn't have a name specified.