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.

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

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

3. - [x] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

https://github.com/stolostron/rhacm-docs/blob/2.14_stage/clusters/discovery/discovery_config_ui.adoc#discovery-console

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12

Doc staged repo within the ACM Workspace:
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:
  • In MCE 2.9, users can now apply more comprehensive filters to the DiscoveryConfig resource, including infrastructure providers, cluster types, and regions. While most filters can be configured through both the CLI and the UI, the region filter is currently available only via the CLI.

• [x] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:
  • Cluster admin or access to the DiscoveryConfig CR instance.

• [x] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)
  • Discovered cluster resources should reflect the filters specified in the DiscoveryConfig, displaying only the resources that match the user's applied criteria when listed in the cluster.

• [x] Add link to dev story here: https://issues.redhat.com/browse/ACM-18705

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

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 7/16/25:

Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

Key Areas to Verify:

1. What functionality should QE focus on? List what was tested or what is most important to validate.
2. Ensure the new validation messages appear for required fields
3. Confirm the workflow still completes as expected after validation fixes
4. Any edge cases or high-risk areas touched by the change

Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link