Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>

Author: bene2k1

pages/kubernetes/reference-content/lb-ingress-controller.mdx

@@ -114,7 +114,7 @@ Use Helm to deploy the NGINX ingress controller with Scaleway-specific configura
     ```
     <Message type="note">
     - The `EXTERNAL-IP` should match your reserved flexible IP (e.g., `195.154.72.226`).
-    - If an ephemeral IP appears, verify that the `loadBalancerIP` field is correctly set and matches a valid flexible IP attached to your Scaleway project.
+    - If an ephemeral IP appears, verify that the `loadBalancerIP` field is correctly set and matches a valid Load Balancer flexible IP attached to your Scaleway Project.
     - Confirm the LoadBalancer in the Scaleway console under **Network > Load Balancers**.
     </Message>
 

pages/kubernetes/reference-content/wildcard-dns.mdx

@@ -33,7 +33,7 @@ In short, Kubernetes wildcard DNS, combined with an ingress controller, provides
 
 ## Overview of key concepts
 
-### ingress controller
+### Ingress controller
 An ingress controller manages external HTTP/HTTPS traffic to services within a Kubernetes cluster based on Ingress resource rules. The NGINX ingress controller is used here.
 
 ### NodePort service
@@ -131,7 +131,7 @@ Use Helm to deploy the NGINX ingress controller with a `NodePort` service and a
 
 6. Configure DNS with round-robin DNS:
     - Use Scaleway’s wildcard DNS (`<cluster-id>.nodes.k8s.<region>.scw.cloud`) for external access.
-        For example for a cluster with ID `39b054d2-5255-4fe3-a327-7ccfac7ffdca` in the `fr-par` region, the DNS is `39b054d2-5255-4fe3-a327-7ccfac7ffdca.nodes.k8s.fr-par.scw.cloud`. This domain name resolves to the public IPs of all nodes in the default pool (e.g., `195.154.72.100`, `195.154.72.101`).
+        For example, for a cluster with ID `39b054d2-5255-4fe3-a327-7ccfac7ffdca` in the `fr-par` region, the DNS is `39b054d2-5255-4fe3-a327-7ccfac7ffdca.nodes.k8s.fr-par.scw.cloud`. This domain name resolves to the public IPs of all nodes in the default pool (e.g., `195.154.72.100`, `195.154.72.101`).
 
     -Alternatively, for a custom domain, map your domain (e.g., `demo.example.com`) to all node IPs via your DNS provider, creating multiple A records:
         ```