Fix #7 broken links

chapters/2-document-creation-information.md

@@ -272,7 +272,7 @@ Example:
 
 ## 2.9 Created <a name="2.9"></a>
 
-**2.9.1** Purpose: Identify when the SPDX file was originally created. The date is to be specified according to combined date and time in UTC format as specified in ISO 8601 standard. This field is distinct from the fields in section 7, which involves the addition of information during a subsequent review.
+**2.9.1** Purpose: Identify when the SPDX file was originally created. The date is to be specified according to combined date and time in UTC format as specified in ISO 8601 standard. This field is distinct from the fields in [section 8](8-annotations.md), which involves the addition of information during a subsequent review.
 
 **2.9.2** Intent: Here, the time stamp can serve as an indication as to whether the analysis needs to be updated.
 

chapters/appendix-I-SPDX-license-list.md

@@ -3,13 +3,14 @@
 The SPDX License List is a list of commonly found licenses and exceptions used for open source and other collaborative software. The purpose of the SPDX License List is to enable easy and efficient identification of such licenses and exceptions in an SPDX document (or elsewhere). The SPDX License List includes a standardized short identifier, full name for each license, vetted license text, other basic information, and a canonical permanent URL for each license and exception. By providing a short identifier, users can efficiently refer to a license without having to redundantly reproduce the full license. License exceptions can be used with the License Expression Syntax operator, "WITH" to create a license with an exception.
 
 * [License Exceptions][exceptions]: The list of commonly found exceptions to open source licenses, which can be used with the License Expression operator, "WITH" to create a license with an exception.
-* Master Files: The HTML pages you see here are generated from the master files for the SPDX License List. The master files include a spreadsheet listing all the licenses, deprecated licenses, and license exceptions; and the text for each license in a .txt file. These files are available in a Git repository.
+* [Master Files][master-files]: The HTML pages you see here are generated from the master files for the SPDX License List. The master files include a spreadsheet listing all the licenses, deprecated licenses, and license exceptions; and the text for each license in a .txt file. These files are available in a Git repository.
 * Overview: For general information about the SPDX License List, including principles for inclusion of a license and an explanation of the fields contained on the list.
 * [Matching Guidelines][matching]: Guidelines for what constitutes a license match to the SPDX License List. For licenses that include markup, the license text on the HTML pages here will display omitable text in blue and replaceable text in red (see Guideline #2 for more information).
 * [Request New License][new-license]: For instructions on how to propose additional licenses or license exceptions be added to the SPDX License List.
 
 [exceptions]: https://spdx.org/licenses/exceptions-index.html
 [matching]: https://spdx.org/spdx-license-list/matching-guidelines
+[master-files]: https://github.com/spdx/license-list
 [new-license]: https://spdx.org/spdx-license-list/request-new-license
 
 The following table contains the full names and short identifiers for the SPDX License List, v2.5 which was released July 2016. For the full and most up-to-date version of the SPDX License List as well as other related information, please see [http://spdx.org/licenses/](http://spdx.org/licenses/)

chapters/appendix-II-license-matching-guidelines-and-templates.md

@@ -4,7 +4,7 @@ The [SPDX License List Matching Guidelines](http://spdx.org/spdx-license-list/ma
 
 ## SPDX License List Template Access
 
-The master files for the SPDX License List includes a spreadsheet listing all the licenses, deprecated licenses, and license exceptions; and the text for each license in a .txt file. These files are available in a [Git repository](http://git.spdx.org/?p=license-list.git%3Ba=summary). Text that can be considered replaceable or omitable for matching purposes is indicated in the .txt file with markup as per the description below.
+The master files for the SPDX License List includes a spreadsheet listing all the licenses, deprecated licenses, and license exceptions; and the text for each license in a .txt file. These files are available in a [Git repository](https://github.com/spdx/license-list). Text that can be considered replaceable or omitable for matching purposes is indicated in the .txt file with markup as per the description below.
 
 RDFa Access: The template text for the license can be accessed using the RDF tag licenseTemplate on the web page containing the license.