From bbeb02e1cc4bfe85573b1155dd5870e83a15a8a2 Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Sun, 19 Dec 2021 15:20:27 +0000
Subject: [PATCH] editorial change

---
 handbook/computing/keyexchange.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/handbook/computing/keyexchange.html b/handbook/computing/keyexchange.html
index 56d491e06..3c222f5df 100644
--- a/handbook/computing/keyexchange.html
+++ b/handbook/computing/keyexchange.html
@@ -72,7 +72,7 @@ The key's randomart image is:
 <font color="darkred">$</font>
 </code>
 </pre>
-<p>This will enable ssh login instantly. Check that it has worked by logging in to the expo server like this:
+<p>Once the nerd has told you that the public key is loaded on the server, check that it has worked by logging in to the expo server like this:
 <code>
 <font color="darkred">$</font> <b>ssh expo@expo.survex.com</b>
 </code>
@@ -143,7 +143,7 @@ Be <b>extremely careful</b> to type ">>" and not ">" in the fourth line below ot
 <br /><font color=blue">expo@expo:~/.ssh$</font> tail -n 1  authorized_keys
 </code> 
 This adds your key on to the end of the authorized keys list and prints the last line - which should be your key that you just added.
-<li>Now your public key is installed for your second machine. You check that it works by logging into the expo server using ssh from your second machine: <var>ssh expo@expo.survex.com </var>.
+<li>Now your public key is installed for your second machine. This will enable ssh login instantly. You check that it works by logging into the expo server using ssh from your second machine: <var>ssh expo@expo.survex.com </var>. 
 </p>
 <p>Note that by using sFTP like this we avoid having to use a text editor over ssh. If you know what you are doing you can do this of course, but the above process is less likely to cause problems for a Windows user setting up their phone as a second device where they are not experienced with vi or nano.