Clarified the priority of a refactoring.

Author: jbrains

Diff for: documents/inbox.md

@@ -1,5 +1,10 @@
 # Today's session plan
 
+- Clean up before moving on:
+  - **Stop reusing a single instance of `PurchaseInProgress` to represent the purchase in progress. Maintaining the state has already become too complicated!**
+    - The class and one of its properties have the same name. Improve this _somehow_.
+    - Make the lifecycle of the Purchase in Progress more obvious in the API. For example: Purchase.begin() returns PurchaseInProgress; purchaseInProgress.complete() returns PurchaseInfo.
+  - Can we compute `isPurchaseInProgress` without maintaining a separate state value?
 - Print a receipt
   - What happens if we have a total with no items? scenario
   - Print the barcode with each item in the receipt
@@ -9,11 +14,6 @@
   - Add a timestamp for the receipt
   - Line up all the decimal points
   - Defect: excessive whitespace when requesting a receipt for an empty Purchase.
-  - Clean up before moving on:
-    - **Stop reusing a single instance of `PurchaseInProgress` to represent the purchase in progress. Maintaining the state has already become too complicated!**
-      - The class and one of its properties have the same name. Improve this _somehow_.
-      - Make the lifecycle of the Purchase in Progress more obvious in the API. For example: Purchase.begin() returns PurchaseInProgress; purchaseInProgress.complete() returns PurchaseInfo.
-    - Can we compute `isPurchaseInProgress` without maintaining a separate state value?
 
 # Inbox