From 1f1df56c343a48cc6a7874ac6a3409e40fea7e71 Mon Sep 17 00:00:00 2001
From: Nikolay Stanchev <ns17@it-innovation.soton.ac.uk>
Date: Thu, 5 Apr 2018 15:33:10 +0100
Subject: [PATCH] corrected a mistake in documentation

---
 docs/monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/monitoring.md b/docs/monitoring.md
index 788143a..a283a7b 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -553,7 +553,7 @@ Then the VM is reported to be in current state __placing__ for the whole sample
 field value are filled in the measurement rows, since the VM has not exited its state, yet.
 
 The last sample period reports the VM exiting state __placing__, then changing state to __placed__. Hence, the __current_state__ tag is set to __placed__.  
-From the whole sample period (1s), the VM has been 0.9s in state 'placed'. Hence, the __current_state_time__ tag is set to 0.9. For the other 0.1s of the sample period,
+From the whole sample period (1s), the VM has been 0.9s in state 'placed'. Hence, the __current_state_time__ field is set to 0.9. For the other 0.1s of the sample period,
 the VM has been reported to be in state __placing__. Since it has exited state __placing__, the total time spent in this state (9.3s + 0.1s = 9.4s) is reported.
 This includes the state time from previous reports. The mean state time value for __placing__ is the same as the sum value because the VM has only been once in this state.
 
-- 
GitLab