Merge pull request #56005 from kquinn1204/TELCODOCS-1179

TELCODOCS-1179 fixing BGP communities doc bugs

Author: mjpytlak

modules/nw-metallb-community-cr.adoc

@@ -10,7 +10,7 @@ The `community` custom resource is a collection of aliases for communities. User
 
 [NOTE]
 ====
-The `community` CRD applies only to BGPAdvertisement. 
+The `community` CRD applies only to BGPAdvertisement.
 ====
 
 
@@ -33,9 +33,7 @@ Specify the same namespace that the MetalLB Operator uses.
 
 |`spec.communities`
 |`string`
-|Specifies a list of IP addresses for MetalLB to assign to services.
-You can specify multiple ranges in a single pool, they will all share the same settings.
-Specify each range in CIDR notation or as starting and ending IP addresses separated with a hyphen.
+|Specifies a list of BGP community aliases that can be used in BGPAdvertisements. A community alias consists of a pair of name (alias) and value (number:number). Link the BGPAdvertisement to a community alias by referring to the alias name in its `spec.communities` field.
 
 |===
 

modules/nw-metallb-configure-community-bgp-advertisement.adoc

@@ -43,7 +43,7 @@ spec:
 $ oc apply -f ipaddresspool.yaml
 ----
 
-. Create a community alias named `community1`. 
+. Create a community alias named `community1`.
 +
 [source,yaml]
 ----
@@ -55,10 +55,10 @@ metadata:
 spec:
   communities:
     - name: NO_ADVERTISE
-    - value: '65535:65282'
+      value: '65535:65282'
 ----
 
-. Create a BGP peer named `doc-example-bgp-peer`. 
+. Create a BGP peer named `doc-example-bgp-peer`.
 
 .. Create a file, such as `bgppeer.yaml`, with content like the following example:
 +
@@ -98,12 +98,14 @@ spec:
   aggregationLength: 32
   aggregationLengthV6: 128
   communities:
-    - community1
+    - NO_ADVERTISE <1>
   ipAddressPools:
     - doc-example-bgp-community
   peers:
     - doc-example-peer
 ----
++
+<1> Specify the `CommunityAlias.name` here and not the community custom resource (CR) name.
 
 .. Apply the configuration:
 +