diff --git a/docs/monitoring.md b/docs/monitoring.md
index 3995daddc9752cdfc57879d7be747ca94c63c1a9..7f996042786020d64066c8010dd028096f23b190 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -78,15 +78,15 @@ Tag location
 | --- | --- | --- |
 | DATACENTRE_1 | 0 | 0 |
 
-A SF media transcoder is placed in a lamp-post. It has no means to obtain GPS coordinates but has a _loc_label_ provided to it as a VM environment variable. It provides zeros in the longitude and latitude. In subsequent data analysis we can search for this SF by location label.
+A SF media transcoder is placed in a lamp-post. It has no means to obtain GPS coordinates but has a _location_label_ provided to it as a VM environment variable. It provides zeros in the longitude and latitude. In subsequent data analysis we can search for this SF by location label.
 
 GPS coordination location
 
-| loc_label | loc_long | loc_lat |
+| location_label | location_long | location_lat |
 | --- | --- | --- |
 | LAMP_1 | 50.842715 | -0.778276 |
 
-A SF that is a proxy to a user attached to a NAP running in street lamp post LAMP_1. Here we have knowledge both of the logical location of the service and also the fine-grained, dynamic position of the service user. Lots of interesting possibilities with both of these bits of information!
+A SF that is a proxy to a user attached to a NAP running in street lamp post LAMP_1. Here we have knowledge both of the logical location of the service and also the fine-grained, dynamic position of the service user.
 
 Note that tags are always strings and cannot be floats, therefore log and lat will always be stored as a measurement field.