docs: general fixes to cart and order concept docs (medusajs#13270)

Author: shahednasser

www/apps/book/public/llms-full.txt

@@ -4,28 +4,42 @@ export const metadata = {
 
 # {metadata.title}
 
-In this document, you’ll get an overview of the main concepts of a cart.
+In this document, you’ll learn about the main concepts related to carts in Medusa.
 
-## Shipping and Billing Addresses
+## Cart
 
-A cart has a shipping and billing address. Both of these addresses are represented by the [Address data model](/references/cart/models/Address).
+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 diagram showcasing the relation between the Cart and Address data models](https://res.cloudinary.com/dza7lstvk/image/upload/v1711532392/Medusa%20Resources/cart-addresses_ls6qmv.jpg)
+A cart holds informations about:
+
+- The items the customer wants to buy.
+- The customer's shipping and billing addresses.
+- The shipping methods used to fulfill the items after purchase.
+- The payment method and information necessary to complete the purchase.
+    - These are stored and handled by the [Payment Module](../../payment/page.mdx).
 
 ---
 
 ## Line Items
 
 A line item, represented by the [LineItem](/references/cart/models/LineItem) data model, is a quantity of a product variant added to the cart. A cart has multiple line items.
 
-A line item stores some of the product variant’s properties, such as the `product_title` and `product_description`. It also stores data related to the item’s quantity and price.
-
 <Note>
 
 In the Medusa application, a product variant is implemented in the [Product Module](../../product/page.mdx).
 
 </Note>
 
+A line item stores some of the product variant’s properties, such as the `product_title` and `product_description`. It also stores data related to the item’s quantity and price.
+
+---
+
+## Shipping and Billing Addresses
+
+A cart has a shipping and billing address. Both of these addresses are represented by the [Address data model](/references/cart/models/Address).
+
+![A diagram showcasing the relation between the Cart and Address data models](https://res.cloudinary.com/dza7lstvk/image/upload/v1711532392/Medusa%20Resources/cart-addresses_ls6qmv.jpg)
+
 ---
 
 ## Shipping Methods

www/apps/resources/app/commerce-modules/cart/concepts/page.mdx

@@ -1,28 +1,30 @@
 export const metadata = {
-  title: `Item Fulfillment`,
+  title: `Item Fulfillment Concepts`,
 }
 
 # {metadata.title}
 
-In this document, you’ll learn about the concepts of item fulfillment.
+In this document, you’ll learn about the concepts related to item fulfillment.
 
 ## Fulfillment Data Model
 
 A fulfillment is the shipping and delivery of one or more items to the customer. It’s represented by the [Fulfillment data model](/references/fulfillment/models/Fulfillment).
 
+A fulfillment can be created to fulfill orders, [returns](../../order/return/), [exchanges](../../order/exchange/page.mdx), and [claims](../../order/claim/page.mdx).
+
 ---
 
 ## Fulfillment Processing by a Fulfillment Provider
 
-A fulfillment is associated with a fulfillment provider that handles all its processing, such as creating a shipment for the fulfillment’s items.
+A fulfillment is associated with a [fulfillment provider](../fulfillment-provider/page.mdx) that handles all its processing, such as creating a shipment for the fulfillment’s items.
 
-The fulfillment is also associated with a shipping option of that provider, which determines how the item is shipped.
+The fulfillment is also associated with a [shipping option](../shipping-option/page.mdx) of that provider, which determines how the item is shipped.
 
 ![A diagram showcasing the relation between a fulfillment, fulfillment provider, and shipping option](https://res.cloudinary.com/dza7lstvk/image/upload/v1712331947/Medusa%20Resources/fulfillment-shipping-option_jk9ndp.jpg)
 
 ---
 
-## data Property
+## data Property of Fulfillment Data Model
 
 The `Fulfillment` data model has a `data` property that holds any necessary data for the third-party fulfillment provider to process the fulfillment.
 
@@ -32,7 +34,7 @@ For example, the `data` property can hold the ID of the fulfillment in the third
 
 ## Fulfillment Items
 
-A fulfillment is used to fulfill one or more items. Each item is represented by the `FulfillmentItem` data model.
+A fulfillment is used to fulfill one or more items. Each item is represented by the [FulfillmentItem data model](/references/fulfillment/models/FulfillmentItem).
 
 The fulfillment item holds details relevant to fulfilling the item, such as barcode, SKU, and quantity to fulfill.
 
@@ -42,14 +44,14 @@ The fulfillment item holds details relevant to fulfilling the item, such as barc
 
 ## Fulfillment Label
 
-Once a shipment is created for the fulfillment, you can store its tracking number, URL, or other related details as a label, represented by the `FulfillmentLabel` data model.
+Once a shipment is created for the fulfillment, you can store its tracking number, URL, or other related details as a label, represented by the [FulfillmentLabel data model](/references/fulfillment/models/FulfillmentLabel).
 
 ---
 
 ## Fulfillment Status
 
-The `Fulfillment` data model has three properties to keep track of the current status of the fulfillment:
+The [Fulfillment data model](/references/fulfillment/models/Fulfillment) has three properties to determine the current status of the fulfillment:
 
-- `packed_at`: The date the fulfillment was packed. If set, then the fulfillment has been packed.
-- `shipped_at`: The date the fulfillment was shipped. If set, then the fulfillment has been shipped.
-- `delivered_at`: The date the fulfillment was delivered. If set, then the fulfillment has been delivered.
+- `packed_at`: The date the fulfillment was packed. If set, the fulfillment has been packed.
+- `shipped_at`: The date the fulfillment was shipped. If set, the fulfillment has been shipped.
+- `delivered_at`: The date the fulfillment was delivered. If set, the fulfillment has been delivered.

www/apps/resources/app/commerce-modules/fulfillment/item-fulfillment/page.mdx

@@ -10,11 +10,11 @@ export const metadata = {
 
 # {metadata.title}
 
-In this document, you'll learn about the options of the Fulfillment Module.
+In this document, you'll learn about the options of the Fulfillment Module. You can pass these options in `medusa-config.ts`.
 
 ## providers
 
-The `providers` option is an array of fulfillment module providers.
+The `providers` option is an array of [Fulfillment Module Providers](../fulfillment-provider/page.mdx).
 
 When the Medusa application starts, these providers are registered and can be used to process fulfillments.
 
@@ -48,6 +48,6 @@ module.exports = defineConfig({
 
 The `providers` option is an array of objects that accept the following properties:
 
-- `resolve`: A string indicating either the package name  of the module provider or the path to it relative to the `src` directory.
+- `resolve`: A string indicating either the package name  of the module provider or its relative path.
 - `id`: A string indicating the provider's unique name or ID.
 - `options`: An optional object of the module provider's options.

www/apps/resources/app/commerce-modules/fulfillment/module-options/page.mdx

@@ -6,9 +6,22 @@ export const metadata = {
 
 In this document, you’ll learn about orders and related concepts
 
+## Order
+
+An order is a purchase made by a customer, either through the storefront or through the API. It is represented by the [Order data model](/references/order/models/Order).
+
+An order holds information about:
+
+- The purchased items.
+- The customer who made the order.
+    - This is stored and handled by the [Customer Module](../../customer/page.mdx).
+- Payment and shipping information
+
+---
+
 ## Order Items
 
-The items purchased in the order are represented by the [OrderItem data model](/references/order/models/OrderItem). An order can have multiple items.
+The items purchased in an order are represented by the [OrderItem data model](/references/order/models/OrderItem). An order can have multiple items.
 
 ![A diagram showcasing the relation between an order and its items.](https://res.cloudinary.com/dza7lstvk/image/upload/v1712304722/Medusa%20Resources/order-order-items_uvckxd.jpg)
 
@@ -28,7 +41,7 @@ Each shipping method is represented by the [OrderShippingMethod data model](/ref
 
 ### data Property
 
-When fulfilling the order, you can use a third-party fulfillment provider that requires additional custom data to be passed along from the order creation process.
+When fulfilling an order, you can use a third-party fulfillment provider that requires additional custom data to be passed along from the order creation process.
 
 The `OrderShippingMethod` data model has a `data` property. It’s an object used to store custom data relevant later for fulfillment.
 
@@ -38,7 +51,9 @@ The Medusa application passes the `data` property to the Fulfillment Module when
 
 ## Order Totals
 
-The order’s total amounts (including tax total, total after an item is returned, etc…) are represented by the [OrderSummary data model](/references/order/models/OrderSummary).
+An order’s total amounts (including tax total, total after an item is returned, etc…) are represented by the [OrderSummary data model](/references/order/models/OrderSummary).
+
+Refer to the [Retrieve Order Totals](../order-totals/page.mdx) guide to learn how to retrieve an order’s totals.
 
 ---
 
@@ -48,4 +63,4 @@ Payments made on an order, whether they’re capture or refund payments, are rec
 
 An order can have multiple transactions. The sum of these transactions must be equal to the order summary’s total. Otherwise, there’s an outstanding amount.
 
-Learn more about transactions in [this guide](../transactions/page.mdx).
+Refer to the [Transactions](../transactions/page.mdx) guide to learn more.