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. - [ ] 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. - [ ] *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://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/networking/networking#using-a-customized-submariner-subscription
• Source: https://github.com/stolostron/rhacm-docs/blob/2.12_stage/networking/submariner/subm_customize.adoc

4. - [ ] Mandatory for GA content:

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

In section 1.4.6.5 of Networking Guide, "Using a customized Submariner subscription" there is a field for Channel which currently reads:

Channel: The channel to follow for the subscription. For example, for Red Hat Advanced Cluster Management 2.9, `stable-0.16`.

This should be changed to reflect the appropriate ACM and Submariner versions. For ACM 2.12 it should read:

Channel: The channel to follow for the subscription. For example, for Red Hat Advanced Cluster Management 2.12, `stable-0.19`.

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