test undo enumeration

examples/custom-resources/transport-server-sni/README.md

@@ -11,7 +11,7 @@ In this example we create two different TransportServers that listen on the same
         protocol: TCP
 ```
 
-2. Add a custom port to the NGINX Ingress Controller pod with the Helm chart.
+1. Add a custom port to the NGINX Ingress Controller pod with the Helm chart.
 
 ```yaml
 controller.customPorts:
@@ -20,7 +20,7 @@ controller.customPorts:
       protocol: TCP
 ```
 
-3. Add a custom port to the NGINX Ingress Controller service.
+1. Add a custom port to the NGINX Ingress Controller service.
 
 ```yaml
 controller.service.customPorts:
@@ -30,22 +30,22 @@ controller.service.customPorts:
             targetPort: 7000 
 ```
 
-4. Use `kubectl` to create the cafe-secret, and mongo-secret. These secrets are used for TLS in the TransportServers.
+1. Use `kubectl` to create the cafe-secret, and mongo-secret. These secrets are used for TLS in the TransportServers.
 `kubectl apply -f cafe-secret.yaml`
 `kubectl apply -f mongo-secret.yaml`
 
-5. Create the mongo and tcp echo example applications.
+1. Create the mongo and tcp echo example applications.
 `kubectl apply -f mongo.yaml`
 `kubectl apply -f tcp-echo-server.yaml`
 
-6. Wait until these are ready.
+1. Wait until these are ready.
 `kubectl get deploy -w`
 
-7. Create the TransportServers for each application.
+1. Create the TransportServers for each application.
 `kubectl apply -f cafe-transport-server.yaml`
 `kubectl apply -f mongo-transport-server.yaml`
 
-8. Ensure they are in valid state.
+1. Ensure they are in valid state.
 `kubectl get ts`
 
 ```bash
@@ -54,7 +54,7 @@ cafe-ts    Valid   AddedOrUpdated   2m
 mongo-ts   Valid   AddedOrUpdated   2m
 ```
 
-9. Set up /etc/hosts or DNS
+1. Set up /etc/hosts or DNS
 This example uses a local NGINX Ingress Controller instance, so the /etc/hosts file
 is being used to set cafe.example.com and mongo.example.com to localhost.
 In a production instance, the server names would be set at the DNS layer.
@@ -66,10 +66,10 @@ In a production instance, the server names would be set at the DNS layer.
 127.0.0.1 mongo.example.com
 ```
 
-10. Expose port 7000 of the LoadBalancer service.
+1. Expose port 7000 of the LoadBalancer service.
 `k port-forward svc/my-release-nginx-ingress-controller 7000:7000`
 
-11. Use `ncat` to ping cafe.example.com on port 7000 with SSL.
+1. Use `ncat` to ping cafe.example.com on port 7000 with SSL.
 `ncat --ssl cafe.example.com 7000`
 When you write a message you should receive the following response:
 
@@ -86,7 +86,7 @@ The request and response should both be 2 bytes.
 127.0.0.1 [24/Sep/2024:15:48:58 +0000] TCP 200 3 3 2.702 "-
 ```
 
-12. Use mongosh to connect to the mongodb container through the TransportServer on port 7000.
+1. Use mongosh to connect to the mongodb container through the TransportServer on port 7000.
 `mongosh --host mongo.example.com --port 7000 --tls --tlsAllowInvalidCertificates`
 
 ```bash