un nest the sections

website/content/docs/k8s/annotations-and-labels.mdx

@@ -67,26 +67,26 @@ Resource annotations could be used on the Kubernetes pod to control connect-inje
 - `consul.hashicorp.com/connect-service-upstreams` - The list of upstream
   services that this pod needs to connect to via Connect along with a static
   local port to listen for those connections. When transparent proxy is enabled,
-  this annotation is optional.
-
-  - There are a few formats this annotation can take:
+  this annotation is optional. There are a few formats this annotation can take:
 
     - Unlabeled:
-         Use the unlabeled annotation format to specify a service name, Consul Enterprise namespaces and partitions,
-        and datacenters. To use [cluster peering](/docs/connect/cluster-peering/k8s) with upstreams, use the following labeled format.
-        - Service name: Place the service name at the beginning of the annotation to specify the upstream service. You can also append the datacenter where the service is deployed (optional). 
+       Use the unlabeled annotation format to specify a service name, Consul Enterprise namespaces and partitions, and
+       datacenters. To use [cluster peering](/docs/connect/cluster-peering/k8s) with upstreams, use the following
+       labeled format.
+      - Service name: Place the service name at the beginning of the annotation to specify the upstream service. You can
+      also append the datacenter where the service is deployed (optional).
         ```yaml
         annotations:
           "consul.hashicorp.com/connect-service-upstreams":"[service-name]:[port]:[optional datacenter]"
         ```
-
-        - Namespace (requires Consul Enterprise 1.7+): Upstream services may be running in different a namespace. Place the upstream namespace after the service name. Refer to  [Consul Enterprise Namespaces](#consul-enterprise-namespaces) for additional details about configuring the injector.
+      - Namespace (requires Consul Enterprise 1.7+): Upstream services may be running in different a namespace. Place
+      the upstream namespace after the service name. Refer to  [Consul Enterprise
+      Namespaces](#consul-enterprise-namespaces) for additional details about configuring the injector.
         ```yaml
         annotations:
           "consul.hashicorp.com/connect-service-upstreams":"[service-name].[service-namespace]:[port]:[optional datacenter]"
         ```
         If the namespace is not specified, the annotation will default to the namespace of the source service.
-
         If you are not using Consul Enterprise 1.7+, Consul will interpret the value placed in the namespace position as part of the service name.
 
         - Admin partitions (requires Consul Enterprise 1.11+): Upstream services may be running in a different
@@ -97,7 +97,8 @@ Resource annotations could be used on the Kubernetes pod to control connect-inje
           annotations:
             "consul.hashicorp.com/connect-service-upstreams":"[service-name].[service-namespace].[service-partition]:[port]:[optional datacenter]"
           ```
-      - [Prepared queries](/docs/connect/proxies#dynamic-upstreams-require-native-integration): Prepend the annotation with `prepared_query` and place the name of the query at the beginning of the string. 
+    - [Prepared queries](/docs/connect/proxies#dynamic-upstreams-require-native-integration): Prepend the annotation
+      with `prepared_query` and place the name of the query at the beginning of the string.
       ```yaml
       annotations:
         'consul.hashicorp.com/connect-service-upstreams': 'prepared_query:[query name]:[port]'