ecal.md

@@ -42,13 +42,6 @@ The ECAL interpreter in EliasDB receives the following events:
 | /db/sock/|`db.web.sock`| bodyJSON, bodyString, commID, header, method, path, pathList, query | Any web request to /db/sock/... These endpoints are used to initiate websocket connections. |
 | - |`db.web.sock.data`| commID, data, header, method, path, pathList, query | An existing websocket connection received some JSON object data. If the close attribute of the object is set to true then the websocket connection is closed. |
 
-EliasDB can receive the following events from the ECAL interpreter:
-
-| ECAL event kind | Event state contents | Description |
-| --- | --- | --- |
-| db.web.sock.msg | commID, payload, close | The payload is send to a client with an open websocket identified by the commID. |
-
-
 | EliasDB Graph Event | ECAL event kind | Event state contents | Description |
 | --- | --- | --- | --- |
 | graph.EventNodeCreated | `db.node.created` | part, trans, node | A node was created. |
@@ -64,6 +57,12 @@ EliasDB can receive the following events from the ECAL interpreter:
 | graph.EventEdgeDelete | `db.edge.delete` | part, trans, key, kind | An edge is about to be deleted. |
 
 Note: EliasDB will wait for the event cascade to be finished before performing the actual operation (e.g. inserting a node). If the event handling requires a time consuming operation then a new parallel event cascade can be started using `addEvent` with a scope:
+
+EliasDB can receive the following events from the ECAL interpreter:
+
+| ECAL event kind | Event state contents | Description |
+| --- | --- | --- |
+| db.web.sock.msg | commID, payload, close | The payload is send to a client with an open websocket identified by the commID. |
 ```
 addEvent("request", "foo.bar.xxx", {
    "payload" : 123