docs: fix web terminal step list numbering (argoproj#11590)

docs: fix web terminal step list numbering (argoproj#11590)
Signed-off-by: Nicholas Morey <nicholas@morey.tech>
Signed-off-by: emirot <emirot.nolan@gmail.com>

docs/operator-manual/web_based_terminal.md

@@ -11,24 +11,25 @@ they have the `exec/create` privilege. If the Pod mounts a ServiceAccount token
 Kubernetes), then the user effectively has the same privileges as that ServiceAccount.
 
 ## Enabling the terminal
+<!-- Use indented code blocks for the numbered list to prevent breaking the numbering. See #11590 -->
 
 1. Set the `exec.enabled` key to `"true"` on the `argocd-cm` ConfigMap.
 
 2. Patch the `argocd-server` Role (if using namespaced Argo) or ClusterRole (if using clustered Argo) to allow `argocd-server`
 to exec into pods
-```yaml
-- apiGroups:
-  - ""
-  resources:
-  - pods/exec
-  verbs:
-  - create
-```
-
-3. Add RBAC rules to allow your users to `create` the `exec` resource, i.e.
-```
-p, role:myrole, exec, create, */*, allow
-```
+
+        - apiGroups:
+          - ""
+          resources:
+          - pods/exec
+          verbs:
+          - create
+
+
+3. Add RBAC rules to allow your users to `create` the `exec` resource, i.e. 
+
+        p, role:myrole, exec, create, */*, allow
+
 
 See [RBAC Configuration](rbac.md#exec-resource) for more info.
 
@@ -42,4 +43,4 @@ By default, Argo CD attempts to execute shells in this order:
 4. cmd
 
 If none of the shells are found, the terminal session will fail. To add to or change the allowed shells, change the 
-`exec.shells` key in the `argocd-cm` ConfigMap, separating them with commas.
+`exec.shells` key in the `argocd-cm` ConfigMap, separating them with commas.