doc/devblog/day_322-326__concurrent_drop_safety.mdwn: Wording
authorRichard Hartmann <richih@debian.org>
Mon, 12 Oct 2015 20:50:16 +0000 (22:50 +0200)
committerRichard Hartmann <richih@debian.org>
Mon, 12 Oct 2015 20:50:16 +0000 (22:50 +0200)
doc/devblog/day_322-326__concurrent_drop_safety.mdwn

index 6b8da87f753b9559771768087c03a8f19c212bfc..5dbf420e4c92fe152fcba208301e3b5a9b39b044 100644 (file)
@@ -41,9 +41,9 @@ rare race condition occurs.
 
 So, I've been implementing that all of yesterday and today. Getting it
 right involves building up 4 different kinds of evidence, which can be
-used to make sure that the last copy of a file can't possibly be being
+used to make sure that the last copy of a file can't possibly end up being
 dropped, no matter what other concurrent drops could be happening.
 I ended up with a very clean and robust implementation of this, and
-a 2 thousand line diff.
+a 2,000 line diff.
 
 Whew!