wip

cap-js-community · Jul 3, 2023 · 23dcc00 · 23dcc00
1 parent 4e0f947
commit 23dcc00
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 7 deletions.
diff --git a/docs/implement-event/index.md b/docs/implement-event/index.md
@@ -5,16 +5,13 @@ nav_order: 4
 ---
 
 <!-- prettier-ignore-start -->
-
 # Implement Event
-
 {: .no_toc}
 <!-- prettier-ignore-end -->
 
 <!-- prettier-ignore -->
-
 - TOC
-  {: toc}
+{: toc}
 
 ## Overview
 

diff --git a/docs/status-handling/index.md b/docs/status-handling/index.md
@@ -14,7 +14,7 @@ nav_order: 6
 <!-- prettier-ignore -->
 
 - TOC
-  {: toc}
+{: toc}
 
 ## Overview
 One of the main pillars of this library is safe transaction handling of events in combination with business processes.

diff --git a/docs/transaction-handling/index.md b/docs/transaction-handling/index.md
@@ -14,14 +14,15 @@ nav_order: 5
 <!-- prettier-ignore -->
 
 - TOC
-  {: toc}
+{: toc}
 
 ## Overview
 
 One of the fundamental pillars of this library is the secure handling of transactions in conjunction with business
 processes. All transactions related to event processing are fully managed and should not be committed or rolled back by
 the event implementation. The circumstances under which transactions are committed or rolled back are described in the
-following section.
+following section. Transactions are always CDS transactions associated with a CDS context. For more general information
+about CAP transaction handling, please refer to the [documentation](https://cap.cloud.sap/docs/node.js/cds-tx).
 
 ## Transaction Handling