finish day 3

_includes/utils/scripts.html

@@ -2,6 +2,7 @@
 <script src="{{ "/assets/js/jquery-3.5.1.min.js" | relative_url }}"></script>
 <script src="{{ "/assets/js/bootstrap.bundle.min.js" | relative_url }}"></script>
 <script src="{{ "/assets/js/bootstrap-toc.min.js" | relative_url }}"></script>
+
 <!--Anchors-->
 <script src="{{ "/assets/js/anchor.min.js" | relative_url }}"></script>
 <script>
@@ -10,4 +11,4 @@
   icon: '#',
   };
   anchors.add('h1, h2, h3, h4, h5').remove('.no-anchor');
-</script>
+</script>

ntnu/21v/ttk4145/summary/summary.md

@@ -138,7 +138,7 @@ Find the failure modes: What could go wrong?
   * Lost
   * Delayed
   * Corrupted
-  * DUplicated
+  * Duplicated
   * Wrong recipient
 
 **Step 2: Detection, Merging of errormodes and error injection**
@@ -187,3 +187,14 @@ There are three solutions:
 
 A transaction is a design framework for Damage Confinement and Error Recovery.
 
+* An *atomic action*, just without the backward recovery error mode as standard mode
+* invincible and instantaneous "calculation" seen from the outside
+* A transformation from one consistent state to another'
+* A modular computation
+
+### Four features: ACID
+
+* **A**tomicity: Either all side effects happens or none
+* **C**oncistency: Leaves the system in a consistent state when finished
+* **I**solation: Errors does not spread
+* **D**urability: Results are not lost