Documentation.md

@@ -79,10 +79,10 @@ ssh-add -l                    # list managed identities (should show at least on
 
 | Syntax | Description |
 | ----------- | ----------- |
-| `ssh-keygen -t ed25519 -C "<YOUR NAME>"` | generate private+public key pair |
+| `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 |
+| `eval "$(ssh-agent -s)"`        | set environment variables of the SSH agent |
 | `ssh-add ~/.ssh/id_ed25519`     | provide private-key identity to agent |
 | `ssh-add -l`                    | list managed identities (should show at least one entry) |
 
@@ -90,7 +90,7 @@ 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".
+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, 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`
 ```