Fact Check

This is built specifically for the 33 JavaScript Concepts project to catch technical errors before they ship. It walks you through five verification phases: running code examples against tests, checking MDN compliance, validating against the ECMAScript spec for edge cases, and verifying external links still work. The methodology is thorough, maybe overkill for a blog post, but exactly right if you're maintaining educational content where incorrect output comments or outdated pre-ES6 patterns could confuse thousands of learners. It even flags common mistakes like claiming typeof null returns "null" or getting Promise microtask timing wrong. Worth adapting if you publish any kind of technical reference material.