en/index: minor fixes

- add missing space in a command;
- prevent wrapping between <code> & full stop (inline-block issue);
- press enter --> press "Enter".

diff --git a/en/index.html b/en/index.html
index 8c87ac513ff0151be526c41eed2ff4651436f358..66be4e3237f748c23bf3f47724d5880ac8fb1a97 100644 (file)
--- a/en/index.html
+++ b/en/index.html
@@ -213,7 +213,7 @@ page</a>.</dd>
 <dd>Your macOS comes with a program called "Terminal" pre-installed, which we'll use to set up your encryption with GnuPG, using the command line. However, the default macOS package manager makes it difficult to install GnuPG and other pieces of free software (like Emacs, GIMP, or Inkscape).<br/>
 To make things easier, we recommend setting up the third-party package manager "Homebrew" to install GnuPG. Copy the link on the home page of <a href="https://brew.sh/">Homebrew</a> and paste it in Terminal. Click "Enter" and wait for it to finalize.<br/>
 When it is done, install the program by entering the following code in Terminal:<br/>
-<code>brew install gnupg gnupg2</code>. After installation is done, you can follow the steps of the rest of this guide.</dd>
+<code>brew install gnupg gnupg2</code>&#65279;. After installation is done, you can follow the steps of the rest of this guide.</dd>
 </dl>
 
 </div><!-- /.troubleshooting -->
@@ -333,7 +333,7 @@ song lyrics, quotes from books, and so on.</p>
 <dl>
 <dt>GnuPG is not installed</dt>
 <dd>
-GPG is not installed. You can check if this is the case with the command <code>gpg --version</code>.
+GPG is not installed. You can check if this is the case with the command <code>gpg --version</code>&#65279;.
 If GnuPG is not installed, it would bring up the following result on most GNU/Linux operating systems, or something like it:
 <samp>Command 'gpg' not found, but can be installed with:
   sudo apt install gnupg</samp>. Follow that command and install the program.</dd>
@@ -343,7 +343,7 @@ If GnuPG is not installed, it would bring up the following result on most GNU/Li
 
 <dt>How can I see my key?</dt>
 <dd>
-Use the following command to see all keys: <code>gpg--list-keys</code>. Yours should be listed in there, and later, so will Edward's (<a href="#section3">section 3</a>). If you want to see only your key, you can use <code>gpg --list-key [your@email]</code>. 
+Use the following command to see all keys: <code>gpg --list-keys</code>&#65279;. Yours should be listed in there, and later, so will Edward's (<a href="#section3">Section 3</a>). If you want to see only your key, you can use <code>gpg --list-key [your@email]</code>&#65279;. 
 You can also use <code>gpg --list-secret-key</code> to see your own private key.</dd>
 
 <dt>More resources</dt>
@@ -417,7 +417,7 @@ $ gpg --export -a [keyID] > my_public_key.asc
 <p># Copy your keyID: <code>gpg --list-key [your@email]</code> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
 <p># Generate a revocation certificate: <code>gpg --gen-revoke --output revoke.asc [keyID]</code></p>
 <p># It will prompt you to give a reason for revocation, we recommend to use <samp>1&nbsp;=&nbsp;key has been compromised</samp>.</p>
-<p># You don't have to fill in a reason, but you can, then press enter for an empty line, and confirm your selection.</p>
+<p># You don't have to fill in a reason, but you can, then press "Enter" for an empty line, and confirm your selection.</p>
 
 
 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
@@ -476,7 +476,7 @@ $ gpg --import my_public_key.asc
 $ gpg --edit-key [your@email]
 </code></p>
 
-<p>Because this is your key, you should choose <code>ultimate</code>. You shouldn't trust anyone else's key ultimately.</p>
+<p>Because this is your key, you should choose <code>ultimate</code>&#65279;. You shouldn't trust anyone else's key ultimately.</p>
 
 <p class="notes"> Refer to <a href="#step-2b">troubleshoot in step 2.B</a> for more information on permissions. When transferring keys, your permissions may get mixed, and errors may be prompted. These are easily avoided when your folders and files have the right permissions</p>
 </dd>