site: Update link to service-apis project (#3363)

Updates #3349

Signed-off-by: Steve Sloka <[email protected]>

site/_posts/2020-07-10-Contours-landscape-jul-2020.md

@@ -114,7 +114,7 @@ For each of the examples, we need two things: information on what Contour has co
 In short, we would love to have more support for configuring Envoy with other services. Before we can do that, properly integrating any external service into the overall Contour picture requires foundational work to build the model for if and how Contour interacts with these services. This work has started (see [contour#2325](https://github.com/projectcontour/contour/issues/2325) and [contour#2495](https://github.com/projectcontour/contour/issues/2495) for some example issues), and we would love feedback about our approach and the implementation. Getting this foundational work right is tricky and may take some time, but once we have it done, we should be able to get the actual features out much more easily in the future.
 
 ### Service-APIs and the future of Ingress
-As an Ingress controller, we on the Contour team have been watching the upstream work on Ingress v1 and contributing to the the [Service-APIs subproject of Kubernetes SIG-Network](https://kubernetes-sigs.github.io/service-apis) (which started out of Ingress V2 work, and has a similar forward looking design to HTTPProxy). Contour is committed to migrating Ingress support to Ingress v1 as soon as support windows allow ([contour#2139](https://github.com/projectcontour/contour/issues/2139)), and are actively contributing to the Service APIs subproject, with the aim of bringing Contour support for the new Service APIs objects as soon as they have enough behavior defined to be implementable.
+As an Ingress controller, we on the Contour team have been watching the upstream work on Ingress v1 and contributing to the the [Service-APIs subproject of Kubernetes SIG-Network](https://kubernetes-sigs.github.io/gateway-api) (which started out of Ingress V2 work, and has a similar forward looking design to HTTPProxy). Contour is committed to migrating Ingress support to Ingress v1 as soon as support windows allow ([contour#2139](https://github.com/projectcontour/contour/issues/2139)), and are actively contributing to the Service APIs subproject, with the aim of bringing Contour support for the new Service APIs objects as soon as they have enough behavior defined to be implementable.
 
 
 ## We want your feedback