Fix broken link

website/content/docs/api-gateway/upgrade-specific-versions.mdx

@@ -97,7 +97,7 @@ Ensure that the following requirements are met prior to upgrading:
 
 1. Inspect the `secret` entries for each of the routes.
 
-  If a `namespace` field is not defined in the `secret` or if the namespace matches the namespace of the parent `Gateway`, then no additional action is required for the `secret`. Otherwise, note the `namespace` field values for `secret` configurations that have a `namespace` defined that do not match the namespace of the parent `Gateway`. You must also note the `namespace` of the parent gateway. You will need these to create a `ReferencePolicy` that explicitly allows each cross-namespace secret-to-gateway pair to prevent the route from breaking (see [step 5](#create-secret-reference-grant)).
+  If a `namespace` field is not defined in the `secret` or if the namespace matches the namespace of the parent `Gateway`, then no additional action is required for the `secret`. Otherwise, note the `namespace` field values for `secret` configurations that have a `namespace` defined that do not match the namespace of the parent `Gateway`. You must also note the `namespace` of the parent gateway. You will need these to create a `ReferencePolicy` that explicitly allows each cross-namespace secret-to-gateway pair to prevent the route from breaking (see [step 5](#create-secret-reference-policy)).
 
   After completing this step, you will have a list of all secrets similar to the following:
 
@@ -142,7 +142,7 @@ Ensure that the following requirements are met prior to upgrading:
   </CodeBlockConfig>
 
   If your output is empty, proceed with the [standard-upgrade](#standard-upgrade).
-<a name="create-reference-grant-secret"/>
+<a name="create-secret-reference-policy"/>
 
 1. Using the list of secrets you created earlier as a guide, create a [`ReferencePolicy`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.ReferencePolicy) to allow each gateway cross namespace secret access.
   The `ReferencePolicy` explicitly allows each cross-namespace gateway to secret pair. The `ReferencePolicy` must be created in the same `namespace` as the `Secret`.