Fix inadvertent bolding by escaping wildcard character

Author: gnunn1

content/modules/ROOT/pages/02-argocd-rbac.adoc

@@ -295,7 +295,7 @@ link:https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resourc
 <4> After resource we define the actions for the policy, in this case we use a wildcard, '*', to permit all actions. Many
 different link:https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions[actions, window="_blank"]
 are available.
-<5> Next is the specific Argo CD resource, this can be a wildcard like `*` for all resources or a named resource such as specific Applications. In this case
+<5> Next is the specific Argo CD resource, this can be a wildcard like `\*` for all resources or a named resource such as specific Applications. In this case
 we have `workshop/*` which allows all Applications that belong to the `workshop` Project.
 <6> Finally whether we `allow` or `deny` the permission, in this case we `allow` to grant permissions.
 
@@ -423,7 +423,7 @@ reviewed earlier. While `groups` is the most commonly set scope, having scopes l
 allows you to match roles to individual users. In a nutshell, when adding additional scopes, like `email`, these
 are treated as groups by Argo CD for matching purposes.
 
-We can also define our own policies here, as we can see with the new `role:none` policy that was added as mentioned earlier. 
+We can also define our own policies here, as we can see with the new `role:none` policy that was added as mentioned earlier.
 
 Confirm that you can now see all Projects by going back to Settings > Projects: