Apply suggestions from code review

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

Author: 3 people

pages/load-balancer/reference-content/migrating-aws.mdx

@@ -53,11 +53,11 @@ Scaleway Load Balancer offers the following features:
 - HTTP Host header and SNI routes
 
 **Backend:**
-- HTTP, HTTPS, TCP and TLS support
+- HTTP, HTTPS, TCP, and TLS support
 - Balancing between Scaleway resources (Instances, Elastic Metal servers, Dedibox) identified by public or private IP, or between non-SCW resources with selected plans 
 - Configurable balancing method: round-robin, least connections, first available
 - Proxy Protocol
-- Sticky sessions (IP based or cookie based)
+- Sticky sessions (IP-based or cookie-based)
 - Customizable health checks
 - Backend protection
 - Customized error page
@@ -88,21 +88,21 @@ The diagram below shows a Scaleway Load Balancer with multiple frontends and bac
 
 ### Application vs Network with Scaleway
 
-To create the equivalent of an AWS **Application Load Balancer**, with Scaleway you will typically create a Load Balancer with:
+To create the equivalent of an AWS **Application Load Balancer** with Scaleway, you will typically create a Load Balancer with:
 
 - One or more frontends listening on port 80 or 443
 - One or more backends configured for HTTP or HTTPS protocol
-- (Optional): Routes from frontends to backends based on HTTP Host headers
+- (Optional) Routes from frontends to backends based on HTTP Host headers
 
-To create the equivalent of an AWS **Network Load Balancer**, with Scaleway you will typically create a Load Balancer with:
+To create the equivalent of an AWS **Network Load Balancer** with Scaleway, you will typically create a Load Balancer with:
 
 - One or more frontends listening on a port matching your application
 - One or more backends configured for TCP protocol
-- (Optional): Routes from frontends to backends based on SNI
+- (Optional) Routes from frontends to backends based on SNI
 
 ## Plans and pricing
 
-Like AWS, the pricing model for Scaleway Load Balancers is based on an hourly rate. Different commercial types of Load Balancer have a different hourly rate, based on:
+Like AWS, the pricing model for Scaleway Load Balancers is based on an hourly rate. Different commercial types of Load Balancers have different hourly rates, based on:
 
 - **Maximum supported bandwidth**
 - **Multicloud support** (whether the Load Balancer can forward traffic to backend servers outside of Scaleway)