minor: small improvements

docs/decisions/0028-fixed-usd-pricing.rst

@@ -35,10 +35,14 @@ Consequences
 - The current flow of propagation of pricing information to Ecommerce will remain as is.
 - Analytics/Data teams will need to ensure that they track Enterprise Customers' purchases against the fixed price appropriately.
 
-
 Alternatives Considered
 -------------------------
 
-It would have been preferable to add this field at the Seat level somehow, and not clutter the CourseRun model unnecessarily.
-However, due to some historical reasons, Executive Education courses (for which we need this functionality), only have unpaid
-seats. It would be confusing to add pricing information to an unpaid seat.
+- It would have been preferable to add this field at the Seat level somehow, and not clutter the CourseRun model unnecessarily.
+  However, due to some historical reasons, Executive Education courses (for which we need this functionality), only have unpaid
+  seats. It would be confusing to add pricing information to an unpaid seat.
+
+- The field could have been integrated at the course level, aligning with the current discovery flows where the course price (CourseEntitlement)
+  is applied to all course runs. However, this approach does not accommodate pricing at the course run level, which has been a significant
+  issue for discovery users in the past. Although there are some workarounds, such as manually adjusting prices in the database, these solutions
+  are both cumbersome and inefficient.