fixing some more broken links (those files won't be constantly checked with the link checker)

Author: spier

meta/innersource-spelling.md

@@ -10,7 +10,7 @@ We encourage you to use the word as a proper noun (like “We use InnerSource in
 
 We favor the spelling **InnerSource**, for the following reasons:
 
-1. That’s the way Tim O’Reilly [spelled it in 2000][opengl_1200] (he was into Perl and camel-case was a thing). Also see the [Foreword of the Adopting InnerSource book](foreword_AdoptingInnerSource) for more of Tim O’Reilly's own words on the topic. 
+1. That’s the way Tim O’Reilly [spelled it in 2000][opengl_1200] (he was into Perl and camel-case was a thing). Also see the [Foreword of the Adopting InnerSource book][foreword_AdoptingInnerSource] for more of Tim O’Reilly's own words on the topic. 
 2. If you set up side-by-side Google searches for “Inner Source” and “InnerSource” you will find that you get more hits on the former term, by only 1% of them have anything to do with what we call InnerSource. The latter term will be 100% cogent to your inquiry.
 3. The OSI was [denied trademark on the term “open source”][no-open-source-trademark] because it was made up of two common and unrelated terms. “InnerSource” on the other hand is a new word.
 

meta/markdown-info.md

@@ -2,7 +2,7 @@
 
 A markdown file is a plain ASCII text file that is meant to be easy to read in plaintext, while also being pretty once rendered.
 
-It is similar to the format that many wiki's have. As an example, you can see [this rendered pattern](../dedicated-community-leader.md) of ours also [in plain text](/../../raw/master/dedicated-community-leader.md). You can do this for any markdown file by clicking the ``Raw`` button when viewing a file online.
+It is similar to the format that many wiki's have. As an example, you can see [this rendered pattern](../patterns/2-structured/dedicated-community-leader.md) of ours also [in plain text](/../../raw/master/patterns/2-structured/dedicated-community-leader.md). You can do this for any markdown file by clicking the ``Raw`` button when viewing a file online.
 
 The ASCII is marked up in a standard format. Here are two cheatsheets for that format:
 

meta/technical-git-howto.md

@@ -1,14 +1,14 @@
 # Command-line git steps for creating a new Pattern
 
-If you want to contribute a new pattern, the workflow is done through Branches and Pull Requests (PR's). You can see the available branches on [the branches URL](https://github.com/InnerSourceCommons/InnerSourcePatterns/branches/all) and existing PR's on the [Pull Request page](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls). Branches are meant to separate content, so that multiple people can work all at once. Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern. 
+If you want to contribute a new pattern, the workflow is done through Branches and Pull Requests (PR's). You can see the available branches on [the branches URL](https://github.com/InnerSourceCommons/InnerSourcePatterns/branches/all) and existing PR's on the [Pull Request page](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls). Branches are meant to separate content, so that multiple people can work all at once. Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern.
 
 There are indeed multiple ways to start a discussion:
 
 * Send a Pull Request for your branch and the maintainers will receive a notification.
 * Create an Issue and ask for comments from some of the maintainers. You can mention them using the '@' symbol prior to their github nickname.
 * Add reviewers to the Pull Request on the website - this sends requests to review your work
 
-New patterns should use, as their base, the [pattern template file](meta/pattern-template.md). 
+New patterns should use, as their base, the [pattern template file](pattern-template.md).
 
 Please, when starting a new pattern, make sure that it does not already exist. Take a look at some of the [existing patterns in this repository](/README.md#reviewed-patterns-proven-and-reviewed).
 
@@ -69,7 +69,7 @@ branch with a new pattern named as foo should be as follows:
 $ git checkout -b pattern/foo
 ```
 
-You are now in the 'pattern/foo' branch. When you create a new branch, the files 
+You are now in the 'pattern/foo' branch. When you create a new branch, the files
 in the directory might appear to have changed. Each branch can have slightly different content, and that is intentional. If you need to go back to the 'master' branch or another branch, you can easily 'checkout' to those as follows:
 
 ```
@@ -87,7 +87,7 @@ $ git checkout -b pattern/ewoks-do-not-hunt
 $ touch ewoks-do-not-hunt.md
 ```
 
-You can fill your [markdown](meta/markdown-info.md) file with the [pattern template text](meta/pattern-template.md) and begin to fill it in with your pattern.
+You can fill your [markdown](markdown-info.md) file with the [pattern template text](pattern-template.md) and begin to fill it in with your pattern.
 
 Once our pattern file is ready to go, we need to add the file to the repo and
 commit that change to our new branch.