docs: edits and fixes to commerce module docs (#7468)

Apply edits and fixes to the commerce modules docs

www/apps/resources/app/commerce-modules/order/transactions/page.mdx

@@ -6,30 +6,19 @@ export const metadata = {
 
 # {metadata.title}
 
-In this document, you’ll learn about an order’s transactions and usefulness.
+In this document, you’ll learn about an order’s transactions and its use.
 
 ## What is a Transaction?
 
-A transaction represents any order payment process, such as capturing or refunding an amount. It’s represented by the `Transaction` data model.
+A transaction represents any order payment process, such as capturing or refunding an amount. It’s represented by the [Transaction data model](/references/order/models/Transaction).
 
 The transaction’s main purpose is to ensure a correct balance between paid and outstanding amounts.
 
 ---
 
-## Transaction Reference
-
-The Order Module doesn’t provide payment processing functionalities, so it doesn’t store payments that can be processed. For that, use the Payment Module or custom logic.
-
-The `Transaction` data model has two fields that determine which data model and record holds the actual payment’s details:
-
-- `reference`: indicates the table’s name in the database. For example, `payment` if you’re using the Payment Module.
-- `reference_id`: indicates the ID of the record in the table. For example, `pay_123`.
-
----
-
 ## Checking Outstanding Amount
 
-The order’s total is stored in the `OrderSummary`'s `total` field. To check the outstanding amount of the order, the transaction amounts of an order are summed. Then:
+The order’s total is stored in the `OrderSummary`'s `total` field. To check the outstanding amount of the order, its transaction amounts are summed. Then, the following conditions are checked:
 
 <Table>
   <Table.Header>
@@ -77,3 +66,14 @@ The order’s total is stored in the `OrderSummary`'s `total` field. To check th
     </Table.Row>
   </Table.Body>
 </Table>
+
+---
+
+## Transaction Reference
+
+The Order Module doesn’t provide payment processing functionalities, so it doesn’t store payments that can be processed. For that, use the Payment Module or custom logic.
+
+The `Transaction` data model has two fields that determine which data model and record holds the actual payment’s details:
+
+- `reference`: indicates the table’s name in the database. For example, `payment` if you’re using the Payment Module.
+- `reference_id`: indicates the ID of the record in the table. For example, `pay_123`.