diff --git a/content/post/how-this-works.md b/content/post/how-this-works.md
index 32837f5..f007e63 100644
--- a/content/post/how-this-works.md
+++ b/content/post/how-this-works.md
@@ -74,6 +74,6 @@ They *could* have gone with a Github-Pages-like Let's Encrypt path, by setting u
 2. Obtaining and generating your own cert, and
 3. Setting up the Google Cloud Load Balancer pointing that VIP to your bucket using your cert.
 
-This is more flexible and powerful (way more knobs to play with on both the cert and the load balancer!), but it's more complicated. The fact that it uses a static VIP means you need to pay for an ever-diminishing and thus [ever-more-costly resource](https://cloud.google.com/vpc/network-pricing#ipaddress). (As of this writing, unused IPv4 addresses cost $113, and AFAICT ones mapped to GCS buckets are free?! I assume that will change eventually as [availability dwindles](https://ipv4.potaroo.net/).)
+This is more flexible and powerful (way more knobs to play with on both the cert and the load balancer!), but it's more complicated. The fact that it uses a static VIP means you need to pay for an ever-diminishing and thus [ever-more-costly resource](https://cloud.google.com/vpc/network-pricing#ipaddress). (As of this writing, unused IPv4 addresses cost $113 / year, and AFAICT ones mapped to GCS buckets are free?! I assume that will change eventually as [availability dwindles](https://ipv4.potaroo.net/).)
 
 I suppose that once IPv4 is sufficiently exhausted, after the ensuing chaos, everyone's crappy ISP will finally support IPv6 it will be more reasonable to just generate free static IPv6 VIPs (forgoing IPv4), and then dispense with server-side tricks like vhosting to map multiple sites onto one address. In the meanwhile, "I just want to serve 4 TB from GCS" is a slightly more complicated and potentially not-quite-free.