X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/410f011382852913bd39338634af3953584979ea..e9e7f558e195c0992d8b37bcbaa112b01694cc67:/personal/_drafts/types-as-contracts.md

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