Documentation.md

@@ -68,12 +68,12 @@ After you have successfully enrolled in Cisco Duo and prepared your SSH key pair
 ### 2.2 SSH access, keys and things
 Quick summary, if you just need a reminder:  
 ```
-|ssh-keygen -t ed25519 -C "<YOUR NAME>" |# generate private+public key pair|
-|cat ~/.ssh/id_ed25519.pub              |# copy-paste and send to hpc-mgr@uni-koeln.de|
+| ssh-keygen -t ed25519 -C "<YOUR NAME>" | # generate private+public key pair |
+| cat ~/.ssh/id_ed25519.pub              | # copy-paste and send to hpc-mgr@uni-koeln.de |
 # Procedure for circumventing passphrase at ssh-login (optional):
-|eval "$(ssh-agent -s)"        |# set ssh-agent's environment variables|
-|ssh-add ~/.ssh/id_ed25519     |# provide private-key identity to agent|
-|ssh-add -l                    |# list managed identities (should show at least one entry)|
+| eval "$(ssh-agent -s)"        | # set ssh-agent's environment variables |
+| ssh-add ~/.ssh/id_ed25519     | # provide private-key identity to agent |
+| ssh-add -l                    | # list managed identities (should show at least one entry) |
 # Done, or keep reading below for more details
 ```
 There is always a private (as in **private - don't share, don't give away**) and a public key in an SSH key pair. As with physical keys, one does not want to share private keys or leave copies thereof in other locations/computers. Instead, create new SSH key pairs on each frequently-used host. Let's outline a **3-step procedure** to get you "keyed-in".