diff --git a/docs/decisions/0012-enterprise-program-inclusion-boolean.rst b/docs/decisions/0012-enterprise-program-inclusion-boolean.rst
index 612fe93caf..72a15347a2 100644
--- a/docs/decisions/0012-enterprise-program-inclusion-boolean.rst
+++ b/docs/decisions/0012-enterprise-program-inclusion-boolean.rst
@@ -4,7 +4,7 @@ Adding Subscription Inclusion toggle to Publisher/Discovery
 Status
 ======
 
-In progress
+Accepted (2022)
 
 Context
 =======
@@ -12,21 +12,17 @@ Context
 Our edX catalog has many subsets, which add distinctions onto which are allowed to be enrolled 
 in by our enterprise customers. 
 
-- Enterprise Catalog: The entirety of the enrollable edX courses**
-- Subscription Catalog: A subset of the Enterprise Catalog including self-paced courses from 
-participating partners. Sometimes referred to as OC Catalog 
-- B2B Subscription Catalog: A subset of the Subscription Catalog**
+- Enterprise Catalog: The entirety of the enrollable edX courses (excluding some select partners)
+- Subscription Catalog: A subset of the Enterprise Catalog including self-paced courses from participating partners. Sometimes, this is referred to as OC Catalog.
+- B2B Subscription Catalog: A subset of the Subscription Catalog (excluding some select partners)
 
-** Does exclude some select partners
 
 Currently, our system for subscription tagging is brittle and relies on communication between 
 two individuals, which leaves us open to a risk multiple issues including:
 
 - Data Integrity: We copy or pull data from multiple different platforms
-- Course Key Tagging: Recently published courses are excluded as the process is manual and 
-is therefore time-gapped
-- Source of Truth/SME Ownership: Current process is owned by one (overworked) member of 
-enterprise and not owners of partner relationships 
+- Course Key Tagging: Recently published courses are excluded as the process is manual and is therefore time-gapped
+- Source of Truth/SME Ownership: Current process is owned by one (overworked) member of enterprise and not owners of partner relationships
 
 The full process must be repeated on a weekly basis and whenever a new partner is included 
 in subscriptions to ensure that the catalog accurately reflects courses that should be included
@@ -38,8 +34,9 @@ Decision
 
 This proposal will change this process so that subscription tagging is done at the Publisher
 level. This will enable us to remove the necessity of a manual process by using a binary flag
-to tag a subscription course within the metadata. In the future, querying for subscription 
-courses through a course field will allow us to refine a particular catalog if we choose to
+to tag a subscription course within the metadata.
+
+In the future, querying for subscription courses through a course field will allow us to refine a particular catalog if we choose to
 pursue an opportunity like specialized (sub) subscription catalogs. Also, moving away from 
 Google Sheets gives various stakeholders visibility into which partners participate in the 
 catalog. This will pave the way for work that can be done in the future to more fully 
@@ -47,17 +44,19 @@ integrate SFDC with Publisher and truly automate this process.
 
 The types of Partner participation in subscriptions are as follows: 
 
-- Traditional: All courses/programs in both the OCE and B2B catalog 
-    Excludes MicroMasters, instructor-led courses, and any specific courses the org wants excluded
+- Traditional: All courses/programs in both the OCE and B2B catalog
+
+  - Excludes MicroMasters, instructor-led courses, and any specific courses the org wants excluded
+
 - Not Participating: None of the partners courses will be available in the subs catalog
 
 The tagging system will be structured by inheritance from both the organization level and
 the course level. If the organization’s inclusion is set to false, none of the courses or 
-programs from this organization will be included in the catalog. If the org flag is set to true, 
-partners do have the option of opting out of courses, which will be manually set for every course
-they wish to exclude. For inclusion flags for both program and course run, this is a calculated 
-field, not manually set like organization and course. For programs, if every course in the program
-is included in that catalog, we will set the flag to true. Course runs are set to true only if
+programs from this organization will be included in the catalog.
+
+If the org flag is set to true, partners do have the option of opting out of courses, which will be manually set for every course
+they wish to exclude. The inclusion flag for both program and course run is a calculated field and not manually set like organization and course.
+For programs, if every course in the program is included in that catalog, we will set the flag to true. Course runs are set to true only if
 the parent course is set to true and the course run is not instructor-led. 
 
 There are some existing organizations with unique customizations. Because of the value-add of