Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [X] Mandatory: Add the required version to the Fix version/s field.

2. - [X] Mandatory: Choose the type of documentation change or review.

• [ ] We need to update to an existing topic

• [ ] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [X] We need a z-Stream (Errata) Advisory and Release note
  for MCE and/or ACM

3. - [ ] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:

• Published doc: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10
• Source: https://github.com/stolostron/rhacm-docs

4. - [X] Mandatory for GA content:

• [X] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:
  *1. Deploy a certificate policy with a SAN entries in the certificate.
  2. When there is a violation of this policy, two expositional messages are given. For example: "1 CA certificates expire in less than 25h0m0s: default:rsa-ca-sample-secret 1 certificates defined SAN entries do not match pattern Allowed: [[:digit:]] Disallowed: [[:alpha:]]: default:rsa-ca-sample-secret"
  3. Click the export button, there is a newline embedded in between the messages which make the csv unusable.*

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

• [ ] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

• [ ] Add link to dev story here:

5. - [X] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.
In this narrow case, the csv cannot be used because a newline is corrupting the formatting. This should be make public in the release notes