typo

[web.git] / ralf / _drafts / types-as-contracts.md

diff --git a/ralf/_drafts/types-as-contracts.md b/ralf/_drafts/types-as-contracts.md
index 5b1974f9022d6830fdb22838f3e9bd7a919f1244..89d99b3c9f9917f8b9629a3e99a39bf3e18ea1b6 100644 (file)
--- a/ralf/_drafts/types-as-contracts.md
+++ b/ralf/_drafts/types-as-contracts.md
@@ -60,7 +60,7 @@ The validation of reference types (in particular, their exclusive / read-only na
 The extra state in my proposal consists of something akin to a reader-writer lock for every memory location.
 I am first going to describe these locks and how they affect program behavior, before explaining contract validation.
 
 The extra state in my proposal consists of something akin to a reader-writer lock for every memory location.
 I am first going to describe these locks and how they affect program behavior, before explaining contract validation.
 

-[^1]: If at this point you are under the impression that all these previous posts have been just building up and are now coming together in this proposal, you are not entirely wrong.
+[^1]: If at this point you are under the impression that all these previous posts have been collectively building up towards this proposal, you are not entirely wrong.

 
 ### Memory locks
 
 
 ### Memory locks