Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: bene2k1

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

@@ -1,6 +1,6 @@
 ---
 meta:
-  title: Deploying an NGINX ingress controller on Scaleway Kubernetes Kapsule with a LoadBalancer
+  title: Deploying an NGINX ingress controller on Scaleway Kubernetes Kapsule with a Load Balancer
   description: This page explains how to expose an application via an ingress object, and using a Load Balancer to make the IP persistent.
 content:
   h1: Exposing a Kubernetes Kapsule ingress controller service with a Load Balancer
@@ -17,7 +17,7 @@ dates:
 This guide walks you through the process of deploying an NGINX ingress controller on Scaleway's Kubernetes Kapsule service.
 We will configure a Load Balancer that uses a persistent IP address, which is essential for maintaining consistent routing. Additionally, we will enable the PROXY protocol to preserve client information such as the original IP address and port, which is recommended for applications that need to log or act on this data.
 
-The guide also delves into the differences between ephemeral and persistent IP addresses, helping you understand when and why to use each type. To complete the guide, we will deploy a demo application that illustrates the entire setup.
+We will explore the differences between ephemeral and persistent IP addresses, helping you understand when and why to use each type, and guide you through deploying a demo application that illustrates the entire setup.
 
 By the end of this guide, you should have a robust and well-configured NGINX ingress controller running on Scaleway's Kubernetes platform.
 
@@ -42,7 +42,7 @@ On Scaleway Kapsule, the LoadBalancer service provisions a Scaleway Load Balance
 - Ephemeral IP: Dynamically assigned by Scaleway when a LoadBalancer service is created. It may change if the service is deleted and recreated, requiring DNS updates.
 - Persistent IP: A flexible IP reserved via the Scaleway API, CLI or console, ensuring consistency across service recreations. This is recommended for production to maintain stable DNS records.
 
-### PROXY Protocol
+### PROXY protocol
 The PROXY protocol allows the LoadBalancer to forward the client's original IP address to the ingress controller, preserving source information for logging and security.
 
 ## Deploying the ingress controller