docs: use anchoring, rearrange section on Telemetry

Signed-off-by: Logan Blyth <[email protected]>

Author: mrbojangles3

docs/install-upgrade/config.md

@@ -25,7 +25,7 @@ Or import existing `fab.yaml` and wiring files:
 
 After the above workflow a user will have a .img file suitable for installing the control node, then bringing up the switches which comprise the fabric.
 
-## Complete Fab.yaml Example File
+## Complete Fab.yaml Example File <a name="example-file"></a>
 
 ``` { .yaml .annotate title="fab.yaml" linenums="1"} 
 apiVersion: fabricator.githedgehog.com/v1beta1
@@ -114,7 +114,7 @@ In order to avoid conflicts, do not use the following usernames: `operator`,`hha
 
 ### NTP and DHCP
 The control node uses public NTP servers from Cloudflare and Google by default.
-The control node runs a DHCP server on the management network. See the [example file](#complete-example-file).
+The control node runs a DHCP server on the management network. See the [example file](#example-file).
 
 ### Control Node
 The control node is the host that manages all the switches, runs k3s, and serves images. 
@@ -131,15 +131,6 @@ API](https://prometheus.io/docs/specs/prw/remote_write_spec/) and Loki API. Metr
 errors, operational status, transceivers, fans, power supplies, temperature
 sensors, BGP neighbors, LLDP neighbors, and more. Logs include Hedgehog agent logs.
 
-Telemetry can be enabled after installation of the fabric. Open the following
-YAML file in an editor on the control node. Modify the fields as needed. Logs
-can be pushed to a grafana instance at the customer environment, or to grafana
-cloud. To enable the telemetry after install use:
-
-``` shell
-kubectl patch -n fab --type merge fabricator/default --patch-file telemetry.yaml
-```
-
 ```{ .yaml title="telemetry.yaml" linenums="1" }
 spec:
   config:
@@ -173,5 +164,14 @@ spec:
         collectSyslogEnabled: true # collect /var/log/syslog on switches and forward to the lokiTargets
 ```
 
+Telemetry can be enabled after installation of the fabric. Open the following
+YAML file in an editor on the control node. Modify the fields as needed. Logs
+can be pushed to a grafana instance at the customer environment, or to grafana
+cloud. To enable the telemetry after install use:
+
+``` shell
+kubectl patch -n fab --type merge fabricator/default --patch-file telemetry.yaml
+```
+
 For additional options, see the `AlloyConfig` [struct in Fabric repo](https://github.com/githedgehog/fabric/blob/master/api/meta/alloy.go).