text update

docs/content/introduction/governance-process.mdx

@@ -96,7 +96,7 @@ This phase is only relevant if you have written a [Jira Support Ticket (internal
 
 ## Phase 3a: Design system team fulfills the request
 
-This phase can only be achieved if the estimated time for the request is acceptable for you and your team and you are willing to wait for us to deliver it.
+This phase can only be achieved if the estimated time for the request is acceptable for you and your team and you are willing to wait for us to deliver it. ​In that case, you can follow the process below.
 
 <Columns columns={[5, 5]} space={4}>
   <div>
@@ -138,7 +138,7 @@ This phase can only be achieved if the estimated time for the request is accepta
 
 ## Phase 3b: Product team’s response if request can’t or won’t be fulfilled
 
-What if you cannot wait for us to deliver a request? Well, than you have to follow this process.
+What if you cannot wait for us to deliver a request, or we decide it doesn't meet our criteria for becoming part of the design system?​
 
 <Columns columns={[5, 5]} space={4}>
 <div>
@@ -148,15 +148,15 @@ What if you cannot wait for us to deliver a request? Well, than you have to foll
 
     - **No:** If the product team is no longer convinced of the need for the request, the process ends, and the product team re-examines their requirements.
 
-    **Step 2:** If the product team is still convinced of the need for the request, they begin building their own component or solution, receiving support from the design system team.
+    **Step 2:** If the product team is still convinced of the need for the request, they can choose to build their own component or solution, receiving support as needed​ from the design system team.
 
     **Step 3:** Throughout the development process, the product team frequently coordinates with the design system team to ensure alignment and adherence to guidelines.
 
-    **Step 4:** The product team ensures that all design tokens and sub-elements used in their solution are sourced from the design system to maintain consistency.
+    **Step 4:** The product team ensures that all design tokens and sub-elements used in their solution are sourced from the design system as much as possible to maintain consistency.
 
     **Step 5:** The product team takes ownership of the custom solution they have developed. They document the solution and maintain it.
 
-    **Step 6:** In the course of time we need to reflect if there has a viable existing alternative in Marigold become available?
+    **Step 6:** If, at some point, a viable alternative becomes available, the product team can decide to use it in place of their custom solution.
 
     - **Yes:** If a viable alternative becomes available in the design system, the product team removes their custom solution and implements the official one.