diff --git a/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html b/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html
index 73d2e57..cf9fa0a 100644
--- a/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html
+++ b/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html
@@ -136,9 +136,9 @@ they have provided, but they also sent one via email, so I'll just use that for
 <p><code>2a03:4000</code> is Netcup's network I believe with <code>AAAA</code> defining a certain part of that network.<br />
 <code>BBBB</code> is the subnet provided to me with <code>cccc:dddd:eeee:ffff</code> being the range of address I can use in that subnet.</p>
 <p>Netcup's IPv6 network is switched, not routed, I'm sure there's a reason for this, and I'm sure it's sensible, but for now the important bit is that the IPv6 gateway should always be <code>fe80::1%vtnet0</code> (where <code>vtnet0</code> is the external interface name) rather than another <code>2a03:4000::AAAA:BBBB</code> IPv6 address. I pop that into my <code>rc.conf</code> as well.</p>
-<pre style="background-color:#212121;color:#eeffff;"><code><span>...
-</span><span>ipv6_defaultrouter=&quot;fe80::1%vtnet0&quot;
-</span><span>...
+<pre data-lang="conf" style="background-color:#212121;color:#eeffff;" class="language-conf "><code class="language-conf" data-lang="conf"><span style="color:#89ddff;">...
+</span><span style="color:#f78c6c;">ipv6_defaultrouter</span><span style="color:#89ddff;">=</span><span style="color:#c3e88d;">&quot;fe80::1%vtnet0&quot;
+</span><span style="color:#89ddff;">...
 </span></code></pre>
 <p>Reboot the VPS, and all works well. <code>ping6</code>s work, <code>curl</code>s to IPv6 addresses work, incoming IPv6 connections work. Great! Done...</p>
 <p>Not Done.</p>