*** empty log message ***

diff --git a/Robust/Transactions/Notes/sysgurantees.dvi b/Robust/Transactions/Notes/sysgurantees.dvi
index 5132f879a1e700c7ea9a2b90ccbde3c2329a73aa..fb98f11c0c1d999e31f4d6c5b124c6866451610f 100644 (file)
Binary files a/Robust/Transactions/Notes/sysgurantees.dvi and b/Robust/Transactions/Notes/sysgurantees.dvi differ

diff --git a/Robust/Transactions/Notes/sysgurantees.tex b/Robust/Transactions/Notes/sysgurantees.tex
index 63a1c75f8a0ab3b0cdf17e37791c4ec3c45e1e94..b72797525412e36a0bd3245968c2bbed6f59e02e 100644 (file)
--- a/Robust/Transactions/Notes/sysgurantees.tex
+++ b/Robust/Transactions/Notes/sysgurantees.tex
@@ -196,7 +196,7 @@ Def: We define a function $g(offsetstat_1, offsettat_2, ..., offsetstat_{n-1}, o
 \section{Implementation Overview}
 
 %proof: A write operation writes to the most recently commited offset (unless imposed otherwise by a seek or a prior read or a following read as shown above) of the file descriptor.  According to Def 2, it does not "use" any data. Since the write does not happen till commit instant, the offset chosen during the execution of transaction can be speculative, and the actual offset to be written to, is determined at the sommit instant, when the most recently commited offset is known. 
-Now we will describe the components of our system and demosntrate how the algorithm 
+Now we will describe the components of our system and demosntrate how the algorithm conforms to the function just described, and how all the rules principles are gurantedd.