Reformatting of 'Improve Findability'. fix InnerSource spelling.

Author: spier

README.md

@@ -53,7 +53,7 @@ The below lists all known patterns. They are grouped into three [maturity levels
 ### Maturity Level 1: Initial
 
 * [Modular Code](patterns/1-initial/modular-code.md) - *Management does not want to spend the extra resources needed to develop modular components and make them available in a visible repository for others to use.*
-* [Improve Findability](patterns/1-initial/improve-findability.md) - *People can't find the internally developed solutions that they need due to poor naming conventions. This causes frustration in finding inner source solutions and a reduction in code reuse.*
+* [Improve Findability](patterns/1-initial/improve-findability.md) - *People can't find the internally developed solutions that they need due to poor naming conventions. This causes frustration in finding InnerSource solutions and a reduction in code reuse.*
 * [Overcoming Project Management Time Pressures](patterns/1-initial/overcoming-project-management-time-pressures.md) - *Project management believes timeline pressure and commitments on feature content does not allow for developers to spend the time needed to develop shareable code and provide support.*
 * [Introducing Metrics in InnerSource](patterns/1-initial/introducing-metrics-in-innersource.md) - *Involve all stakeholders in designing and interpreting metrics to measure the current status in terms of health and performance of the InnerSource initiative.*
 * [Shared Code Repo Different from Build Repo](patterns/1-initial/shared-code-repo-different-from-build-repo.md) - *Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.*

patterns/1-initial/improve-findability.md

@@ -2,18 +2,13 @@
 
 Improve Findability
 
-## Also Known As
-
-- Badly Named Piles
-- Poor Naming Conventions
-
 ## Patlet
 
-TBD
+People can't find the internally developed solutions that they need due to poor naming conventions. This causes frustration in finding InnerSource solutions and a reduction in code reuse.
 
 ## Problem
 
-People can't find the internally developed solutions that they need due to poor naming conventions.
+People can't find the internally developed solutions that they need due to poor naming conventions. This causes frustration in finding InnerSource solutions and a reduction in code reuse.
 
 ## Context
 
@@ -36,14 +31,14 @@ To help improve findability for inner source projects:
 - Include keywords in project descriptions.
 - Apply tagging to repositories (validated).
 - Use labels where possible.
-- If possible, pull repository names, descriptions, and README.md files into the search engine (not the code itself).
+- If possible, pull repository names, descriptions, and `README.md` files into the search engine (not the code itself).
 - Instate a concierge service (guide) to help product people find stuff. (This approach might not scale, but could be helpful at the beginning of a program.)
 
 <img alt="Poor naming conventions" src="/assets/img/poornamingconventions.jpg" width="70%">
 
 ## Known Instances
 
-None known as of yet---this is a pattern idea until it is proven.
+None known as of yet - this is a pattern idea until it is proven.
 
 ## Desired Resulting Context
 
@@ -67,3 +62,8 @@ None known as of yet---this is a pattern idea until it is proven.
 - Erin Bank (CA Technologies)
 - Padma Sudarsan (Nokia)
 - Tim Yao (Nokia)
+
+## Also Known As
+
+- Badly Named Piles
+- Poor Naming Conventions