Adding WellSky as a Known Instance to the Core Team pattern (#492)

Adding WellSky as a Known Instance to the Core Team pattern

Author: spier

patterns/1-initial/incubator-pipeline.md

@@ -14,7 +14,7 @@ The team managing the shared code library needs a way to allow InnerSource contr
 
 ## Story
 
-See [Culture, Behaviors, and InnerSource. A three-part blog series. 3 of 3](https://www.linkedin.com/pulse/culture-behaviors-innersource-three-part-blog-series-3-gil-yehuda/) for the conceptual inspiration for this pattern. 
+See [Culture, Behaviors, and InnerSource. A three-part blog series. 3 of 3](https://www.linkedin.com/pulse/culture-behaviors-innersource-three-part-blog-series-3-gil-yehuda/) for the conceptual inspiration for this pattern.
 
 _Note: This may be replaced with a direct story from the dev team who implemented this pattern. Watch this space._
 
@@ -86,4 +86,3 @@ Initial
 * John Sibo
 * Jennifer Skov
 * John Yopp
-

patterns/2-structured/core-team.md

@@ -95,7 +95,8 @@ The core team fills those gaps and greases the wheels so that the contribution e
 
 ## Known Instances
 
-Nike implemented this pattern to manage the InnerSource effort around its reusable CI/CD pipelines.
+* **Nike** implemented this pattern to manage the InnerSource effort around its reusable CI/CD pipelines.
+* **WellSky** established a Core Team for a key project. This allowed them to scale their InnerSource contributions to that project significantly - see [Wide-Scaled InnerSource with a Core Team](https://www.youtube.com/watch?v=kgxexjYdhIc).
 
 ## Status