diff --git a/_includes/utils/scripts.html b/_includes/utils/scripts.html
index 8a49cb8..1ca6327 100644
--- a/_includes/utils/scripts.html
+++ b/_includes/utils/scripts.html
@@ -2,6 +2,7 @@
+
\ No newline at end of file
+
diff --git a/ntnu/21v/ttk4145/summary/summary.md b/ntnu/21v/ttk4145/summary/summary.md
index 3ca64fc..efd1679 100644
--- a/ntnu/21v/ttk4145/summary/summary.md
+++ b/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