Documentation.md

@@ -71,17 +71,16 @@ Quick summary, if you just need a reminder:
 | Command | Description |
 | ----------- | ----------- |
 | `ssh-keygen -t ed25519 -C "<YOUR NAME>"` | generate private + public key pair |
-| `cat ~/.ssh/id_ed25519.pub`              | print content of public key file; copy-paste and send to hpc-mgr@uni-koeln.de |
+| `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 environment variables of the SSH agent |
-| `ssh-add ~/.ssh/id_ed25519`     | provide private-key identity to agent |
+| `ssh-add ~/.ssh/id_ed25519`     | provide private key identity to agent |
 | `ssh-add -l`                    | list managed identities (should show at least one entry) |
 
 Please keep reading below if you require 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 their copies in other locations/computers. Instead, we recommend to create new SSH key pairs on each frequently-used host. Let's outline a **3-step procedure** to get you "keyed-in".
+An SSH key pair always consists of a private key (as in **private - don't share, don't give away**) and a public key. As with physical keys, one does not want to share private keys or leave their copies in other locations/computers. Instead, we recommend to create new SSH key pairs on each frequently-used host. Let's outline a **3-step procedure** to get you "keyed-in".
 
 #### 2.2.1 Step 1: Generate authentication keys: `ssh-keygen`
 ```