fix: markdown links that just were "here"

Signed-off-by: jmeridth <[email protected]>

Author: jmeridth

docs/commercial-licenses.md

@@ -2,4 +2,4 @@
 
 Should you wish to contribute to a project that requires a proprietary license to do so, <COMPANY_NAME> will need to purchase a license after making the decision whether or not to do so.
 
-If there is no existing proprietary license, an issue can be opened at [Governance, Risk, Compliance & Communication (GRCC)](XXX) or a workflow in [tool] to begin the process of reviewing the vendor for our data privacy and security protections to purchase a license. See more on the Procurement process [here](XXX).
+If there is no existing proprietary license, an issue can be opened at [Governance, Risk, Compliance & Communication (GRCC)](XXX) or a workflow in [tool] to begin the process of reviewing the vendor for our data privacy and security protections to purchase a license. See more on [the Procurement process](XXX).

docs/ospo-tools-and-external-guides.md

@@ -1,6 +1,6 @@
 ## Tools
 
-These tools, whether developed by GitHub or the broader community, are useful for OSPOs to manage and scale open source initiatives effectively. While we are highlighting some of the tools and guides we encounter that solve common use cases for OSPOs, there are even more out there. To help curate a more robust toolkit, consider adding the `OSPO` [topic](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics#adding-topics-to-your-repository) to relevant repositories. See the full list of OSPO topic repositories [here](https://github.com/topics/ospo). If you're looking for more tools you can also check out [`awesome-ospo`](https://github.com/todogroup/awesome-ospo) that provides a list of packages and projects OSPOs in the TODO Group have found useful.
+These tools, whether developed by GitHub or the broader community, are useful for OSPOs to manage and scale open source initiatives effectively. While we are highlighting some of the tools and guides we encounter that solve common use cases for OSPOs, there are even more out there. To help curate a more robust toolkit, consider adding the `OSPO` [topic](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics#adding-topics-to-your-repository) to relevant repositories. See the full list of [OSPO topic repositories](https://github.com/topics/ospo). If you're looking for more tools you can also check out [`awesome-ospo`](https://github.com/todogroup/awesome-ospo) that provides a list of packages and projects OSPOs in the TODO Group have found useful.
 
 ### Compliance
 

policies/releasing.md

@@ -5,7 +5,7 @@ The following steps should be taken to release and maintain your open source pro
 
 1. **Register your release**. Create an issue in the XXX repo to register your intended release.
 2. **Name your project**. Check that it does [not conflict with an existing project](http://ivantomic.com/projects/ospnc/) or infringe on any [trademarks](https://www.uspto.gov).
-3. **Include the following in the root directory**. The folder with the templates is available [here](../release%20template).
+3. **Include the following in the root directory**. The [folder with the templates](../release%20template) is available.
    - **README.md file** describing the purpose and state of the repository. A good README file is often
      critical to project success. This is also a good place to put any top-level and important information for newcomers to your project.
    - **LICENSE.txt file** with the MIT license text. Include <COMPANY_NAME> above the copyright statement.