Issue #67 - updated documentation for aggregation

docs/aggregation.md

@@ -95,6 +95,7 @@ the target endpoint ID of the **network_delays** measurement, the rows are combi
 Example:
 
 * Result from first query:
+
 ```
 name: network_delays
 tags: path=endpoint1.ms-A.ict-flame.eu---endpoint2.ms-A.ict-flame.eu
@@ -108,8 +109,9 @@ time                Dnet
 ----                ----
 1524833145975682287 10.3
 ```
-
+  
 * Result from second query
+
 ```
 name: service_delays
 tags: FQDN=ms-A.ict-flame.eu, endpoint=endpoint2.ms-A.ict-flame.eu, sf_instance=test-sf-clmc-agent-build_INSTANCE
@@ -118,6 +120,7 @@ time                Dresponse
 1524833145975682287 11
 ```
 
+
 The script will parse the path identifier **endpoint1.ms-A.ict-flame.eu---endpoint2.ms-A.ict-flame.eu** and find the target endpoint being
 **endpoint2.ms-A.ict-flame.eu**. Then the script checks if there is service delay measurement row matching this endpoint. Since there is one,
 those values will be merged, so the result will be a row like this:
@@ -125,7 +128,7 @@ those values will be merged, so the result will be a row like this:
 | pathID_F (tag) | pathID_R (tag) | FQDN (tag) | sf_instance (tag) | D_path_F | D_path_R | D_service | time |
 | --- | --- | --- | --- | --- | --- | --- | --- | 
 | endpoint1.ms-A.ict-flame.eu---endpoint2.ms-A.ict-flame.eu | endpoint2.ms-A.ict-flame.eu---endpoint1.ms-A.ict-flame.eu | ms-A.ict-flame.eu | test-sf-clmc-agent-build_INSTANCE | 9.2 | 10.3 | 11 | 1524833145975682287 | 
-
+  
 Here, another assumption is made that we can reverse the path identifier of a network delay row and that the reverse path delay would also 
 be reported in the **network_delays** measurement.