dateCompleted -> dateOrdered for 4.x+

Author: AugustMiller

docs/commerce/4.x/orders-carts.md

@@ -8,7 +8,7 @@ updatedVersion: commerce/5.x/system/orders-carts.md
 
 Variants are added to a _cart_ that can be completed to become an _order_. Carts and orders are both listed in the control panel under **Commerce** → **Orders**.
 
-When we use the terms “cart” and “order”, we’re always referring to an [Order](commerce4:craft\commerce\elements\Order) element; a cart is simply an order that hasn’t been completed—meaning its `isCompleted` property is `false` and its `dateCompleted` is `null`.
+When we use the terms “cart” and “order”, we’re always referring to an [Order](commerce4:craft\commerce\elements\Order) element; a cart is simply an order that hasn’t been completed—meaning its `isCompleted` property is `false` and its `dateOrdered` is `null`.
 
 Typically, a cart is completed in response to a customer [making a payment](./making-payments.md)—or by satisfying other requirements you’ve defined through [configuration](./config-settings.md) or an [extension](./extend/README.md).
 
@@ -515,7 +515,7 @@ This number is usually best used as the customer-facing identifier of the order,
 The “Order Reference Number Format” is a mini Twig template that’s rendered when the order is completed. It can use order attributes along with Twig filters and functions. For example:
 
 ```twig
-{{ object.dateCompleted|date('Y') }}-{{ id }}
+{{ object.dateOrdered|date('Y') }}-{{ id }}
 ```
 
 Output:
@@ -534,7 +534,7 @@ The `seq()` function takes the following parameters:
 For example:
 
 ```twig
-{{ object.dateCompleted|date('Y') }}-{{ seq(object.dateCompleted|date('Y'), 8) }}
+{{ object.dateOrdered|date('Y') }}-{{ seq(object.dateOrdered|date('Y'), 8) }}
 ```
 
 Ouput:

docs/commerce/5.x/system/orders-carts.md

@@ -135,7 +135,7 @@ The _order reference_ is generated upon completing a cart using the store’s **
 The “Order Reference Number Format” is an [object template](/5.x/system/object-templates.md) that’s rendered when the order is completed. It can use order attributes along with Twig filters and functions. For example:
 
 ```twig
-{{ dateCompleted|date('Y') }}-{{ id }}
+{{ dateOrdered|date('Y') }}-{{ id }}
 ```
 
 Output:
@@ -154,7 +154,7 @@ The `seq()` function takes the following parameters:
 For example:
 
 ```twig
-{{ dateCompleted|date('Y') }}-{{ seq(dateCompleted|date('Y'), 8) }}
+{{ dateOrdered|date('Y') }}-{{ seq(dateOrdered|date('Y'), 8) }}
 ```
 
 Output:
@@ -168,7 +168,7 @@ In this example we’ve used the current year as the sequence name so we automat
 Sequences are global, so constructing keys that will not collide with others you may use in other fields or templates is essential to avoid gaps.
 
 ::: tip
-Order references cannot be relied upon for sorting. Use `.orderBy('dateCompleted DESC')` if you wish to display orders in reverse-chronological order.
+Order references cannot be relied upon for sorting. Use `.orderBy('dateOrdered DESC')` if you wish to display orders in reverse-chronological order.
 :::
 
 ### Creating Orders