capitalize headings

docs/architecture-overview.md

@@ -31,7 +31,7 @@ Every boundary above only means something if a service can't just skip it by rea
 
 **Three separate routing authorities enforce these** — the edge firewall, the user-facing proxy, and the internal proxy zone — rather than one central router handling everything. That's a deliberate rejection of the simpler single-router design: one router is one thing to hardening-focus on and one thing that takes everything down if it's compromised or misconfigured.
 
-### What actually happens when one fails
+### What Actually Happens When One Fails
 
 Not a hypothetical — this is the real, deliberate payoff of splitting routing authority three ways instead of one:
 
@@ -87,7 +87,7 @@ That third fix isn't just a claim — it's the actual live ruleset:
 
 </details>
 
-## The other six traffic laws
+## The Other Six Traffic Laws
 
 Each of these gets its own full mechanism doc elsewhere in this repo — this table is the map, not the territory:
 
@@ -102,7 +102,7 @@ Each of these gets its own full mechanism doc elsewhere in this repo — this ta
 
 The pattern repeats across all eight laws, not just the trust-boundary story above: **control-plane failure never takes down the data plane.** Every "failure behavior" row above ends the same way — the thing that broke stops working, and everything else keeps running regardless. That's not a coincidence; it's the same design principle applied consistently everywhere, not just to network trust.
 
-## What this map deliberately excludes
+## What This Map Deliberately Excludes
 
 Not a firewall rule listing, not a port inventory, not a service configuration reference — those live in [`docs/firewall-and-network.md`](firewall-and-network.md) and the docs linked in the table above. This is strictly the stable, directional shape of how trust and traffic actually move — meant to still be true even after the specific tools implementing it change again, the way it already has three times.