Addressed review comments

Author: Jonas Arndt

asciidoc/components/metallb.adoc

@@ -32,7 +32,7 @@ SUSE Edge uses MetalLB in three key ways:
 
 * As a Load Balancer Solution: MetalLB serves as the Load Balancer solution for bare-metal machines.
 * For an HA K3s/RKE2 Setup: MetalLB allows for load balancing the Kubernetes API using a Virtual IP address.
-* As a L3 BGP solution where MetalLB advertises routes to the service IPs to
+* As an L3 BGP solution where MetalLB advertises routes to the service IPs to
   nearby routers.
 
 [NOTE]

asciidoc/guides/metallb-k3s_l3.adoc

@@ -15,15 +15,15 @@ endif::[]
 
 MetalLB is a load-balancer implementation for bare-metal Kubernetes clusters, using standard routing protocols.
 
-In this guide, we demonstrate how to deploy MetalLB in layer 3 (L3) mode.
+In this guide, we demonstrate how to deploy MetalLB in layer 3 (L3) BGP mode.
 
 == Why use MetalLB
 
 MetalLB is a compelling choice for load balancing in bare-metal Kubernetes clusters for several reasons:
 
 . Native Integration with Kubernetes: MetalLB seamlessly integrates with Kubernetes, making it easy to deploy and manage using familiar Kubernetes tools and practices.
 . Bare-Metal Compatibility: Unlike cloud-based load balancers, MetalLB is designed specifically for on-premises deployments where traditional load balancers might not be available or feasible.
-. Supports Multiple Protocols: MetalLB supports both Layer 2 and BGP (Border Gateway Protocol) modes, providing flexibility for different network architectures and requirements.
+. Supports Multiple Protocols: MetalLB supports both Layer 2 and Layer 3 BGP (Border Gateway Protocol) modes, providing flexibility for different network architectures and requirements.
 . High Availability: By distributing load-balancing responsibilities across multiple nodes, MetalLB ensures high availability and reliability for your services.
 . Scalability: MetalLB can handle large-scale deployments, scaling alongside your Kubernetes cluster to meet increasing demand.
 
@@ -33,14 +33,14 @@ The major advantage of the layer 2 mode is its universality: it works on any Eth
 
 == MetalLB on K3s (using L3)
 
-In this quick start, L3 mode will be used.
+In this quick start, L3 mode is used.
 This means that we need to have neighboring router(s) with BGP capabilities within
 the network range.
 
 == Prerequisites
 
 * A K3s cluster where MetalLB is going to be deployed.
-* Router(s) on the network that support the BGP protocol
+* Router(s) on the network that support the BGP protocol.
 * A free IP address within the network range for the service. In this example
   `192.168.10.100`
 
@@ -77,7 +77,7 @@ done
 
 == Configuration
 
-At this point, the installation is completed. Now it is time to create an
+. At this point, the installation is completed. Now it is time to create an
 IPAddressPool: 
 
 [,bash]
@@ -108,7 +108,8 @@ spec:
 EOF
 ----
 
-We will also configure a BGPPeer. Note that the FRR router has ASN 1000 while
+[start=2]
+. We will also configure a BGPPeer. Note that the FRR router has ASN 1000 while
 our BGPPeer will have 1001. We can also see that the FRR Router has an IP
 address that is 192.168.3.140.
 
@@ -128,7 +129,8 @@ spec:
 EOF
 ----
 
-After this we will need to create the BGPAdvertisement (L3):  
+[start=3]
+. After this we will need to create the BGPAdvertisement (L3):  
 
 [,bash]
 ----
@@ -146,9 +148,7 @@ EOF
 
 == Usage
 
-At this point we can create an example application with a service. In our case
-that service will have the IP address from our IPAddressPool: 192.168.10.100.
-
+Create an example application with a service. In this case, IP address from the `IPAddressPool` is `192.168.10.100` for that service.
 
 [,bash]
 ----
@@ -199,8 +199,7 @@ EOF
 ----
 
 
-Let us see it in action: If you log onto the FRR Router you can see the routes
-created from the BGP advertisement
+To verify, log onto the FRR Router to can see the routes created from the BGP advertisement.
 
 [,console]
 ----
@@ -231,9 +230,7 @@ NAME               TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)
 hello-kubernetes   LoadBalancer   10.43.127.75   192.168.122.11   80:31461/TCP   8s
 ----
 
-If this router is the default gateway for your network, you can run a simple
-curl command from a box on that network to verify that they can reach the httpd
-sample app:
+If this router is the default gateway for your network, you can run the `curl` command from a box on that network to verify that they can reach the httpd sample app
 
 [,console]
 ----