Fixed InnerSource casing and changed formatting

patterns/1-initial/overcoming-project-management-time-pressures.md

@@ -1,6 +1,6 @@
 ## Title
 
-Time Constraints Hamper Inner Source Progress  
+Time Constraints Hamper InnerSource Progress  
 
 ## Patlet
 
@@ -16,26 +16,32 @@ Customer deadlines and delivery commitments for feature content do not change.
 
 ## Forces
 
-- Aggressive roadmaps for delivery
-- Project management concern that engagement will lead to missed deadlines
-- Project management concern that Code contribution and/or mentoring may lead to dilution of subject matter expert time spent on their own projects (other teams may require their time).
+❎ Aggressive roadmaps for delivery
 
-+ Elimination of rewriting common code saves time (write once, use many times)
-+ Crowd-based testing and debugging saves time (and improves quality)
-+ The collaboration and synergy of inner sourcing can generate new, innovative features  .
-+ Test Driven Development could mitigate some of the above forces
+❎ Project management concern that engagement will lead to missed deadlines
+
+❎ Project management concern that Code contribution and/or mentoring may lead to dilution of subject matter expert time spent on their own projects (other teams may require their time).
+
+
+✔️ Elimination of rewriting common code saves time (write once, use many times)
+
+✔️ Crowd-based testing and debugging saves time (and improves quality)
+
+✔️ The collaboration and synergy of inner sourcing can generate new, innovative features 
+
+✔️ Test Driven Development could mitigate some of the above forces
 
 ## Solutions
 
-- Known pattern: temporary fork by product team, merging changes back later to component team
+- Known pattern: Temporary fork by product team, merging changes back later to component team
 - Known anti-pattern: surreptitious temporary fork, no communication
 - New Pattern: Pre-pull request (prior to release), to ensure component team has buy-in, to avoid breakage for temporary fork
-- Allocate time into Development sprint/release schedules to allow for inner sourcing
-- Provide education to product owners and Development leads regarding time saving benefits of Inner Source
+- Allocate time into Development sprint/release schedules to allow for InnerSource
+- Provide education to product owners and Development leads regarding time saving benefits of InnerSource
 
 ## Resulting Context
 
-Time is allotted in the schedule for inner sourcing. Less duplicative development due to availability of reusable code. (No negative impact on customer deadlines or content delivery commitments.)
+Time is allotted in the schedule for InnerSource. Less duplicative development due to availability of reusable code. (No negative impact on customer deadlines or content delivery commitments.)
 
 ## Known Instances