diff --git a/docs/monitoring.md b/docs/monitoring.md
index 4455e32c26fb7534e1f230fbda45f40e9eed10ac..704588691b09cabcd94898fd1e9521cf70a3505e 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -119,7 +119,27 @@ If tags are used then measurements of GPS coordinates will need to be translated
 
 Matching on tags is limited to matching and potentially spatial hierarchies (e.g. country.city.street). Using a coordiante system allows for mathatical functions to be developed (e.g. proximity functions)
 
-## **Decision Context**
+## **Decisions**
+
+### Service Management Decisions
+
+Capacity Decision Context
+
+* Provision compute node
+* Provision network provider
+
+Media Service Decision Context
+
+* Place SF
+* Unplace SF
+* Boot SF
+* Connect SF
+* Route to SF against criteria
+* Change resource allocation to SF 
+
+Health Checks?
+
+### Decision Context
 
 Monitoring data is collected to support service design, management and control decisions. The link between decisions and data is through queries and rules applied to contextual information stored with measurement values.  
 
@@ -173,24 +193,6 @@ Give a worked example across service and network measurements based on the mpeg-
 
 Discuss specific tags
 
-### Decisions
-
-Capacity Decision Context
-
-* Provision compute node
-* Provision network provider
-
-Media Service Decision Context
-
-* Place SF
-* Unplace SF
-* Boot SF
-* Connect SF
-* Route to SF against criteria
-* Change resource allocation to SF 
-
-Health Checks?
-
 ## **Architecture**
 
 ### General ###