Merge pull request #792 from david-martin/fix-getting-started-404s

Fix a couple of 404s for getting started

docs/gateways/define-and-place-a-gateway.md

@@ -3,7 +3,7 @@
 In this guide, we will go through defining a Gateway in the OCM hub cluster that can then be distributed to and instantiated on a set of managed spoke clusters.
 
 ### Prerequisites
-* Complete the [Getting Started Guide](https://docs.kuadrant.io/getting-started/) to bring up a suitable environment. 
+* Complete the [Getting Started Guide](https://docs.kuadrant.io/getting-started-multi-cluster/) to bring up a suitable environment. 
 
 If you are looking to change provider from the default Istio:
 * Please have the Gateway provider of your choice installed and configured (in this example we use Envoy gateway. See the following [docs](https://gateway.envoyproxy.io/v0.5.0/user/quickstart.html))

docs/installation/control-plane-installation.md

@@ -83,7 +83,7 @@ gatewayclass.gateway.networking.k8s.io/kuadrant-multi-cluster-gateway-instance-p
 
 **Note:** :exclamation: To manage the creation of DNS records, MGC uses [ManagedZone](https://github.com/Kuadrant/dns-operator/blob/main/docs/reference/managedzone.md) resources. A `ManagedZone` can be configured to use DNS Zones on both AWS (Route53), and GCP (Cloud DNS). Commands to create each are provided below. 
 
-First, depending on the provider you would like to use export the [environment variables detailed here](https://docs.kuadrant.io/getting-started/#config) in a terminal session.
+First, depending on the provider you would like to use export the [environment variables detailed here](https://docs.kuadrant.io/getting-started-multi-cluster/) in a terminal session.
 
 Next, create a secret containing either the AWS or GCP credentials. We'll also create a namespace for your MGC configs: