diff --git a/docs.it4i/anselm/shell-and-data-access.md b/docs.it4i/anselm/shell-and-data-access.md
index ec6660db4c650f5be626c3f08213b05c48db1496..ce096b19338238f4f414abfabd6eac222c0098c2 100644
--- a/docs.it4i/anselm/shell-and-data-access.md
+++ b/docs.it4i/anselm/shell-and-data-access.md
@@ -30,13 +30,13 @@ Private key authentication:
 On **Linux** or **Mac**, use
 
 ```console
-local $ ssh -i /path/to/id_rsa username@anselm.it4i.cz
+$ ssh -i /path/to/id_rsa username@anselm.it4i.cz
 ```
 
 If you see warning message "UNPROTECTED PRIVATE KEY FILE!", use this command to set lower permissions to private key file.
 
 ```console
-local $ chmod 600 /path/to/id_rsa
+$ chmod 600 /path/to/id_rsa
 ```
 
 On **Windows**, use [PuTTY ssh client](../general/accessing-the-clusters/shell-access-and-data-transfer/putty.md).
@@ -89,23 +89,23 @@ To achieve 160MB/s transfer rates, the end user must be connected by 10G line al
 On linux or Mac, use scp or sftp client to transfer the data to Anselm:
 
 ```console
-local $ scp -i /path/to/id_rsa my-local-file username@anselm.it4i.cz:directory/file
+$ scp -i /path/to/id_rsa my-local-file username@anselm.it4i.cz:directory/file
 ```
 
 ```console
-local $ scp -i /path/to/id_rsa -r my-local-dir username@anselm.it4i.cz:directory
+$ scp -i /path/to/id_rsa -r my-local-dir username@anselm.it4i.cz:directory
 ```
 
 or
 
 ```console
-local $ sftp -o IdentityFile=/path/to/id_rsa username@anselm.it4i.cz
+$ sftp -o IdentityFile=/path/to/id_rsa username@anselm.it4i.cz
 ```
 
 Very convenient way to transfer files in and out of the Anselm computer is via the fuse filesystem [sshfs](http://linux.die.net/man/1/sshfs)
 
 ```console
-local $ sshfs -o IdentityFile=/path/to/id_rsa username@anselm.it4i.cz:. mountpoint
+$ sshfs -o IdentityFile=/path/to/id_rsa username@anselm.it4i.cz:. mountpoint
 ```
 
 Using sshfs, the users Anselm home directory will be mounted on your local computer, just like an external disk.
@@ -150,7 +150,7 @@ It works by tunneling the connection from Anselm back to users workstation and f
 Pick some unused port on Anselm login node  (for example 6000) and establish the port forwarding:
 
 ```console
-local $ ssh -R 6000:remote.host.com:1234 anselm.it4i.cz
+$ ssh -R 6000:remote.host.com:1234 anselm.it4i.cz
 ```
 
 In this example, we establish port forwarding between port 6000 on Anselm and port 1234 on the remote.host.com. By accessing localhost:6000 on Anselm, an application will see response of remote.host.com:1234. The traffic will run via users local workstation.
@@ -190,7 +190,7 @@ Port forwarding is static, each single port is mapped to a particular port on re
 To establish local proxy server on your workstation, install and run SOCKS proxy server software. On Linux, sshd demon provides the functionality. To establish SOCKS proxy server listening on port 1080 run:
 
 ```console
-local $ ssh -D 1080 localhost
+$ ssh -D 1080 localhost
 ```
 
 On Windows, install and run the free, open source [Sock Puppet](http://sockspuppet.com/) server.
@@ -198,7 +198,7 @@ On Windows, install and run the free, open source [Sock Puppet](http://sockspupp
 Once the proxy server is running, establish ssh port forwarding from Anselm to the proxy server, port 1080, exactly as [described above](#port-forwarding-from-login-nodes).
 
 ```console
-local $ ssh -R 6000:localhost:1080 anselm.it4i.cz
+$ ssh -R 6000:localhost:1080 anselm.it4i.cz
 ```
 
 Now, configure the applications proxy settings to **localhost:6000**. Use port forwarding to access the [proxy server from compute nodes](#port-forwarding-from-compute-nodes) as well.