Book Formatting Review (#308)

* Formatting fixes in Common Requirements: format the definition of a to-be-written pattern in the Resulting Context
* Fix some cross-references to other patterns
* Various formatting fixes and image fixes

Author: spier

assets/img/review-committee-sketch.jpg

@@ -41,10 +41,11 @@ In the example presented above, the supplier helps both customers realize that t
 
 This might require negotiating requirements changes with the customer.  The changes might also require involvement by the sales teams and product managers to get alignment on the requirements.  The customer might need incentives, such as discounts, to agree to the changes.
 
-A related pattern (to be written) is a circular story-writing exercise reported at one company employing Inner Sourcing.  
-The developers write a story to solve a problem in one way.  
+A related pattern [pattern to be written] is a circular story-writing exercise reported at one company employing InnerSource.  
 
-The program managers rewrite the story to better express their needs---keeping the essence the same. By the time it returns to developers though they don't recognize it as what they wanted to do in the first place and so balk at implementing it.  The solution to this pattern is to have more seats around the planning table so that story modifications are understood across the project not just in the developer or program manager camps.
+* The developers write a story to solve a problem in one way.  
+* The program managers rewrite the story to better express their needs - keeping the essence the same. By the time it returns to developers though they don't recognize it as what they wanted to do in the first place and so balk at implementing it.  
+* The solution to this pattern is to have more seats around the planning table so that story modifications are understood across the project not just in the developer or program manager camps.
 
 ## Known Instances
 

patterns/2-structured/common-requirements.md

@@ -97,7 +97,7 @@ They will provide a head-and-shoulders improvement in on-the-ground results over
 ## Status
 
 * Structured
-* Old status: Proven in multiple domains.
+* Proven in multiple domains.
 
 ## Authors
 

patterns/2-structured/crossteam-project-valuation.md

@@ -61,7 +61,7 @@ When used in combination with the InnerSource Portal pattern, the Gig Marketplac
 
 * A large financial services organization has used the creation of an InnerSource Gig Marketplace website to foster their InnerSource program.
 * SAP implemented the Gig Marketplace pattern - a new InnerSource program was added to the internal job platform where positions and similar offerings can be posted.
-* The Gig Marketplace pattern has been proven to work extremely well with the associated InnerSource Portal pattern in this context.  The InnerSource Portal increases awareness of specific projects currently underway while the Gig Marketplace advertises tasks of a certain type available to be worked on within those projects.
+* The Gig Marketplace pattern has been proven to work extremely well with the associated [InnerSource Portal](./innersource-portal.md) pattern in this context.  The InnerSource Portal increases awareness of specific projects currently underway while the Gig Marketplace advertises tasks of a certain type available to be worked on within those projects.
 
 ## Status
 

patterns/2-structured/gig-marketplace.md

@@ -177,7 +177,7 @@ Not only should feature development be owned by InnerSource teams - support and
 
 * SP-0: Support given by the core dev or support team. A business contract guaranties the support. There is no knowledge about the product outside the team.
 * SP-1: There are rules and regulations to formalize the support on the product, given by a dedicated supporting team.
-* SP-2: Support for InnerSource contributions is formalized through InnerSource patterns like [30 day warranty](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/master/patterns/2-structured/30-day-warranty.md) or [service vs. library](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/master/patterns/2-structured/service-vs-library.md).
+* SP-2: Support for InnerSource contributions is formalized through InnerSource patterns like [30 Day Warranty](./30-day-warranty.md) or [Service vs. Library](./service-vs-library.md).
 * SP-3: There are rules and regulations to formalize the support on the product, given by a mature community.
 
 **Culture**

patterns/2-structured/maturity-model.md

@@ -33,13 +33,17 @@ Any time someone gives to your inner source project, recognize them with a since
 
 For non-trivial contributions (all code contributions and also significant time contributions), say thank you via the following mechanisms:
 
-1. Call out the person by name in any chat location (e.g. _Slack_) where you organize your project activity.  Let everyone know what they did and thank them publicly.  Example:
+(1) Call out the person by name in any chat location (e.g. _Slack_) where you organize your project activity.  Let everyone know what they did and thank them publicly.  
+
+Example:
 
 > Everyone @here give a high-five to @andrew.clegg for updating the _rcs-viewer_ to the latest version of the _hebo-client_ (https://github.com/rcs/rcs-viewer/pull/81).
 Thanks for helping keep this library up-to-date, Andy!
 
-2. Send an email to them and their manager (cc'd) privately thanking them for the contribution.
-For code contributions often-times you can just forward the merge notification mail.  Example:
+(2) Send an email to them and their manager (cc'd) privately thanking them for the contribution.
+For code contributions often-times you can just forward the merge notification mail.  
+
+Example:
 
 > Hi, Andy, I want to thank you again for making this update.
 It may have been a small amount of time, but it's attention like this from each person that make the RCS project work for all of us.

patterns/2-structured/praise-participants.md

@@ -73,7 +73,7 @@ the implementation.
 
 ## See also
 
-Related to this pattern is the [Thirty day warranty](30-day-warranty.md) pattern that takes a different approach to solving the forces described above.
+Related to this pattern is the [30 Day Warranty](30-day-warranty.md) pattern that takes a different approach to solving the forces described above.
 
 ## Known Instances