Fix links in Repository Activity Score (2nd try) (#411)

* Point GitHub links in "Repository Activity Score" to the redirect target.
* Prevent further links checks for failing GitHub links (by excluding those links in the GHA workflow)
* "Crossing the InnerSource Chasm": Fix link to a pattern that got renamed
* "Crossing the InnerSource Chasm": Fix some typos

Author: spier

.github/workflows/link-checker.yml

@@ -21,6 +21,6 @@ jobs:
       id: lc
       uses: peter-evans/link-checker@v1
       with:
-        args: -v -d . -x "http://creativecommons.org/licenses|https://isc-inviter.herokuapp.com|https://github.com/rcs/rcs-viewer/pull/81|fearlesschangepatterns.com|https://ulir.ul.ie/bitstream/handle/10344/4443/Stol_2014_inner.pdf" README.md patterns/ -r
+        args: -v -d . -x "http://creativecommons.org/licenses|https://isc-inviter.herokuapp.com|https://github.com/rcs/rcs-viewer/pull/81|fearlesschangepatterns.com|https://ulir.ul.ie/bitstream/handle/10344/4443/Stol_2014_inner.pdf|https://docs.github.com/en/rest/metrics/statistics|https://docs.github.com/en/rest/search#search-repositories" README.md patterns/ -r
     - name: Fail if there were link errors
       run: exit ${{ steps.lc.outputs.exit_code }}

patterns/1-initial/crossing-chasm.md

@@ -69,7 +69,7 @@ written solutions with people following your trail.
 * Share external material (bonus points if that is material that colleagues
 created earlier: talks, blog articles, book chapters, magazine articles, videos
 etc.)
-* Co-create a document of shared [InnerSource Principles](../1-initial/explicit-innersource-principles.md).
+* Co-create a document of shared [InnerSource Principles](../2-structured/document-your-guiding-principles.md).
 
 ### Steps for pragmatists
 
@@ -85,19 +85,19 @@ etc.)
 hires.
 * Integrate any tooling and any experiments you have run into established
 company structures (e.g. GitHub/ GitLab instances are under a regular plan,
-accounts are easy to create and integrated with e.g. coporate single sign on
+accounts are easy to create and integrated with e.g. corporate single sign-on
 solutions, in-house support can provide help for these tools).
 * Provide low effort opportunities for learning (e.g. put little riddles in your
 coffee kitchen or whatever the digital alternative is for your company.)
 * Ship bite sized learning pieces to inboxes.
-* Pull in external expertise - sometimes in house expertise counts much less
+* Pull in external expertise - sometimes in-house expertise counts much less
 than external statements.
 
 ### Steps for laggards
 
 * Incorporate InnerSource into career competencies description.
 
-## Resulting context
+## Resulting Context
 
 * The InnerSource initiative can reach teams with various innovation
 preferences.

patterns/2-structured/repository-activity-score.md

@@ -46,7 +46,7 @@ The repository activity score is a numeric value that represents the (GitHub) ac
 In addition, it considers activity parameters like last update and creation date of the repo to give young projects with a lot of traction a boost.
 Projects with contributing guidelines, active participation stats, and issues (public backlog) receive a higher ranking as well.
 
-All of this can be fetched and calculated automatically using the result set of the [GitHub search API](https://docs.github.com/en/rest/reference/search#search-repositories) and [GitHub statistics API](https://docs.github.com/en/rest/reference/metrics#statistics). Other code versioning systems like BitBucket, Gitlab, Gerrit can be integrated as well if a similar API is available.
+All of this can be fetched and calculated automatically using the result set of the [GitHub search API](https://docs.github.com/en/rest/search#search-repositories) and [GitHub statistics API](https://docs.github.com/en/rest/metrics/statistics). Other code versioning systems like BitBucket, Gitlab, Gerrit can be integrated as well if a similar API is available.
 
 The code below assumes the variable `repo` contains an entity fetched from the GitHub `search` API and the `participation` object contains an entity from the GitHub `stats/participation` API.