fix: close remaining unclosed <ol> tags in blog posts

Coding-Dev-Tools · Oct 3, 2026 · Aug 9, 2026 · Aug 10, 2026 · Aug 10, 2026 · Aug 15, 2026
commit cb54dfad855c91183eba01466f45f85c3cc6bab5
@@ -295,7 +295,7 @@ <h2>Real-World Scenario: Compromised Key Response</h2>
     <li>Ran <code>apiauth generate api-key --service api-gateway</code> — a new key was created</li>
     <li>Ran <code>apiauth export --format github-actions</code> — the new key was exported to update CI secrets</li>
     <li>Verified with <code>apiauth list</code> that the revoked key still appears in the audit trail for compliance</li>
-  </ul>
+  </ol>
   <p>
     Total time: under 60 seconds. No frantic Slack messages, no searching through .env files, no wondering if the key was rotated everywhere.
   </p>

diff --git a/blog/mcp-everywhere-why-your-cli-tools-need-it.html b/blog/mcp-everywhere-why-your-cli-tools-need-it.html
@@ -180,7 +180,7 @@ <h2>Getting Started</h2>
             <li><strong>Serve one:</strong> <code>click-to-mcp serve your-cli-name</code></li>
             <li><strong>Add to your AI agent config</strong> (Claude Code, Cursor, etc.)</li>
             <li><strong>Submit to MCP directories</strong> for discoverability</li>
-        </ul>
+        </ol>
 
         <p>That's it. No SDK code, no separate deployments, no maintenance burden. Your existing CLI tools just became AI-accessible.</p>
 

@@ -109,7 +109,7 @@ <h2>How It Works</h2>
     <li><strong>Parse</strong> — Each format has a dedicated parser (regex-based for Drizzle, full grammar for SQL) that extracts tables, columns, types, constraints, and enums into a unified IR</li>
     <li><strong>IR</strong> — An intermediate representation of the schema, lossless with respect to all supported formats</li>
     <li><strong>Generate</strong> — Each output format has a generator that renders the IR as idiomatic code</li>
-  </ul>
+  </ol>
 
   <p>This architecture ensures that converting A → B → A is an identity (roundtrip), even across complex transformations.</p>