From b36f750ceebae5786a73435079fef01a8be104e3 Mon Sep 17 00:00:00 2001
From: Zoe <zoe@fsf.org>
Date: Fri, 9 Aug 2019 13:45:33 -0400
Subject: [PATCH] updating kitchen w 3.c and 3.e changes

---
 en/kitchen/index.t.html | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

diff --git a/en/kitchen/index.t.html b/en/kitchen/index.t.html
index 2157179a..84da614e 100644
--- a/en/kitchen/index.t.html
+++ b/en/kitchen/index.t.html
@@ -721,20 +721,12 @@ HTML. Instead, you can render the message body as plain text.</p>
 <h3><em>Step 3.c</em> Receive a response</h3>
 
 <p>When Edward receives your email, he will use his private key to decrypt
-it, then use your public key (which you sent him in <a href="#step-3a">Step
-3.A</a>) to encrypt his reply to you.</p>
+it, then reply to you. </p>
 
 <p class="notes">It may take two or three minutes for Edward to
 respond. In the meantime, you might want to skip ahead and check out the <a
 href="#section5">Use it Well</a> section of this guide.</p>
 
-<p>When you receive Edward's email and open it, Enigmail will automatically
-detect that it is encrypted with your public key, and then it will use your
-private key to decrypt it.</p>
-
-<p>Notice the bar that Enigmail shows you above the message, with information
-about the status of Edward's key.</p>
-
 </div><!-- End .main -->
 </div><!-- End #step-3c .step -->
 
@@ -773,9 +765,9 @@ be encrypted, signed, both, or neither.</p>
 
 <h3><em>Step 3.e</em> Receive a response</h3>
 
-<p>When Edward receives your email, he will use your public key (which you
-sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature
-is authentic and the message you sent has not been tampered with.</p>
+<p>When Edward receives your email, he will use your public key (which
+you sent him in <a href="#step-3a">Step 3.A</a>) to verify the message
+you sent has not been tampered with and to encrypt his reply to you.</p>
 
 <p class="notes">It may take two or three minutes for Edward to
 respond. In the meantime, you might want to skip ahead and check out the <a
@@ -786,6 +778,13 @@ whenever possible. If everything goes according to plan, it should say
 "Your signature was verified." If your test signed email was also encrypted,
 he will mention that first.</p>
 
+<p>When you receive Edward's email and open it, Enigmail will
+automatically detect that it is encrypted with your public key, and
+then it will use your private key to decrypt it.</p>
+
+<p>Notice the bar that Enigmail shows you above the message, with
+information about the status of Edward's key.</p>
+
 </div><!-- End .main -->
 </div><!-- End #step-3e .step -->
 </div></section>
-- 
2.25.1