News62: final (hopefully) edits

Author: harding

_posts/en/newsletters/2019-09-04-newsletter.md

@@ -68,7 +68,7 @@ notes a few changes in popular Bitcoin infrastructure projects.
   This completes the proposer step in SNICKER.
 
   If Bob participates in the scheme, his wallet can begin the
-  receiver by periodically checking the server to see if
+  receiver step by periodically checking the server to see if
   anyone like Alice has sent him a proposed PSBT.  If so, Bob can
   evaluate the PSBT to ensure it's correct, add his signature for his
   UTXO to finalize it, and broadcast the transaction to complete the
@@ -82,13 +82,13 @@ notes a few changes in popular Bitcoin infrastructure projects.
   people via a variety of servers, selecting whichever proposal he
   prefers (or none at all).  Either party can also spend their UTXO
   normally at any time, automatically invalidating any pending proposals
-  without any harm done.  The PSBTs can be exchanged using any medium that doesn't require users identify themselves,
+  without any harm done.  The PSBTs can be exchanged using any medium that doesn't require users to identify themselves,
   such as a via a simple FTP server over Tor, making it easy for anyone to host a
   SNICKER exchange server.
 
   The main downside of the proposal is that it requires the proposer
   (Alice) know the public key of the receiver (Bob).  Almost all
-  transactions today pay an address that doesn't include a public key,
+  transaction outputs today pay addresses that don't directly include public keys,
   although that may change if the proposed [taproot][bip-taproot]
   soft fork is activated and becomes widely adopted.  In the meantime,
   the SNICKER proposal suggests scanning for reused addresses where public keys