apache · dave2wave · Nov 29, 2025 · Nov 28, 2025 · Nov 28, 2025 · Nov 28, 2025
diff --git a/.github/linters/.markdown-lint.yml b/.github/linters/.markdown-lint.yml
@@ -7,7 +7,7 @@ MD004:
 MD005:
   indent: 2
 
-MD007: 2
+MD007: false
 
 MD013:
   code_blocks: false
@@ -17,14 +17,18 @@ MD013:
 # MD025/single-title/single-h1 Multiple top-level headings in the same document
 MD025: false
 
-MD029: one
+MD028: false
+
+MD029: false
 
 MD033: false
 
 MD034: false
 
 MD035: consistent
 
+MD040: false
+
 # MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading
 MD041: false
 

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -35,7 +35,7 @@ repos:
         files: ^requirements\.txt$
       - id: trailing-whitespace
         args: [--markdown-linebreak-ext=md]
-        exclude: \.svg$
+        exclude: (\.svg$)
-        exclude: (\.svg$)
+        exclude: \.svg$
-        exclude: (\.svg$)
+        exclude: \.svg$
   - repo: https://github.com/igorshubovych/markdownlint-cli
     rev: v0.46.0
     hooks:

diff --git a/content/highlight/github.min.css b/content/highlight/github.min.css
diff --git a/content/highlight/highlight.min.js b/content/highlight/highlight.min.js
@@ -1210,4 +1210,4 @@ begin:"\\b[0-9]{4}(-[0-9][0-9]){0,2}([Tt \\t][0-9][0-9]?(:[0-9][0-9]){2})?(\\.[0
 aliases:["yml"],contains:l}}});const He=ae;for(const e of Object.keys(Ke)){
 const n=e.replace("grmr_","").replace("_","-");He.registerLanguage(n,Ke[e])}
 return He}()
-;"object"==typeof exports&&"undefined"!=typeof module&&(module.exports=hljs);
+;"object"==typeof exports&&"undefined"!=typeof module&&(module.exports=hljs);
diff --git a/content/pages/draft-asf-token-standard.md b/content/pages/draft-asf-token-standard.md
@@ -112,4 +112,4 @@ These values must not be used in any application. The `sample` component will be
 
 ## Detection guidance
 
-To detect tokens, the regular expression presented in the Syntax section above can be used alone, without anchoring, as a heuristic with a high probability of matches. For better prevention of false positives in detection, the suffix matching the CRC-32 can be validated. Components can also be validated against the list maintained by Security.
+To detect tokens, the regular expression presented in the Syntax section above can be used alone, without anchoring, as a heuristic with a high probability of matches. For better prevention of false positives in detection, the suffix matching the CRC-32 can be validated. Components can also be validated against the list maintained by Security.
diff --git a/content/pages/policies.md b/content/pages/policies.md
@@ -3,5 +3,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
 
 We will list various proposed policies and policy changes. These will be speculative until approved.
 
+## Security policies
+
 1. [ASF standard for scannable secret tokens](./draft-asf-token-standard)
    - [FAQ](./draft-asf-token-standard-faq)
diff --git a/requirements.txt b/requirements.txt
@@ -1,4 +1,5 @@
 beautifulsoup4
 Markdown
 pelican
+pre-commit
 requests
Original file line number	Diff line number	Diff line change
Expand Up		@@ -112,4 +112,4 @@ These values must not be used in any application. The `sample` component will be

		## Detection guidance

		To detect tokens, the regular expression presented in the Syntax section above can be used alone, without anchoring, as a heuristic with a high probability of matches. For better prevention of false positives in detection, the suffix matching the CRC-32 can be validated. Components can also be validated against the list maintained by Security.
		To detect tokens, the regular expression presented in the Syntax section above can be used alone, without anchoring, as a heuristic with a high probability of matches. For better prevention of false positives in detection, the suffix matching the CRC-32 can be validated. Components can also be validated against the list maintained by Security.