Fix typos in Managed Gateway API documentation

Author: przlplx

support/azure/azure-kubernetes/extensions/managed-gateway-api.md

@@ -32,8 +32,8 @@ When AKS successfully installs fresh managed Gateway API CRDs, or takes ownershi
 - `app.kubernetes.io/part-of: <hash>`
 - `eno.azure.io/replace: true`
 
-If these annotations are missing, it's possible that an issue affects the Managed Gateway API CRD provisioning. [Make sure that no conflicts exist in pre-existing installations of the Gateway API CRDs](#step-1-verify-existing-gateway-api-crd-channel-and-bundle-version). Then, try to uninstall and re-install the Managed Gateway CRDs to determine whether the expected annotations are successfully added.
+If these annotations are missing, it's possible that an issue affects the Managed Gateway API CRD provisioning. [Make sure that no conflicts exist in pre-existing installations of the Gateway API CRDs](#step-1-verify-existing-gateway-api-crd-channel-and-bundle-version). Then, try to uninstall and reinstall the Managed Gateway CRDs to determine whether the expected annotations are successfully added.
 
 ## Step 3: Inspect Managed Gateway API CRD version after AKS upgrades
 
-If you upgrade your AKS cluster to a new minor version after you install the Managed Gateway API CRDs, the CRDs are automatically upgraded to the [new supported Gateway API bundle version for that Kubernetes version](/azure/aks/managed-gateway-api#gateway-api-bundle-version-and-aks-kubernetes-version-mapping). You should verify that the Gateway API CRD bundle version is updated accordingly based on the value of the `gateway.networking.k8s.io/bundle-version` annotation. If it's not, try uninstalling and re-installing the Managed Gateway CRDs to see whether the bundle version is updated to the newer version.
+If you upgrade your AKS cluster to a new minor version after you install the Managed Gateway API CRDs, the CRDs are automatically upgraded to the [new supported Gateway API bundle version for that Kubernetes version](/azure/aks/managed-gateway-api#gateway-api-bundle-version-and-aks-kubernetes-version-mapping). You should verify that the Gateway API CRD bundle version is updated accordingly based on the value of the `gateway.networking.k8s.io/bundle-version` annotation. If it's not, try to uninstall and reinstall the Managed Gateway CRDs to see whether the bundle version is updated to the newer version.