NO-JIRA: Correct wording in SDN documentation

[saintdle]

What this PR does / why we need it:

Fixes wording in the SDN document as it doesn't read correctly.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # n/a

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[openshift-ci]

Hi @saintdle. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jparrill]

/ok-to-test

[jparrill]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill, saintdle

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jparrill]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jparrill]

/retest

[saintdle]

@jparrill do the other two tests need triggering or can this be merged as is?

[bryan-cox]

Could you update the commit to be in the imperative tone per 6. here - https://hypershift.pages.dev/contribute/#prior-to-submitting-a-pull-request?

[saintdle]

Could you update the commit to be in the imperative tone per 6. here - https://hypershift.pages.dev/contribute/#prior-to-submitting-a-pull-request?

Done

[bryan-cox]

Thanks!

/retitle NO-JIRA: Correct wording in SDN documentation
/lgtm

[openshift-ci-robot]

@saintdle: This pull request explicitly references no jira issue.

In response to this:

What this PR does / why we need it:

Fixes wording in the SDN document as it doesn't read correctly.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # n/a

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@saintdle: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.