fixes broken links highlighted by html-proofer

CONTRIBUTING.md

@@ -153,7 +153,7 @@ You should also run the testing script against your local build. This script wil
 
 ## Submitting Your Open Source Project
 
-If you have a project that you have open sourced, then you need to add (or update) your project in the [code inventory](https://code.mil/code.json) file that the DoD uses to comply with [OMB Policy (M-16-21)](https://sourcecode.cio.gov/OSS/). You can read more about the format of the [code inventory format](https://code.gov/about/compliance/inventory-code) on the Code.gov website.
+If you have a project that you have open sourced, then you need to add (or update) your project in the [code inventory](https://code.mil/code.json) file that the DoD uses to comply with [OMB Policy (M-16-21)](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf). You can read more about the format of the [code inventory format](https://code.gov/about/compliance/inventory-code) on the Code.gov website.
 
 To add your project you will need to submit a Pull Request to this project on GitHub. You can follow the instructions here for doing so, but if you are not familiar with GitHub, you can also just [tell us about your project](https://code.mil/tell-us-about-your-code.html) and we can get the process started.
 

src/how-to-open-source.md

@@ -38,8 +38,8 @@ Now that you've chosen a license you should add a few documents to the codebase
 
 You can see examples of these documents in the code repository for this very website!
 
-* [LICENSE.md](https://github.com/Code-dot-mil/code.mil/blob/master/LICENSE.md)
-* [INTENT.md](https://github.com/Code-dot-mil/code.mil/blob/master/INTENT.md)
+- [LICENSE.md](https://github.com/Code-dot-mil/code.mil/blob/master/LICENSE.md)
+- [INTENT.md](https://github.com/Code-dot-mil/code.mil/blob/master/INTENT.md)
 
 <section class="usa-alert usa-alert-info">
   <article class="usa-alert-body">
@@ -60,8 +60,8 @@ The last piece of documentation you absolutely need is how people can contribute
 
 You can read the contributing documentation for this site to see an example of what this looks like:
 
-* [CONTRIBUTING.md](https://github.com/Code-dot-mil/code.mil/blob/master/CONTRIBUTING.md)
-* [CONTRIBUTORS.md](https://github.com/Code-dot-mil/code.mil/blob/master/CONTRIBUTORS.md)
+- [CONTRIBUTING.md](https://github.com/Code-dot-mil/code.mil/blob/master/CONTRIBUTING.md)
+- [CONTRIBUTORS.md](https://github.com/Code-dot-mil/code.mil/blob/master/CONTRIBUTORS.md)
 
 ### Step 5: Release it!
 
@@ -80,7 +80,7 @@ If you aren't sure where to post the code, or you need help getting source contr
 
 ### Step 6: OMB Policy Tracking
 
-The last piece of this process is adding your project to the [code inventory](https://code.mil/code.json) file that the DoD uses to comply with [OMB Policy (M-16-21)](https://sourcecode.cio.gov/OSS/). You can read more about the format of the [code inventory format](https://code.gov/about/compliance/inventory-code) on the Code.gov website.
+The last piece of this process is adding your project to the [code inventory](https://code.mil/code.json) file that the DoD uses to comply with [OMB Policy (M-16-21)](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf). You can read more about the format of the [code inventory format](https://code.gov/about/compliance/inventory-code) on the Code.gov website.
 
 To add your project you will need to submit a Pull Request to the [Code.mil project on GitHub](https://github.com/Code-dot-mil/code.mil). There are instructions for doing so in our code repository, but if you are not familiar with GitHub, you can also just [tell us about your project](/tell-us-about-your-code.html) and we can get the process started.
 

src/why-open-source.md

@@ -17,7 +17,7 @@ You may have lots of questions about OSS and how a DoD project can be released p
 
 Aside from the technical benefits mentioned above, the [Federal Source Code Policy (M-16-21)](https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2016/m_16_21.pdf) from the US CTO includes a section initiating an [open source pilot](https://code.gov/about/open-source/introduction) which mandates that each government agency **release as OSS at least 20% of its new custom developed code** for the term of the program (and we recommend continuing that beyond the pilot).
 
-Going beyond the OMB policy itself, the [2018 NDAA](https://www.congress.gov/bill/115th-congress/house-bill/2810/text) states in [section 875](https://www.congress.gov/bill/115th-congress/house-bill/2810/text#toc-H085810BEC6434028988553F08918929F) that "...the Secretary of Defense shall initiate for the Department of Defense the open source software pilot program established by the Office of Management and Budget Memorandum M-16-21..."
+Going beyond the OMB policy itself, the [2018 NDAA](https://www.govinfo.gov/app/details/PLAW-115publ91) states in section 875 that "...the Secretary of Defense shall initiate for the Department of Defense the open source software pilot program established by the Office of Management and Budget Memorandum M-16-21..."
 
 <section class='usa-alert usa-alert-info'>
   <article class='usa-alert-body'>