Updated README.md

Author: rsenden

README.md

@@ -2,7 +2,7 @@
 
 This Fortify SSC parser plugin allows for importing scan results from OWASP Dependency Check.
 
-### Related Links
+### <a name="related-links">Related Links</a>
 
 * **Downloads**:  
   _Beta versions may be unstable or non-functional. The `*-licenseReport.zip` and `*-dependencySources.zip` files are for informational purposes only and do not need to be downloaded._
@@ -13,12 +13,12 @@ This Fortify SSC parser plugin allows for importing scan results from OWASP Depe
 * **OWASP Dependency Check website**: https://owasp.org/www-project-dependency-check/
 
 
-## Usage
+## <a name="usage">Usage</a>
 
 The following sections describe how to install and use the plugin. For generic information
 about how to install and use SSC parser plugins, please see the Fortify SSC documentation.
 
-### Plugin Install & Upgrade
+### <a name="plugin-install--upgrade">Plugin Install & Upgrade</a>
 
 * Obtain the plugin binary jar file
 	* Either download from Bintray (see [Related Links](#related-links)) 
@@ -31,21 +31,21 @@ about how to install and use SSC parser plugins, please see the Fortify SSC docu
 	* Upload the plugin jar file
 	* Enable the plugin by clicking the `ENABLE` button
 
-### Plugin Uninstall
+### <a name="plugin-uninstall">Plugin Uninstall</a>
 
 * In Fortify Software Security Center:
 	* Navigate to Administration->Plugins->Parsers
 	* Select the parser plugin that you want to uninstall
 	* Click the `DISABLE` button
 	* Click the `REMOVE` button 
 
-### Obtain results
+### <a name="obtain-results">Obtain results</a>
 
 Please see the OWASP Dependency Check documentation for details on scanning applications and 
 generating reports. Note that the SSC parser plugin requires the uploaded reports to be in JSON
 format.
 
-### Upload results
+### <a name="upload-results">Upload results</a>
 
 SSC web interface (manual upload):
 
@@ -68,26 +68,26 @@ SSC clients (FortifyClient, Maven plugin, ...):
 
 
 
-## Information for plugin developers
+## <a name="information-for-plugin-developers">Information for plugin developers</a>
 
 The following sections provide information that may be useful for developers of this 
 parser plugin.
 
-### IDE's
+### <a name="ides">IDE's</a>
 
 This project uses Lombok. In order to have your IDE compile this project without errors, 
 you may need to add Lombok support to your IDE. Please see https://projectlombok.org/setup/overview 
 for more information.
 
-### Gradle
+### <a name="gradle">Gradle</a>
 
 It is strongly recommended to build this project using the included Gradle Wrapper
 scripts; using other Gradle versions may result in build errors and other issues.
 
 The Gradle build uses various helper scripts from https://github.com/fortify-ps/gradle-helpers;
 please refer to the documentation and comments in included scripts for more information. 
 
-### Commonly used commands
+### <a name="commonly-used-commands">Commonly used commands</a>
 
 All commands listed below use Linux/bash notation; adjust accordingly if you
 are running on a different platform. All commands are to be executed from
@@ -107,7 +107,7 @@ the main project directory.
 Note that the version management tasks operate only on the local repository; you will need to manually
 push any changes (including tags and branches) to the remote repository.
 
-### Versioning
+### <a name="versioning">Versioning</a>
 
 The various version-related Gradle tasks assume the following versioning methodology:
 
@@ -117,7 +117,7 @@ The various version-related Gradle tasks assume the following versioning methodo
 	* However, note that the Gradle build may be unable to identify a correct version number for the project
 	* As such, only builds from tagged versions or from a `<version>-SNAPSHOT` branch should be published to a Maven repository
 
-### Automated Builds & publishing
+### <a name="automated-builds--publishing">Automated Builds & publishing</a>
 
 Travis-CI builds are automatically triggered when there is any change in the project repository,
 for example due to pushing changes, or creating tags or branches. If applicable, binaries and related 
@@ -130,6 +130,6 @@ artifacts are automatically published to Bintray using the `bintrayUpload` task:
 See the [Related Links](#related-links) section for the relevant Travis-CI and Bintray links.
 
 
-# Licensing
+# <a name="licensing">Licensing</a>
 See [LICENSE.TXT](LICENSE.TXT)