Apply suggestions from Quentin

Co-authored-by: Quentin Monnet <[email protected]>

Author: mrbojangles3

docs/install-upgrade/config.md

@@ -104,7 +104,7 @@ spec:
 Configuring control node and switch users is done either passing 
 `--default-password-hash` to `hhfab init` or editing the resulting `fab.yaml` 
 file emitted by `hhfab init`.  The default username on the control node is
-core. 
+`core`.
 
 #### Switch Users
 There are two users on the switches, `admin` and `operator`. The `operator` user has
@@ -113,8 +113,8 @@ broad administrative power on the switch.
 In order to avoid conflicts, do not use the following usernames: `operator`,`hhagent`,`netops`.
 
 ### 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 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).
 
 ### Control Node
 The control node is the host that manages all the switches, runs k3s, and serves images. 
@@ -171,7 +171,6 @@ spec:
         - loadavg
         - meminfo
         collectSyslogEnabled: true # collect /var/log/syslog on switches and forward to the lokiTargets
-
 ```
 
 For additional options, see the `AlloyConfig` [struct in Fabric repo](https://github.com/githedgehog/fabric/blob/master/api/meta/alloy.go).