Add code review

Author: bjee19

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

@@ -63,6 +63,15 @@ EOF
 This gateway defines a single listener on port 80. Since no hostname is specified, this listener matches on all hostnames.
 After creating the Gateway resource, NGINX Gateway Fabric will provision an NGINX Pod and Service fronting it to route traffic.
 
+Save the public IP address and port of the NGINX Service into shell variables:
+
+   ```text
+   GW_IP=XXX.YYY.ZZZ.III
+   GW_PORT=<port number>
+   ```
+
+{{< note >}}In a production environment, you should have a DNS record for the external IP address that is exposed, and it should refer to the hostname that the gateway will forward for.{{< /note >}}
+
 The [HTTPRoute](https://gateway-api.sigs.k8s.io/api-types/httproute/) is typically deployed by the [application developer](https://gateway-api.sigs.k8s.io/concepts/roles-and-personas/#roles-and-personas_1). To deploy the `coffee` HTTPRoute:
 
 ```yaml
@@ -147,15 +156,6 @@ This HTTPRoute has a few important properties:
 
 ### Send traffic to Coffee
 
-Save the public IP address and port of the NGINX Service into shell variables:
-
-   ```text
-   GW_IP=XXX.YYY.ZZZ.III
-   GW_PORT=<port number>
-   ```
-
-{{< note >}}In a production environment, you should have a DNS record for the external IP address that is exposed, and it should refer to the hostname that the gateway will forward for.{{< /note >}}
-
 Using the external IP address and port for the NGINX Service, we can send traffic to our coffee applications.
 
 {{< note >}} If you have a DNS record allocated for `cafe.example.com`, you can send the request directly to that hostname, without needing to resolve. {{< /note >}}