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

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

• [x] We need to update to an existing topic

3. - [x] *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:

• https://github.com/stolostron/rhacm-docs/tree/2.13_stage/apis/policy.json.adoc
• https://github.com/stolostron/rhacm-docs/tree/2.13_stage/governance/config_policy_ctrl.adoc

4. - [ ] Mandatory for GA content:

• [ ] Add steps, the diff, known issue, and/or other important conceptual information in the following space:

• [ ] 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.

– The API doc for Policy (which I acknowledge is deprecated) had been updated with fields from ConfigurationPolicy, which was incorrect. These extra fields should be cleaned out.
– The customMessage description for ConfigurationPolicy it appears somehow got a bit lost in translation.

Reference PR: https://github.com/stolostron/rhacm-docs/pull/7521