Shortening some pattern titles to make for nicer links (#239)

Shortening some pattern titles to make for nicer links in the book. Moving the longer titles to the Alias section where that seemed useful.

Author: spier

README.md

@@ -37,7 +37,7 @@ The below lists all known patterns. They are grouped into three [maturity levels
 * [Praise Participants](patterns/2-structured/praise-participants.md) - *Thank contributors effectively to engender further engagement from them and to encourage others to contribute*
 * [Repository Activity Score](patterns/2-structured/repository-activity-score.md) - *The repository activity score is a numeric value that represents the (GitHub) activity of an InnerSource project.*
 * [Review Committee](patterns/2-structured/review-committee.md) - *A formal review committee is setup within an org to "officiate" particular inner source projects with resources, etc.*
-* [Service vs. library: It's inner source, not inner deployment](patterns/2-structured/service-vs-library.md) - *Teams in a DevOps environment may be reluctant to work across team boundaries on common code bases due to ambiguity over who will be responsible for responding to service downtime. The solution is to realize that often it's
+* [Service vs. Library](patterns/2-structured/service-vs-library.md) - *Teams in a DevOps environment may be reluctant to work across team boundaries on common code bases due to ambiguity over who will be responsible for responding to service downtime. The solution is to realize that often it's
 possible to either deploy the same service in independent environments with separate escalation chains in the event of service downtime or factor a lot of shared code out into one library and collaborate on that.*
 * [Trusted Committer](patterns/2-structured/trusted-committer.md) - *Many inner-source projects will find themselves in a situation where they consistently receive feedback, features, and bug-fixes from contributors. In these situations project maintainers seek ways to recognize and reward the work of the contributor above and beyond single contributions.*
 
@@ -50,9 +50,9 @@ possible to either deploy the same service in independent environments with sepa
 * [Open Source Trumps InnerSource](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/46) - *People find the InnerSource project but, after all things are considered, even if the InnerSource component meets their needs, they still go with the open source component.*
 * [Start as Experiment](patterns/2-structured/start-as-experiment.md) - *An inner source initiative is considered but not started, because management is unsure about its outcome and therefore unwilling to commit to the investment.*
 * [Include Product Owners](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/71) - *Key Performance Indicators (KPIs) for Product Owners are primarily product focused, and don't consider areas such as collaborative development. This results in a lower level of engagement with inner source projects.*
-* [Provide standard base documentation through a README](patterns/2-structured/project-setup/base-documentation.md) - *New contributors to an InnerSource project have a hard time figuring out who maintains the project, what to work on, and how to contribute. Providing documentation in standard files like README.md/CONTRIBUTING.md enables a self service process for new contributors, so that they can find the answers to the most common questions on their own.*
-* [Issue tracker use cases](patterns/2-structured/project-setup/issue-tracker.md) - *The InnerSource host team fails to make not only plans and progress but also context for changes transparent. This is solved by increasing the use cases for the project issue tracker to also serve brainstorming, implementation discussion, and feature design.*
-* [Communication tooling](patterns/2-structured/project-setup/communication-tooling.md) - *An InnerSource project is being used outside the original development team but users are having trouble getting help and getting in touch with the project team. The idea is to setup and document standard communication tooling that allows for discussions to become visible, archived and searchable.*
+* [Standard Base Documentation](patterns/2-structured/project-setup/base-documentation.md) - *New contributors to an InnerSource project have a hard time figuring out who maintains the project, what to work on, and how to contribute. Providing documentation in standard files like README.md/CONTRIBUTING.md enables a self service process for new contributors, so that they can find the answers to the most common questions on their own.*
+* [Issue Tracker Use Cases](patterns/2-structured/project-setup/issue-tracker.md) - *The InnerSource host team fails to make not only plans and progress but also context for changes transparent. This is solved by increasing the use cases for the project issue tracker to also serve brainstorming, implementation discussion, and feature design.*
+* [Communication Tooling](patterns/2-structured/project-setup/communication-tooling.md) - *An InnerSource project is being used outside the original development team but users are having trouble getting help and getting in touch with the project team. The idea is to setup and document standard communication tooling that allows for discussions to become visible, archived and searchable.*
 
 ### Maturity Level 1: Initial
 

patterns/2-structured/maturity-model.md

@@ -1,6 +1,6 @@
 ## Title
 
-Maturity model: Learn about InnerSource best practices
+Maturity Model
 
 ## Patlet
 
@@ -225,6 +225,10 @@ long term.
 
 ## Acknowledgements
 
+## Alias
+
+Maturity model: Learn about InnerSource best practices
+
 ## Status
 
 Drafted in September 2019

patterns/2-structured/project-setup/base-documentation.md

@@ -1,6 +1,6 @@
 ## Title
 
-Provide standard base documentation through a README
+Standard Base Documentation
 
 ## Patlet
 
@@ -152,6 +152,10 @@ Europace AG, Paypal Inc.
 
 ## Acknowledgements
 
+## Alias
+
+Provide standard base documentation through a README
+
 
 ## Status
 

patterns/2-structured/project-setup/communication-tooling.md

@@ -1,6 +1,6 @@
 ## Title
 
-Communication tooling
+Communication Tooling
 
 ## Patlet
 
@@ -65,21 +65,21 @@ personally back to official communication channels.
 
 ## Resulting Context
 
-Setting up and consistently using official asynchronous communication channels 
-helps create a base level of passive documentation that can be referenced again 
+Setting up and consistently using official asynchronous communication channels
+helps create a base level of passive documentation that can be referenced again
 when similar questions come up again.
 
 With communication happening in the open others can easily follow project
-progress and get active contributing. Others lurking and reading lowers the 
+progress and get active contributing. Others lurking and reading lowers the
 barrier to get involved raising the likelihood of receiving contributions.
 
 With questions being answered in public more people can add their perspective
-leading to a complete picture - this includes not only host team members, 
+leading to a complete picture - this includes not only host team members,
 but also users of the project.
 
 Keeping communication in asynchronous channels allows for participants on
 different schedules - either due to different time zones or due to different
-routines, meeting schedules, team routines - to meaningfully contribute to 
+routines, meeting schedules, team routines - to meaningfully contribute to
 the project.
 
 Answering questions in those channels means that not only other team members

patterns/2-structured/project-setup/issue-tracker.md

@@ -1,6 +1,6 @@
 ## Title
 
-Issue tracker use cases
+Issue Tracker Use Cases
 
 ## Patlet
 

patterns/2-structured/service-vs-library.md

@@ -1,5 +1,5 @@
 ## Title
-Service vs. library: It's inner source, not inner deployment
+Service vs. Library
 
 ## Patlet
 Teams in a DevOps environment may be reluctant to work across team boundaries on
@@ -88,3 +88,7 @@ Isabel Drost-Fromm
 ## Acknowledgements
 
 Thank you Tobias Gesellchen for review internal to Europace AG.
+
+## Alias
+
+Service vs. library: It's inner source, not inner deployment