more markdown linting & link checking fixes

OWASP · Sep 10, 2024 · 22bde74 · 22bde74
1 parent 920ef8e
commit 22bde74
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 5 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -18,7 +18,7 @@ jobs:
       - name: Link Checker
         uses: lycheeverse/lychee-action@v1.10.0
         with:
-          args: --no-progress --max-retries 5 './docs/**/*.md'
+          args: --no-progress --max-retries 5 --exclude-path './docs/about-top-10/in-the-news.md' './docs/**/*.md'
           fail: true
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

diff --git a/docs/archive/2018/0x02-about-project.md b/docs/archive/2018/0x02-about-project.md
@@ -22,6 +22,6 @@ This document is released under the Creative Commons Attribution ShareAlike 3.0
 
 ## Contributors
 
-* Chris Romeo  &nbsp; | Dan Anderson  &nbsp; |  David Cybuck 
+* Chris Romeo  &nbsp; | Dan Anderson  &nbsp; |  David Cybuck
 * Dave Ferguson | Josh Grossman | Osama Elnaggar
 * Colin Watson &nbsp; | Rick Mitchell &nbsp; |  And many more…  
diff --git a/docs/archive/2018/0x04-introduction.md b/docs/archive/2018/0x04-introduction.md
@@ -25,7 +25,7 @@ This list was originally created by the current project leads with contributions
 
 ## Target Audience
 
-This document is primarily written for developers. However, development managers, product owners, Q/A professionals, program managers, and anyone involved in building software can also benefit from this document. 
+This document is primarily written for developers. However, development managers, product owners, Q/A professionals, program managers, and anyone involved in building software can also benefit from this document.
 
 ## How to Use this Document
 

diff --git a/docs/archive/2018/c1-security-requirements.md b/docs/archive/2018/c1-security-requirements.md
@@ -36,7 +36,7 @@ This story contains the same message as the traditional requirement from ASVS, w
 
 ## Implementation
 
-Successful use of security requirements involves four steps. The process includes discovering / selecting, documenting, implementing, and then confirming correct implementation of new security features and functionality within an application. 
+Successful use of security requirements involves four steps. The process includes discovering / selecting, documenting, implementing, and then confirming correct implementation of new security features and functionality within an application.
 
 ### Discovery and Selection
 
@@ -46,7 +46,7 @@ The process begins with discovery and selection of security requirements. In thi
 
 During investigation and documentation, the developer reviews the existing application against the new set of security requirements to determine whether the application currently meets the requirement or if some development is required. This investigation culminates in the documentation of the results of the review.
 
-### Implementation
+### Implementation Phase
 
 After the need is determined for development, the developer must now modify the application in some way to add the new functionality or eliminate an insecure option. In this phase the developer first determines the design required to address the requirement, and then completes the code changes to meet the requirement.
 

diff --git a/docs/archive/2018/c5-validate-inputs.md b/docs/archive/2018/c5-validate-inputs.md
@@ -86,6 +86,7 @@ Consider an application that needs to accept HTML from users (via a WYSIWYG edit
 Therefore, you need a library that can parse and clean HTML formatted text. Please see the [XSS Prevention Cheat Sheet on HTML Sanitization](https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet#RULE_.236_-_Sanitize_HTML_Markup_with_a_Library_Designed_for_the_Job) for more information on HTML Sanitization.
 
 ### Validation Functionality in Libraries and Frameworks
+
 All languages and most frameworks provide validation libraries or functions which should be leveraged to validate data. Validation libraries typically cover common data types, length requirements, integer ranges, "is null" checks and more. Many validation libraries and frameworks allow you to define your own regular expression or logic for custom validation in a way that allows the programmer to leverage that functionality throughout your application. Examples of validation functionality include PHP’s [filter functions](https://secure.php.net/manual/en/filter.examples.validation.php) or the [Hibernate Validator](http://hibernate.org/validator/) for Java. Examples of HTML Sanitizers include [Ruby on Rails sanitize method](http://edgeapi.rubyonrails.org/classes/ActionView/Helpers/SanitizeHelper.html), [OWASP Java HTML Sanitizer](https://www.owasp.org/index.php/OWASP_Java_HTML_Sanitizer_Project) or [DOMPurify](https://github.com/cure53/DOMPurify).
 
 ## Vulnerabilities Prevented