docs: language fixes for meeting minutes

1 files changed, 10 insertions, 12 deletions

diff --git a/blog/2021/04/18/meeting.mdwn b/blog/2021/04/18/meeting.mdwn
index 58b138a..7f176be 100644
--- a/blog/2021/04/18/meeting.mdwn
+++ b/blog/2021/04/18/meeting.mdwn
@@ -60,7 +60,7 @@ Lars is thus proposing a change to how Obnam code review will work:
 Typical values for N will be:
 
 * 0 for typo fixes and similar low-impact changes, or fixes to
-  urgent high-impact issues
+  urgent high-impact issues (immediate self-merge)
 * 1 for other urgent changes
 * 3 for most changes – this will be the default
 * 5 for changes likely to be controversial or affecting security
@@ -74,7 +74,8 @@ a merge request as "approved", allowing someone else to merge. The
 "merge" one will allow telling GitLab to actually merge the change,
 closing the merge request.
 
-Merge requests by others will follow the same process.
+Merge requests by others will follow the same process. If nobody else
+reviews a change, Lars will do that.
 
 This workflow should at least open the door to code review without
 slowing down development too much.
@@ -98,7 +99,7 @@ unanimity.
 
 When the project starts having other regular contributors, some form
 of formal governance will be needed. But it's too early to decide on
-that. Lars tends to prefer democracy and voting.
+that. Lars tends to prefer ordered discussion, democracy, and voting.
 
 
 # Goals
@@ -131,10 +132,10 @@ Obnam defending against all the modeled threats.
 The main goal of this iteration is to add at least rudimentary
 encryption of chunks, before they're uploaded to the server, and
 decryption and validation after they're downloaded. This should use
-the encryption keys stored by `obnam init`. It's OK if this is done
-only if the client configuration says encryption is turned on, to
-allow an opt-in approach to encryption for now. Later on, encryption
-won't be optional.
+the encryption keys stored by `obnam init`. This is done only if the
+client configuration says encryption is turned on, to allow an opt-in
+approach to encryption for now. Later on, encryption won't be
+optional.
 
 At the same time, work needs to start on using more concurrency in the
 client, and that means that Lars needs to learn more about Rust,
@@ -145,14 +146,11 @@ back log of open issues.
 
 # Commitments for this iteration
 
-[[!milestone 8]] represents this iteration on GitLab.
+New [[!milestone 8]] represents this iteration on GitLab.
 
 This is a one-week iteration, which is short, so commitments need to
 not be overly ambitious. For Lars, that means a time budget of 8 hours
-of this iteration.
-
-For this iteration, Lars is committed to resolving the following
-issues:
+this iteration. Lars is committed to resolving the following issues:
 
 - [[!issue 28]] - large vectors should be iterators (1h)
 - [[!issue 102]] - need to have tilde expansion in config file (0.25h)