ZIP 311: Minor edits from PR comments

zip-0311.html

@@ -22,7 +22,7 @@ Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/387">https://g
                 <li>A sender may need to prove that their payment was sent to a recipient, and available to be received (following the Zcash protocol in-band).</li>
                 <li>A third party may need to verify that a payment between a given sender and recipient was executed successfully.</li>
             </ul>
-            <p>When a transaction involves only transparent addresses, proof-of-payment is simple: The sender provides the transaction ID, and the recipent examines the blockchain to confirm that the transaction was mined. A third party can also perform this verification if they know the transparent addresses of the involved parties.</p>
+            <p>When a transaction involves only transparent addresses, proof-of-payment is simple: The sender provides the transaction ID, and the recipient examines the blockchain to confirm that the transaction was mined. A third party can also perform this verification if they know the transparent addresses of the involved parties.</p>
             <p>However, if the transaction involves shielded addresses, the blockchain by itself does not contain enough information to allow a record of the payment to be reconstructed and verified:</p>
             <table>
                 <thead>
@@ -79,7 +79,7 @@ Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/387">https://g
         </section>
         <section id="use-cases"><h2><span class="section-heading">Use cases</span><span class="section-anchor"> <a rel="bookmark" href="#use-cases"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
             <section id="managing-contributions-for-an-event"><h3><span class="section-heading">Managing contributions for an event</span><span class="section-anchor"> <a rel="bookmark" href="#managing-contributions-for-an-event"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
-                <p>Alice runs an event on behalf of Bob and Carol, who both agree to split the cost equally. Alice receives a single payment for half the amount, and wants proof of who it came from (so she knows which person to follow up with for the remaining amount). Carol can provide a payment disclosure that reveals:</p>
+                <p>Alice runs an event on behalf of Bob and Carol, who both agree to split the cost equally. Alice receives a single payment for half the amount, and wants proof of who it came from (so she knows which person to follow up with for the remaining amount). Carol can provide a payment disclosure that reveals to Alice:</p>
                 <ul>
                     <li>The correct amount was sent to the Alice's recipient address in the given transaction.</li>
                     <li>Carol was the sender of that transaction (more precisely, Carol controls the spend authority used in that transaction).</li>

zip-0311.rst

@@ -27,7 +27,7 @@ There are various situations where a proof-of-payment may be desired. For exampl
   executed successfully.
 
 When a transaction involves only transparent addresses, proof-of-payment is simple: The
-sender provides the transaction ID, and the recipent examines the blockchain to confirm
+sender provides the transaction ID, and the recipient examines the blockchain to confirm
 that the transaction was mined. A third party can also perform this verification if they
 know the transparent addresses of the involved parties.
 
@@ -61,7 +61,7 @@ Managing contributions for an event
 Alice runs an event on behalf of Bob and Carol, who both agree to split the cost equally.
 Alice receives a single payment for half the amount, and wants proof of who it came from
 (so she knows which person to follow up with for the remaining amount). Carol can provide
-a payment disclosure that reveals:
+a payment disclosure that reveals to Alice:
 
 - The correct amount was sent to the Alice's recipient address in the given transaction.
 - Carol was the sender of that transaction (more precisely, Carol controls the spend