docs: fix spelling and grammar (#13862)

Fixed various spelling errors and grammatical issues across multiple .mdx documentation files.

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.

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.
 

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.

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."],
 ]
 

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(