gep-1234: Formatting fixes around use cases for GAMMA initiative

Author: David Yu

site-src/geps/gep-1324.md

@@ -42,18 +42,18 @@ These use-cases are presented as an aid for discussion, and as frames of referen
     6. I want to be able to gradually opt-in to a mesh (no mesh, L4 only, L7 enabled) so I can choose the right fit for my application's performance and compatibility goals.
     7. I want to define access policies for my service
 2. As a service consumer…
-    8. I want to change the behavior (such as timeouts, retries, header manipulation) when my application connects to services through configuration, rather than modifying my application.
-    9. I want to collect HTTP metrics for services I connect to.
-    10. I want to be able to connect to Kubernetes Services and external services.
-    11. I want to override the destination of my traffic, for example, to send requests to external services to an internal replica, or to send all requests to an egress proxy.
+    1. I want to change the behavior (such as timeouts, retries, header manipulation) when my application connects to services through configuration, rather than modifying my application.
+    2. I want to collect HTTP metrics for services I connect to.
+    3. I want to be able to connect to Kubernetes Services and external services.
+    4. I want to override the destination of my traffic, for example, to send requests to external services to an internal replica, or to send all requests to an egress proxy.
 3. As a mesh administrator…
-    12. I want to enforce that all traffic within my cluster is encrypted.
-    13. I want to have strict isolation and control at namespace level, so a bug/malicious user can't impact other namespaces
-    14. I want to be able to allow app owners to gradually opt-in to a mesh (no mesh, L4 only, L7 enabled) so they can choose the right fit for their applications’ performance and compatibility goals.
-    15. Since mesh can be multi-tenant and hosting multiple services (e.g. foo or bar), as a mesh administrator I need to make sure a client can discover different services. Here are few possible ways
-        1. Each service is allocated a unique IP and port
-        2. Or Each service must use unique Host name
-        3. Or a unique port and protocol,  (80:http, 443 tls)
+    1. I want to enforce that all traffic within my cluster is encrypted.
+    2. I want to have strict isolation and control at namespace level, so a bug/malicious user can't impact other namespaces
+    3. I want to be able to allow app owners to gradually opt-in to a mesh (no mesh, L4 only, L7 enabled) so they can choose the right fit for their applications’ performance and compatibility goals.
+    4. Since mesh can be multi-tenant and hosting multiple services (e.g. foo or bar), as a mesh administrator I need to make sure a client can discover different services. Here are few possible ways
+      1. Each service is allocated a unique IP and port
+      2. Or Each service must use unique Host name
+      3. Or a unique port and protocol,  (80:http, 443 tls)
 
 ## Glossary