Correct PR link for GEP-995 implementation

[craigbox]

While reading https://gateway-api.sigs.k8s.io/geps/gep-2648/#migration-from-single-to-multiple-targets I saw this text:

HTTPRoute.Rules.Name (once they are added in GEP-995, PR at https://github.com/kubernetes-sigs/gateway-api/pull/2593)

Following through I see that 2593 is merged but needs a second PR to actually implement it. I've updated the text to say

HTTPRoute.Rules.Name (once they are added in GEP-995, implementation tracked by #2985)

so people don't have to walk the same path I did.

[k8s-ci-robot]

Hi @craigbox. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[craigbox]

/release-note-none

[mlavacca]

Thanks for fixing this, @craigbox!

/ok-to-test

[craigbox]

/test pull-gateway-api-verify

I'mma call this a flake but leave it to you all to figure out.

[robscott]

Thanks @craigbox!

/lgtm
/approve
/unhold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: craigbox, robscott

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:

• geps/OWNERS [robscott]

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