diff --git a/docs/VOLUME.md b/docs/VOLUME.md
index 7056350..7b312c2 100644
--- a/docs/VOLUME.md
+++ b/docs/VOLUME.md
@@ -212,7 +212,7 @@ If the same test is run with a leveldb backend but with the pre-sweeper fold mec
 
 ## Riak Cluster Test - Phase 3 - Journal Compaction
 
-When first developing the issue of compacting the value store was left to one side from a performance perspective, under the assumption that compaction would occur in some out-of-hours window.  Bitcask is configurable in this way, but also manages to do continuous compaction without major performance issues.
+When first developing leveled, the issue of compacting the value store was left to one side from a performance perspective, under the assumption that compaction would occur in some out-of-hours window.  Bitcask is configurable in this way, but also manages to do continuous compaction without major performance issues.
 
 For this phase, a new compaction feature was added to allow for "continuous" compaction of the value store (Journal).  This means that each vnode will schedule approximately N compaction attempts through the day, rather than wait for a compaction window to occur.
 
@@ -225,7 +225,7 @@ This was tested with:
 - 12 hour duration,
 - 200M keys with a pareto distribution (and hence significant value rotation in the most commonly accessed keys).
 
-With 10 compaction events per day, after the 12 hour test 155GB per node had been compacted out of the value store during the test.  In the 12 hours following the test, a similar amount was compacted - to the point there was rough equivalence in node volumes between the closing state of the leveled test and the closing state of the leveldb test.
+With 10 compaction events per day, after the 12 hour test 155GB per node had been compacted out of the value store during the test.  In the 12 hours following the test, a further 125GB was compacted - to the point there was rough equivalence in node volumes between the closing state of the leveled test and the closing state of the leveldb test.
 
 As before, the Riak + leveled test had substantially lower tail latency, and achieved higher (and more consistent) throughput.  There was an increased volatility in throughput when compared to non-compacting tests, but the volatility is still negligible when compared with leveldb tests.
 
@@ -250,6 +250,7 @@ Hour 10 | 9,965.14 | 143.52%
 Hour 11 | 10,112.84 | 149.13%
 Hour 12 | 10,266.02 | 144.63%
 
+This is the first time a test of this duration has been run, and there does appear to be a trend of Riak/leveled throughput tending towards a stable volume, rather than an ongoing decline in throughput as the test progresses.
 
 ## Riak Cluster Test - Phase 4 - 2i