Apply suggestions from code review

Co-authored-by: Benedikt Rollik <[email protected]>
Co-authored-by: Jessica <[email protected]>
Co-authored-by: ldecarvalho-doc <[email protected]>

Author: 4 people

pages/load-balancer/troubleshooting/certificates.mdx

@@ -82,11 +82,3 @@ Check the following documentation:
 - [Setting up SSL bridging, offloading or passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/)
 - [Load Balancer API Documentation: Certificates](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-certificate-get-an-ssltls-certificate)
 - [Load Balancer Terraform Documentation: Certificates](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/lb_certificate)
-
-
-
-
-     
-
-
-    

pages/load-balancer/troubleshooting/configuration.mdx

@@ -87,11 +87,11 @@ You may find that traffic is not being filtered as expected via your Load Balanc
 
 ### Cause
 
-Instance Security Groups and/or Load Balancer ACLs are incorrectly configured.
+Instance security groups and/or Load Balancer ACLs are incorrectly configured.
 
 ### Solution
 
-Instance [Security Groups](instances/how-to/use-security-groups/) should still filter public traffic arriving on your backend server Instances, as long as that traffic is arriving over the public interface. This means the Instance in question must be attached to the Load Balancer via its public IP and not any private IP.
-- Ensure that your Instance is attached via its public IP address. If your Instance behind a Load Balancer is attached via a private IP address, the Security Group rules will not be applied.
-- Double check your [Security Group rules](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings), to verify that they correspond to the required ports, protocols and IP addresses configured for your Load Balancer
+Instance [security groups](instances/how-to/use-security-groups/) should still filter public traffic arriving on your backend server Instances, as long as that traffic is arriving over the public interface. This means the Instance in question must be attached to the Load Balancer via its public IP and not any private IP.
+- Ensure that your Instance is attached via its public IP address. If your Instance behind a Load Balancer is attached via a private IP address, the security group rules will not be applied.
+- Double check your [security group rules](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings), to verify that they correspond to the required ports, protocols, and IP addresses configured for your Load Balancer
 - To filter incoming traffic to your backend servers **as it passes through the Load Balancer**, use [Load Balancer ACLs](/load-balancer/how-to/create-manage-acls/).

pages/load-balancer/troubleshooting/k8s-errors.mdx

@@ -16,11 +16,11 @@ categories:
 If you are experiencing errors with your Kubernetes Kapsule Load Balancer. This page helps you find solutions to some of the most common problems.
 
 <Message type="important">
-You should **never** try to create or modify a Kubernetes Kapsule's Load Balancer via the Scaleway console, the API, or any other devtools.
+You should **never** try to create or modify a Kubernetes Kapsule's Load Balancer via the Scaleway console, the API, or any other developer tools.
 
 This leads to unexpected and unreliable behaviour, as the cluster's **C**loud **C**ontroller **M**anager is unaware of the Load Balancer and attempts to overwrite configurations made in the console.
 
-Always provision and modify Kubernetes Load Balancers via the [CCM](/kubernetes/reference-content/kubernetes-load-balancer/#creating-a-load-balancer-for-your-cluster-overview). Use [annotations](/kubernetes/reference-content/kubernetes-load-balancer/#defining-your-load-balancers-configuration-via-annotations) to modify configure your cluster’s Load Balancer.
+Always provision and modify Kubernetes Load Balancers via the [CCM](/kubernetes/reference-content/kubernetes-load-balancer/#creating-a-load-balancer-for-your-cluster-overview). Use [annotations](/kubernetes/reference-content/kubernetes-load-balancer/#defining-your-load-balancers-configuration-via-annotations) to configure your cluster’s Load Balancer.
 </Message>
 
 ## I'm experiencing connectivity issues with my Kubernetes Load Balancer
@@ -33,10 +33,10 @@ A configuration issue is preventing successful communication between your Load B
 
 ### Solutions
 
-- Ensure that you provisioned and configured your Load Balancer via Kubernetes nad not via the Scaleway console, which provokes unexpected behaviors and errors.
+- Ensure that you provisioned and configured your Load Balancer via Kubernetes and not via the Scaleway console, which provokes unexpected behaviors and errors.
 - Verify that the required service is running on all nodes. If it is missing from some nodes, this could be causing health checks to fail.
 - Check  your cluster's `externalTrafficPolicy` setting. If it is set to `Local` instead of `Cluster`, this could be causing the issue. Change the policy to `Cluster`.
-- Try enabling or disabling Cloudflare's Proxy Mode, which may be affecting connectivity
+- Try enabling or disabling Cloudflare's Proxy Mode, which may be affecting connectivity.
 
 
 ## My certificate is not being resolved when accessing my Kubernetes Load Balancer from within the cluster