Merge pull request #49034 from rh-tokeefe/OSSMDOC-650

OSSMDOC-650: Clarify JWKS write up in release notes

Author: JStickler

modules/ossm-rn-known-issues.adoc

@@ -34,9 +34,9 @@ These are the known issues in {SMProductName}:
 
 * link:https://github.com/istio/istio/issues/14743[Istio-14743] Due to limitations in the version of Istio that this release of {SMProductName} is based on, there may be applications that are currently incompatible with {SMProductShortName}. See the linked community issue for details.
 
-* https://issues.redhat.com/browse/OSSM-1668[OSSM-1668] `jwksResolverCA` field is missing in `SMCP`. If you upgrade from Service Mesh operator 2.1.3 to Service Mesh operator 2.2, then the `jwksResolverCA` field is not supported.
+* https://issues.redhat.com/browse/OSSM-1668[OSSM-1668] A new field `spec.security.jwksResolverCA` was added to the Version 2.1 `SMCP` but is missing in the 2.2.0 and 2.2.1 releases. When upgrading from an Operator version where this field was present to an Operator version that is missing this field, the `.spec.security.jwksResolverCA` field is not available in the `SMCP`.
 +
-Workaround: Use the `techPreview` `jwksResolverExtraRootCA` field to enable additional JWKS CA certificates.
+Workaround: To enable additional JSON Web Key Set CA certificates when using an Operator version that is missing `spec.security.jwksResolverCA`, the workaround is to use the `spec.techPreview jwksResolverExtraRootCA` field.
 
 //Keep OSSM-1655 in RN, closed as "explained" error is expected.
 * https://issues.redhat.com/browse/OSSM-1655[OSSM-1655] Kiali dashboard shows error after enabling mTLS in `SMCP`.