X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/0577c00521c5c2a8dd0106ee6bdc0e2fbcd36f79..709252ab99debf5fdde52aa0972466a8e4af8b1c:/ralf/_drafts/types-as-contracts.md

diff --git a/ralf/_drafts/types-as-contracts.md b/ralf/_drafts/types-as-contracts.md
index 5b1974f..89d99b3 100644
--- 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.
 
-[^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