diff --git a/pilot/index.tpl.html b/pilot/index.tpl.html
index c4327ad..b253f82 100644
--- a/pilot/index.tpl.html
+++ b/pilot/index.tpl.html
@@ -2,7 +2,7 @@
 *{box-sizing:border-box}
 body{margin:0;background:var(--void);color:var(--ink);font-family:var(--sans);
      -webkit-font-smoothing:antialiased}
-.wrap{max-width:64ch;margin:0 auto;padding:0 1.25rem}
+.wrap{max-width:56rem;margin:0 auto;padding:0 1.25rem}
 h1 em{color:transparent;background:linear-gradient(100deg,var(--cyan) 10%,var(--magenta));
   -webkit-background-clip:text;background-clip:text;padding-bottom:.12em}
 .card{position:relative}
diff --git a/pilot/mirror.tpl.html b/pilot/mirror.tpl.html
index d80c8db..a96721a 100644
--- a/pilot/mirror.tpl.html
+++ b/pilot/mirror.tpl.html
@@ -1,4 +1,5 @@
 <style>
+  :root{--void-2:#0a0f1b;--card:#0d1424;--good:#7fe0a7;--bad:#ff8fa3}
   *{box-sizing:border-box}
   html{scroll-behavior:smooth}
   body{margin:0;background:var(--void);color:var(--ink);
@@ -468,7 +469,7 @@ per upstream, with <code>http.compat: ["docker2s2"]</code>) is mandatory in both
 directions: the registry refuses to start with one and not the other (the Loop 1 field
 note is this rule being learned). This deployment runs both on all five upstreams.</p>
 
-<p>Digest preservation and artifact completeness are different properties. The docs tie
+<p>Digest preservation and artefact completeness are different properties. The docs tie
 <code>preserveDigest</code>/<code>compat</code> to keeping mirrored manifest bytes and
 media types - and therefore signature <em>validity</em> - aligned with upstream. Whether
 signature, SBOM and attestation objects <em>arrive</em> is separate: OCI 1.1 referrers
@@ -496,7 +497,7 @@ upstream documentation and the deployed version's source:</p>
 <ul>
 <li>With no retention configuration, <strong>all tags are retained</strong> and
 <strong>all untagged manifests are deleted</strong> by GC (unless referenced by an index
-or artifact). Timing is two-stage: the manifest ages past <code>gcDelay</code> (1h here),
+or artefact). Timing is two-stage: the manifest ages past <code>gcDelay</code> (1h here),
 then deletion happens at the next sweep (<code>gcInterval</code>, 24h here) - the survival
 window depends on where creation falls relative to that sweep, not a fixed one-hour fuse.</li>
 <li><strong>Digest-only pull-through entries are stored as untagged manifests.</strong>