auto

README.md

 # Project 5: Transactional Support From a Log
+<font =-1>v1.0</font>
 
 
 # Overall Project Description
@@ -76,10 +77,9 @@ Our transaction substrate is modeled on that in Tango.  Update transactions are
 *optimistic*, and commit only if isolation is preserved for the entire transaction
 execution. Said another way:
 
-&nbsp;&nbsp;&nbsp;**Definition 1:** *&nbsp;&nbsp;&nbsp;T<sub>i</sub> commits iff for each read r in T<sub>i</sub>: 
-<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- r is not a **dirty write** &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;* // note that the paper does not mention this 
-*<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- there are no writes (without
-associated aborts) to r's key in the log between r and T<sub>i</sub>'s commit.*
+&nbsp;&nbsp;&nbsp;**Definition 1:** *&nbsp;&nbsp;&nbsp;T<sub>i</sub> commits iff for each read r in T<sub>i</sub>,
+the value read by* r *is not stale by the time T<sub>i</sub>'s commit record is encountered.*
+
 
 Transactions that are observed to commit have their writes reflected in the clients local
 key-value store.
@@ -99,7 +99,7 @@ ignored by other replicas.
 
 ## Part 2: Snapshot Isolation
 
-Your decision as to how to implement this, but it should not involve any changes to the
+Your decision as to how to implement this, but it need not involve any changes to the
 log abstraction in `replica.go`