Update docs/operator-manual/upgrading/2.14-3.0.md

Co-authored-by: rumstead <[email protected]>
Signed-off-by: Regina Voloshin <[email protected]>

docs/operator-manual/upgrading/2.14-3.0.md

@@ -33,7 +33,7 @@ server.rbac.log.enforce.enable: "true"
 
 Users who have the above setting in place, would be unaffected by this change and don't need to perform any additional action. It is recommended though to delete this setting from the `argocd-cm` ConfigMap.
 
-Users who either have `server.rbac.log.enforce.enable` set to `false` or don't have this setting at all in their `argocd-cm` ConfigMap will have to explicitly grant `logs, get` access, as this flag (and it's default behaviour of `false`) has been deprecated.
+Users who either have `server.rbac.log.enforce.enable` set to `false` or don't have this setting at all in their `argocd-cm` ConfigMap will have to explicitly grant `logs, get` access, as this flag (and it's default behaviour of `false`) has been removed.
 Similarly to the way you currently manage the access to Applications, the access to logs can be either granted on a Project scope level (Project resource) or on the global level scope (`argocd-rbac-cm` ConfigMap resource).
 
 ## Other changes