docs: correct typos in documentation (#4413)
* Correct typos in documentation * Remove changes to References directory --------- Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
This commit is contained in:
Bhyn
GitHub
@@ -158,7 +158,7 @@ In case the customer enters an invalid discount or the discount cannot be applie
|
||||
|
||||
## Display Discount Details
|
||||
|
||||
After the customer enters a discount code and it is applied to the cart, you can display the discount details to the customer. This shows the customer how much they benefitted from the discount.
|
||||
After the customer enters a discount code and it is applied to the cart, you can display the discount details to the customer. This shows the customer how much they benefited from the discount.
|
||||
|
||||
The previous request returns the full cart object with different fields that can be used to display the discount details depending on the discount type.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ The `StockLocation` entity represents a stock location. It has minimal attribute
|
||||
|
||||
## StockLocationAddress Entity
|
||||
|
||||
The `StockLocationAddress` is an entitiy that contains address-related fields, such as `city` or `country_code`.
|
||||
The `StockLocationAddress` is an entity that contains address-related fields, such as `city` or `country_code`.
|
||||
|
||||
The `StockLocationAddress` entity belongs to the `StockLocation` entity. It is used to store the address details of a stock location.
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ You want to add or use the following admin functionalities:
|
||||
|
||||
---
|
||||
|
||||
## Prerequisities
|
||||
## Prerequisites
|
||||
|
||||
### Medusa Components
|
||||
|
||||
|
||||
@@ -565,13 +565,13 @@ medusa.admin.orders.capturePayment(orderId)
|
||||
import { useAdminCapturePayment } from "medusa-react"
|
||||
|
||||
const CapturePayment = () => {
|
||||
const capturePament = useAdminCapturePayment(
|
||||
const capturePayment = useAdminCapturePayment(
|
||||
orderId
|
||||
)
|
||||
// ...
|
||||
|
||||
const handleCapture = () => {
|
||||
capturePament.mutate()
|
||||
capturePayment.mutate()
|
||||
}
|
||||
|
||||
// ...
|
||||
|
||||
@@ -182,7 +182,7 @@ Medusa provides the necessary infrastructure and tooling that allows automating
|
||||
|
||||
The Medusa backend facilitates automating these flows by allowing the customer to submit a [return](https://docs.medusajs.com/api/store#tag/Returns/operation/PostReturns) or [swap](https://docs.medusajs.com/api/store#tag/Swaps/operation/PostSwaps) requests through the store APIs. The merchant can then review and handle these requests. This eliminates the need for the customer to perform the same action through customer support or other means.
|
||||
|
||||
You can also integrate these flows within bigger processes that trigger requesting or creating these flows. It can be done through core APIs, [custom endpoints](../../development/endpoints/overview.mdx), or [custom services](../../development/services/overview.mdx). You can also listen to events related to orders such as [Order](../../development/events/events-list.md#order-events) or [Swap](../../development/events/events-list.md#swap-events) events with [subscribers](../../development/events/subscribers.mdx) to perform asynchronus actions.
|
||||
You can also integrate these flows within bigger processes that trigger requesting or creating these flows. It can be done through core APIs, [custom endpoints](../../development/endpoints/overview.mdx), or [custom services](../../development/services/overview.mdx). You can also listen to events related to orders such as [Order](../../development/events/events-list.md#order-events) or [Swap](../../development/events/events-list.md#swap-events) events with [subscribers](../../development/events/subscribers.mdx) to perform asynchronous actions.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ This section gives an overview of the features available in Medusa. You can lear
|
||||
|
||||
### Optimized Shopping and Fulfillment Experience
|
||||
|
||||
Medusa provides the necessary features to build a customizable shopping experience for your customers. Medusa also offers features optimized for business operations to manage their orders effeciently.
|
||||
Medusa provides the necessary features to build a customizable shopping experience for your customers. Medusa also offers features optimized for business operations to manage their orders efficiently.
|
||||
|
||||
<LargeCardList colSize={6}>
|
||||
<LargeCard
|
||||
@@ -80,7 +80,7 @@ Medusa provides the necessary features to build a customizable shopping experien
|
||||
}}
|
||||
>
|
||||
|
||||
- Allow orders from both registered and unregisterd customers.
|
||||
- Allow orders from both registered and unregistered customers.
|
||||
- Allow customers to create return or exchange requests from the storefront for better customer experience.
|
||||
- Assign customers different groups for segmentation and specify different pricing for customer groups.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
description: 'Learn how to implement price list functionalities for admins using the REST APIs. This includes how to create a price list, retriving price list details, managing prices in the price list, and more.'
|
||||
description: 'Learn how to implement price list functionalities for admins using the REST APIs. This includes how to create a price list, retrieving price list details, managing prices in the price list, and more.'
|
||||
addHowToData: true
|
||||
---
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ The relation is implemented in the Product entity. You can access the product
|
||||
The parent-child hierarchy is represented in the `ProductCategory` entity through the following relations:
|
||||
|
||||
- You can access the parent of a category by expanding the `parent_category` relation and accessing `category.parent_category`. You can also access the ID of the parent category by accessing `category.parent_category_id`. If a category doesn’t have a parent, the relation and the ID will be `null`.
|
||||
- You can access the children of a category by expanding the `category_children` relation and accessing `category.category_children`. If a category doesn’t have children, the relation will be an empty array. By default, when expanding this relation in Product Category endpoints, only the immediate child categories are returned. If you want to get the entire heirarchy of child categories, you must pass the `include_descendants_tree` flag to the endpoint setting its value to `true`.
|
||||
- You can access the children of a category by expanding the `category_children` relation and accessing `category.category_children`. If a category doesn’t have children, the relation will be an empty array. By default, when expanding this relation in Product Category endpoints, only the immediate child categories are returned. If you want to get the entire hierarchy of child categories, you must pass the `include_descendants_tree` flag to the endpoint setting its value to `true`.
|
||||
|
||||
Aside from these relations, the `mpath` attribute, which is a [Materialized Path](https://typeorm.io/tree-entities#materialized-path-aka-path-enumeration) that is automatically generated by Typeorm, can be used to query deep trees faster.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
description: 'Learn how to implement user profile management features using the admin APIs. This includes user authentication, updating the profile, and reseting the password.'
|
||||
description: 'Learn how to implement user profile management features using the admin APIs. This includes user authentication, updating the profile, and resetting the password.'
|
||||
addHowToData: true
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user