From 3d76ae3399d7a5334e414e92b0a0c92b92bbbf4f Mon Sep 17 00:00:00 2001
From: Sheen Capadngan <sheensantoscapadngan@gmail.com>
Date: Tue, 17 Jun 2025 20:25:38 +0800
Subject: [PATCH] misc: some more updates in examples

---
 .../guides/production-hardening.mdx           | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/self-hosting/guides/production-hardening.mdx b/docs/self-hosting/guides/production-hardening.mdx
index d91ff1214..1ec08a0a4 100644
--- a/docs/self-hosting/guides/production-hardening.mdx
+++ b/docs/self-hosting/guides/production-hardening.mdx
@@ -337,18 +337,18 @@ spec:
           port: 6379
 ```
 
-**Infrastructure firewall considerations**. In addition to the universal host firewalls, implement cloud-level security:
+**Infrastructure firewall considerations**. In addition to the universal host firewalls, implement infrastructure-level security:
 
-```bash
-# Example: AWS Security Groups, Azure NSGs, or GCP Firewall Rules
-# Allow ingress from load balancer to NodePort/ClusterIP service
-# Allow egress to managed databases
-# Block all other traffic
+For cloud deployments (AWS Security Groups, Azure NSGs, or GCP Firewall Rules):
 
-# For on-premises, ensure node-level firewalls allow:
-# - Ingress traffic from ingress controllers
-# - Egress traffic to external services (databases, SMTP)
-```
+- Allow ingress from load balancer to NodePort/ClusterIP service
+- Allow egress to managed databases
+- Block all other traffic
+
+For on-premises deployments, ensure node-level firewalls allow:
+
+- Ingress traffic from ingress controllers
+- Egress traffic to external services (databases, SMTP)
 
 #### Access Control