Update shell-and-data-access.md

docs.it4i/general/shell-and-data-access.md

@@ -178,7 +178,7 @@ A very convenient way to transfer files in and out of cluster is via the fuse fi
 $ sshfs -o IdentityFile=/path/to/id_rsa username@cluster-name.it4i.cz:. mountpoint
 ```
 
-Using sshfs, the users Barbora home directory will be mounted on your local computer, just like an external disk.
+Using SSHFS, the user's Barbora home directory will be mounted on your local computer, just like an external disk.
 
 Learn more about SSH, SCP, and SSHFS by reading the manpages:
 
@@ -194,7 +194,7 @@ More information about the shared file systems is available [here][4].
 
 ## Connection Restrictions
 
-Outgoing connections, from cluster login nodes to the outside world, are restricted to the following ports:
+Outgoing connections from cluster login nodes to the outside world, are restricted to the following ports:
 
 | Port | Protocol |
 | ---- | -------- |
@@ -206,7 +206,7 @@ Outgoing connections, from cluster login nodes to the outside world, are restric
 !!! note
     Use **SSH port forwarding** and proxy servers to connect from cluster to all other remote ports.
 
-Outgoing connections, from cluster compute nodes are restricted to the internal network. Direct connections from compute nodes to the outside world are cut.
+Outgoing connections from cluster compute nodes are restricted to the internal network. Direct connections from compute nodes to the outside world are cut.
 
 ## Port Forwarding
 
@@ -215,7 +215,7 @@ Outgoing connections, from cluster compute nodes are restricted to the internal
 !!! note
     Port forwarding allows an application running on cluster to connect to arbitrary remote hosts and ports.
 
-It works by tunneling the connection from cluster back to users' workstations and forwarding from the workstation to the remote host.
+It works by tunneling the connection from cluster back to the user's workstations and forwarding from the workstation to the remote host.
 
 Pick some unused port on the cluster login node  (for example 6000) and establish the port forwarding:
 
@@ -223,11 +223,11 @@ Pick some unused port on the cluster login node  (for example 6000) and establis
 $ ssh -R 6000:remote.host.com:1234 cluster-name.it4i.cz
 ```
 
-In this example, we establish port forwarding between port 6000 on the cluster and port 1234 on the remote.host.com. By accessing localhost:6000 on the cluster, an application will see the response of remote.host.com:1234. The traffic will run via the user's local workstation.
+In this example, we establish port forwarding between port 6000 on the cluster and port 1234 on the `remote.host.com`. By accessing `localhost:6000` on the cluster, an application will see the response of `remote.host.com:1234`. The traffic will run via the user's local workstation.
 
-Port forwarding may be done **using PuTTY** as well. On the PuTTY Configuration screen, load your cluster configuration first. Then go to *Connection->SSH->Tunnels* to set up the port forwarding. Click the Remote radio button. Insert 6000 to the Source port textbox. Insert remote.host.com:1234. Click the Add button, then Open.
+Port forwarding may be done **using PuTTY** as well. On the PuTTY Configuration screen, load your cluster configuration first. Then go to *Connection->SSH->Tunnels* to set up the port forwarding. Click the Remote radio button. Insert 6000 to the Source port textbox. Insert `remote.host.com:1234`. Click the Add button, then Open.
 
-Port forwarding may be established directly to the remote host. However, this requires that the user has an SSH access to remote.host.com.
+Port forwarding may be established directly to the remote host. However, this requires that the user has an SSH access to `remote.host.com`.
 
 ```console
 $ ssh -L 6000:localhost:1234 remote.host.com
@@ -271,7 +271,7 @@ Once the proxy server is running, establish the SSH port forwarding from cluster
 $ ssh -R 6000:localhost:1080 cluster-name.it4i.cz
 ```
 
-Now, configure the applications proxy settings to **localhost:6000**. Use port forwarding to access the [proxy server from compute nodes][5] as well.
+Now, configure the applications proxy settings to `localhost:6000`. Use port forwarding to access the [proxy server from compute nodes][5] as well.
 
 ## Graphical User Interface
 

[Jan Siwiec]

relates to #70