Making update permission optional

Author: Shubha Narayanan

modules/cert-manager-configuring-routes.adoc

@@ -11,7 +11,7 @@ The following steps demonstrate the process of utilizing the {cert-manager-opera
 .Prerequisites
 
 * You have installed version 1.14.0 or later of the {cert-manager-operator}.
-* You have the `create` and `update` permissions on the `routes/custom-host` sub-resource.
+* You have `create` permission on the `routes/custom-host` sub-resource that helps create and update routes.
 * You have a `Service` resource that you want to expose.
 
 .Procedure

modules/nw-ingress-route-secret-load-external-cert.adoc

@@ -16,7 +16,7 @@ This feature applies to both edge routes and re-encrypt routes.
 .Prerequisites
 
 * You must enable the `RouteExternalCertificate` feature gate.
-* You must have the `create` and `update` permissions on the `routes/custom-host`.
+* You have `create` permission on the `routes/custom-host` sub-resource that helps create and update routes.
 * You must have a secret containing a valid certificate/key pair in PEM-encoded format of type `kubernetes.io/tls`, which includes both `tls.key` and `tls.crt` keys.
 * You must place the referenced secret in the same namespace as the route you want to secure.