Fix broken links and example output (#1373)

Problem: Outdated links and incorrect output in our examples and guides.

Solution: Fix links and output.

Author: kate-osborn

examples/https-termination/README.md

@@ -8,7 +8,7 @@ reference a Secret in a different Namespace.
 
 ## 1. Deploy NGINX Gateway Fabric
 
-1. Follow the [installation instructions](/docs/installation.md) to deploy NGINX Gateway Fabric.
+1. Follow the [installation instructions](https://docs.nginx.com/nginx-gateway-fabric/installation/) to deploy NGINX Gateway Fabric.
 
 1. Save the public IP address of NGINX Gateway Fabric into a shell variable:
 
@@ -195,19 +195,19 @@ You can also check the conditions of the Gateway `https` Listener to verify the
  Conditions:
    Last Transition Time:  2023-06-26T20:23:56Z
    Message:               Certificate ref to secret certificate/cafe-secret not permitted by any ReferenceGrant
-   Observed Generation:   2
+   Observed Generation:   1
    Reason:                RefNotPermitted
    Status:                False
    Type:                  Accepted
    Last Transition Time:  2023-06-26T20:23:56Z
    Message:               Certificate ref to secret certificate/cafe-secret not permitted by any ReferenceGrant
-   Observed Generation:   2
+   Observed Generation:   1
    Reason:                RefNotPermitted
    Status:                False
    Type:                  ResolvedRefs
    Last Transition Time:  2023-06-26T20:23:56Z
    Message:               Certificate ref to secret certificate/cafe-secret not permitted by any ReferenceGrant
-   Observed Generation:   2
+   Observed Generation:   1
    Reason:                Invalid
    Status:                False
    Type:                  Programmed

site/content/how-to/traffic-management/advanced-routing.md

@@ -125,7 +125,7 @@ This request should receive a response from the `coffee-v1` Pod.
 
 ```text
 Server address: 10.244.0.9:8080
-Server name: coffee-v2-68bd55f798-s9z5q
+Server name: coffee-v1-76c7c85bbd-cf8nz
 ```
 
 If we want our request to be routed to `coffee-v2`, then we need to meet the defined conditions. We can include a header:

site/content/how-to/traffic-management/routing-traffic-to-your-app.md

@@ -132,7 +132,7 @@ spec:
 EOF
 ```
 
-This gateway is associated with the NGINX Gateway Fabric through the **gatewayClassName** field. The default installation of NGINX Gateway Fabric creates a GatewayClass with the name **nginx**. NGINX Gateway Fabric will only configure gateways with a **gatewayClassName** of **nginx** unless you change the name via the `--gatewayclass` [command-line flag](/docs/cli-help.md#static-mode).
+This gateway is associated with the NGINX Gateway Fabric through the **gatewayClassName** field. The default installation of NGINX Gateway Fabric creates a GatewayClass with the name **nginx**. NGINX Gateway Fabric will only configure gateways with a **gatewayClassName** of **nginx** unless you change the name via the `--gatewayclass` [command-line flag]({{< relref "/reference/cli-help.md#static-mode" >}}).
 
 We specify a [listener](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Listener) on the gateway to open an entry point on the cluster. In this case, since the coffee application accepts HTTP requests, we create an HTTP listener, named **http**, that listens on port 80.