From 4abcc7f1d4c80f84218c001169c2970ba5105c7b Mon Sep 17 00:00:00 2001
From: tamsin woo <tamsinwoo@pm.me>
Date: Tue, 12 Mar 2024 20:45:30 -0700
Subject: [PATCH] fix duplicate langage in hugo-on-k8s post

---
 content/posts/hugo-on-k8s-nginx/index.md  | 4 ++--
 public/posts/hugo-on-k8s-nginx/index.html | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/posts/hugo-on-k8s-nginx/index.md b/content/posts/hugo-on-k8s-nginx/index.md
index bf7b821..bed6da7 100644
--- a/content/posts/hugo-on-k8s-nginx/index.md
+++ b/content/posts/hugo-on-k8s-nginx/index.md
@@ -307,8 +307,8 @@ this part expresses a routing rule: traffic reaching the cluster via
 to actually apply this rule, i need an ingress controller. mine is
 [ingress-nginx][nginx-ingress].
 
-when i deployed controller in my cluster, it created _some more_ `nginx` `Pod`s
-in my cluster. these update their configuration dynamically based on the rules
+when i deployed controller in my cluster, it created _some more_ `nginx` `Pod`s.
+these update their configuration dynamically based on the rules
 in my `Ingress` resource(s). the controller also also creates a `Service` of
 type `LoadBalancer`, which [magically][do-lb] creates a load balancer appliance
 in my cloud provider. off-screen, i can point DNS to *that* appliance to finish
diff --git a/public/posts/hugo-on-k8s-nginx/index.html b/public/posts/hugo-on-k8s-nginx/index.html
index 2918f14..31ade2b 100644
--- a/public/posts/hugo-on-k8s-nginx/index.html
+++ b/public/posts/hugo-on-k8s-nginx/index.html
@@ -314,8 +314,8 @@ and direct it to the <code>Service</code>:</p>
 <code>estradiol.cloud</code> should go to my <code>Service</code>, and then to one of its backend <code>Pod</code>s.
 to actually apply this rule, i need an ingress controller. mine is
 <a href="https://kubernetes.github.io/ingress-nginx/">ingress-nginx</a>.</p>
-<p>when i deployed controller in my cluster, it created <em>some more</em> <code>nginx</code> <code>Pod</code>s
-in my cluster. these update their configuration dynamically based on the rules
+<p>when i deployed controller in my cluster, it created <em>some more</em> <code>nginx</code> <code>Pod</code>s.
+these update their configuration dynamically based on the rules
 in my <code>Ingress</code> resource(s). the controller also also creates a <code>Service</code> of
 type <code>LoadBalancer</code>, which <a href="https://docs.digitalocean.com/products/kubernetes/how-to/add-load-balancers/">magically</a> creates a load balancer appliance
 in my cloud provider. off-screen, i can point DNS to <em>that</em> appliance to finish