Mapped dev-wiki conversion situation for situational awareness

[simantics/platform.git] / docs / Developer / Database / VirtualGraphs.md

diff --git a/docs/Developer/Database/VirtualGraphs.md b/docs/Developer/Database/VirtualGraphs.md
index 66c20ee85b4c95593d765713d3a4a8bd79ae6f94..98a2f44bb4a605b54d35fa6c43da7254af863390 100644 (file)
--- a/docs/Developer/Database/VirtualGraphs.md
+++ b/docs/Developer/Database/VirtualGraphs.md
@@ -13,18 +13,20 @@ Virtual graphs are manipulated via the following interfaces
 \r
 ## Specification\r
 \r
-A write request has a single graph into which it writes. This is determined by *WriteTraits* and usually as a parameter to *WriteRequest*. If null is provided, the client applies modifications into the persistent graph. The following rules apply:\r
+A write request has a single graph into which it writes. This is determined by *WriteTraits* and usually as a parameter to *WriteRequest*. If null is provided, the client applies modifications into the persistent graph.\r
+\r
+The following rules apply:\r
 \r
 * New resources are created into the given virtual graph\r
 * Claim statements are added into the given virtual graph\r
 * Value changes are applied into the given virtual graph\r
 * When the virtual graph provided to the WriteRequest is:\r
-** **null**:\r
-*** For denied statements the location of the statement is determined and the statement is removed from that virtual graph. If the denied statement is not a part of any virtual graph, it is removed from the persistent graph.\r
-** **non-null**:\r
-*** Statements are only removed from the virtual graph specified for the write request\r
+  * **null**:\r
+    * For denied statements the location of the statement is determined and the statement is removed from that virtual graph. If the denied statement is not a part of any virtual graph, it is removed from the persistent graph.\r
+  * **non-null**:\r
+    * Statements are only removed from the virtual graph specified for the write request\r
 \r
-The user can perform modifications into multiple virtual graphs within a single transaction. This is accomplished by issuing a new synchronous modification (WriteGraph.sync) into a new virtual graph.\r
+The user can perform modifications into multiple virtual graphs within a single transaction. This is accomplished by issuing a new synchronous modification `WriteGraph.sync[Request]` into a new virtual graph.\r
 \r
 ## Examples\r
 \r
@@ -114,8 +116,8 @@ public class VirtualGraphExample {
 ## Debugging\r
 \r
 The standard Simantics Graph Debugger view shows for every statement which virtual graph it belongs to. This information is visible on the *Graph* column of the statement table. The Graph column will show:\r
-;DB: when the statement is in the persistent graph\r
-;'name' (W): when the statement is in a named workspace-persistent virtual graph\r
-;'name' (M): when the statement is in a named memory-persistent (transient) virtual graph\r
+* **DB**: when the statement is in the persistent graph\r
+* **name (W)**: when the statement is in a named workspace-persistent virtual graph\r
+* **name (M)**: when the statement is in a named memory-persistent (transient) virtual graph\r
 \r
-[[Image:GraphDebuggerVG.png|frame|center|Graph debugger example with statements in virtual graphs.]]\r
+![Graph debugger example with statements in virtual graphs](Images/GraphDebuggerVG.png)
\ No newline at end of file