General Markdown Maintenance & Addition of Dockerfile for Easy Testin…

…g w/o Python (#1459)

* Maintenance

- Added `Dockerfile` for containerized local testing.
- Updated lint task to cover all markdown files except `node_modules` and `cheatsheets_excluded`.
- Resolved markdown lint issues identified in various repository files.
- Added additional suggestion for `File_Upload_Cheat_Sheet.md`.

* Remove CODEOWNERS errors

---------

Co-authored-by: Jeymz Simmons <james@robotti.io>
Co-authored-by: Shlomo Zalman Heigh <shlomozalmanheigh@gmail.com>

.github/CODEOWNERS

@@ -1,13 +1,12 @@
-# See https://help.github.com/en/articles/about-code-owners
+# See [https://help.github.com/en/articles/about-code-owners](https://help.github.com/en/articles/about-code-owners)
 
-# These owners will be the default owners for everything in the repo.
-*       @mackowski @jmanico @szh
+## These owners will be the default owners for everything in the repo
 
-# commjoen have full access to Secrets_Management_CheatSheet
-* /cheatsheets_draft/Secrets_Management_CheatSheet.md @commjoen 
+- @mackowski @jmanico @szh
 
-# Kevin W. Wall (kwwall) 
-/cheatsheets/Authentication_Cheat_Sheet.md kevin.w.wall@gmail.com @mackowski @jmanico @szh
+## Kevin W. Wall (kwwall)
+
+/cheatsheets/Authentication_Cheat_Sheet.md @kwwall @mackowski @jmanico @szh
 /cheatsheets/Authorization_Cheat_Sheet.md @kwwall @mackowski @jmanico @szh
 /cheatsheets/C-Based_Toolchain_Hardening_Cheat_Sheet.md @kwwall @mackowski @jmanico @szh
 /cheatsheets/Choosing_and_Using_Security_Questions_Cheat_Sheet.md @kwwall @mackowski @jmanico @szh

.github/ISSUE_TEMPLATE/new_cheatsheet_proposal.md

@@ -12,22 +12,15 @@ assignees: ''
 ## What is the proposed Cheat Sheet about?
 <!--- A short summary of what the Cheat Sheet will be about -->
 
-
 ## What security issues are commonly encountered related to this area?
 <!--- Common issues or vulnerabilities that would be addressed -->
 
-
-
 ## What is the objective of the Cheat Sheet?
 <!--- What the Cheat Sheet will provide to the reader and wider community -->
 
-
-
 ## What other resources exist in this area?
 <!--- Are there any other OWASP projects that cover this area? -->
 <!--- Would this content be better suited to the testing guide projects? -->
 <!--- What other third party guidelines or resources currently exist? -->
 
-
-
 <!-- Thank you again for your contribution -->

.github/pull_request_template.md

@@ -1,4 +1,6 @@
-Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series. 
+# You're A Rockstar
+
+Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.
 
 > :triangular_flag_on_post: If your PR is related to grammar/typo mistakes, please double-check the file for other mistakes in order to fix all the issues in the current cheat sheet.
 
@@ -15,6 +17,6 @@ Please make sure that for your contribution:
 
 If your PR is related to an issue, please finish your PR text with the following line:
 
-This PR covers issue #<insert number here>.
+This PR covers issue #`<REPLACE WITH ISSUE NUMBER>`.
 
 Thank you again for your contribution :smiley:

CODE_OF_CONDUCT.md

@@ -14,21 +14,21 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
+- The use of sexualized language or imagery and unwelcome sexual attention or
  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
  professional setting
 
 ## Our Responsibilities
@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at dominique.righetto@owasp.org or jim@owasp.org. 
+reported by contacting the project team at [dominique.righetto@owasp.org](mailto:dominique.righetto@owasp.org) or [jim@owasp.org](mailto:jim@owasp.org).
 
 All complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
@@ -69,9 +69,9 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
 
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq)