**Martijn:** - Openly stated open questions ("How do A and B relate?") is preferred over closely stated ones ("Does A imply B?") - Avoid unnecessary "ing"s. ("B, playing G0" vs. "B plays G0"). - "There are a bunch of floating 'this'es in the write-up. In my experience, this often indicates lazy writing: fine on slack, not great in papers." - "You regularly seem to write unachiveable instead of unachievable." - Consistency: "We don't hyphenate public key encryption (others of course do, but then you'd also have to go selective-opening attacks, chosen-plaintext attacks, etc.)" - "Phil Rogaway has a philosophy about when to hyphenate and when not. For instance, he would say a hash function is collision resistant, in other words, it is a collision-resistant hash function (or even collision-resistant hash-function). In any case, the purpose of the hyphenation should be to assist the reader in parsing the sentence by grouping together what belongs together." - "talking about hyphenation, the "standard model-unachievable" looks very weird to me, perhaps 'standard-model unachievable' though in most cases I rewrote it to unachievable in the standard model." - My reply: "that’s likely a mental holdover from Norwegian writing—since there wouldn’t be a space in standard model so you would say “standardmodell-uoppnåelig” or similar—that you’re probably right is a worse fit for English; I’ll keep it in mind going forward"