From 785651c7822bfcefbb3d50f566e7bacd1bc2ab28 Mon Sep 17 00:00:00 2001
From: bpcreech <35012922+bpcreech@users.noreply.github.com>
Date: Tue, 6 Feb 2024 17:28:57 -0500
Subject: [PATCH] tiny edits

---
 content/post/how-this-works.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/post/how-this-works.md b/content/post/how-this-works.md
index 17d368a..428f8de 100644
--- a/content/post/how-this-works.md
+++ b/content/post/how-this-works.md
@@ -166,12 +166,12 @@ instead, the
 go with a more complex path of:
 
 1. Allocating your own static VIP (probably both IPv4 and IPv6),
-2. Obtaining and generating your own cert, and
+2. Obtaining 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
+and the load balancer!), but it's more complicated. The fact that it uses a per-site
 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