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. - [ ] Mandatory: Add the required version to the Fix version/s field.
2.10
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.10/html/networking/networking#installing-subctl-command-utility
• Source: https://github.com/stolostron/rhacm-docs/blob/2.10_stage/networking/submariner/install_subctl.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.

In Section 1.4.3 "Installing the subctl command utility"

Steps 1-4 mention subctl version to download as `v0.16` but it should be `v0.17` 0.16 was used for ACM 2.9. This results in customers using the wrong version of subctl which creates problems during troubleshooting.