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 Service
:
estradiol.cloud
should go to my Service
, and then to one of its backend Pod
s.
to actually apply this rule, i need an ingress controller. mine is
ingress-nginx.
-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 creates a load balancer appliance
in my cloud provider. off-screen, i can point DNS to that appliance to finish