fix(lb): review (#3972)

Author: RoRoJ

network/load-balancer/reference-content/sni-route-deprecation.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: Learn more about the deprecation of SNI routes with HTTP backends for Scaleway Load Balancers
 tags: load-balancer sni http routes backend
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-14
 categories: 
   - load-balancer
   - network
@@ -18,7 +18,7 @@ This page documents the deprecation of SNI routes with HTTP backends on Scaleway
 We removed the ability to create SNI based [routes](/network/load-balancer/how-to/create-manage-routes/) to HTTP backends in Scaleway Load Balancer. This feature was deprecated on March 1st 2023, and removed on June 1st 2023.
 
 - SNI routes are still available and supported for TCP backends.
-- SNI routes with HTTP backends are no longer be available.
+- SNI routes with HTTP backends are no longer available.
 - SNI routes to an HTTP backend were automatically converted to new **HTTP Host header**-based routes.
 
 ## Why did we deprecate this feature?
@@ -31,7 +31,7 @@ While this proves to be efficient since it avoids all the overhead related to TC
 
 When using HTTP protocol to the backend servers, the best solution is then to terminate TLS at the Load Balancer, decrypt traffic, look at the HTTP host header value to select the appropriate backend, and then forward the request to selected backend with or without encryption based on your use case. Since the protocol to the backend is HTTP, the Load Balancer has access to all the HTTP protocol metadata. There is then no point to limiting it to TCP/TLS layer metadata. 
 
-This is why we have decided to remove the ability to create SNI based routes when the backend protocol is HTTP, and are now instead proposing HTTP Host header routes.
+This is why we decided to remove the ability to create SNI based routes when the backend protocol is HTTP, and are now instead proposing HTTP Host header routes.
 
 See the console screenshots below as examples: