News71: edits for adamjonas and jonatack feedback (thanks!)

Author: harding

_posts/en/newsletters/2019-11-06-newsletter.md

@@ -62,7 +62,7 @@ projects.
 
     - Whether each LN payment should pay different public keys (using
       pubkey tweaking).  Removing key tweaking was proposed to reduce
-      the amount state tracking necessary, but a concern was raised that
+      the amount of state tracking necessary, but a concern was raised that
       this would make the channel state too deterministic.  This could
       allow a watchtower that received a series of encrypted breach
       remedy transactions from one side of a channel to be able to
@@ -93,7 +93,7 @@ projects.
     not they want to participate in address relay---a per-node method
     and a per-connection method.  The per-node method could easily build
     on top of work already being done for addrv2 messages (see [Newsletter
-    #37][news37 addrv2]), but it would be less flexible than the the
+    #37][news37 addrv2]), but it would be less flexible than the
     per-connection method.  In particular, the per-connection method
     could allow a node to dedicate some connections to transaction relay
     and other connections to address relay, producing possible privacy
@@ -122,7 +122,7 @@ projects.
 
 - [LND #3558][] synthesizes a unified policy for any case where two
   particular nodes have multiple channels open between them and then
-  uses this synthetic policy when considering routing through any of
+  uses this unified policy when considering routing through any of
   those channels.  [BOLT4][bolt4 non-strict rec] recommends that multiple channels
   between the same nodes should all use the same policy, but this
   doesn't always happen, so this change tries to determine "the greatest
@@ -132,11 +132,11 @@ projects.
 
 - [LND #3556][] adds a new `queryprob` RPC that returns the expected
   probability that a payment would succeed given a particular
-  destination node and amount.  This replaces functionality previously
+  source node, destination node, and payment amount.  This replaces functionality previously
   removed from the `querymc` RPC.
 
 - [BOLTs #660][] updates [BOLT1][] to reserve Type-Length-Value (TLV)
-  type identifiers less than 2<sup>16</sup> for types defined in in the
+  type identifiers less than 2<sup>16</sup> for types defined in the
   LN specification (the BOLT documents).  The remaining values may be
   used freely as custom records by any LN implementation.  The updated
   specification also now provides guidance on how to select numbers for