From f2a30879ccddf03810f21603a36f2fdb5785af81 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Krup=C4=8D=C3=ADk?= <lukas.krupcik@vsb.cz>
Date: Wed, 24 Aug 2016 07:24:25 +0200
Subject: [PATCH] modify

---
 .../cygwin-and-x11-forwarding.md              |  35 +---
 .../graphical-user-interface.md               |  22 +--
 .../graphical-user-interface/vnc.md           | 174 ++++++------------
 .../x-window-system.md                        | 149 +++++----------
 .../accessing-the-clusters/introduction.md    |  19 +-
 .../introduction.md                           |  21 ---
 .../shell-access-and-data-transfer/pageant.md |  17 +-
 .../shell-access-and-data-transfer/putty.md   |  89 +++------
 .../puttygen.md                               |  79 +++-----
 .../ssh-keys.md                               |  94 +++-------
 .../vpn-connection-fail-in-win-8.1.md         |  14 +-
 .../applying-for-resources.md                 |  39 +---
 12 files changed, 236 insertions(+), 516 deletions(-)
 delete mode 100644 docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/introduction.md

diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/cygwin-and-x11-forwarding.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/cygwin-and-x11-forwarding.md
index 3631336e7..0d1de9f9d 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/cygwin-and-x11-forwarding.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/cygwin-and-x11-forwarding.md
@@ -1,44 +1,27 @@
-Cygwin and X11 forwarding 
+Cygwin and X11 forwarding
 =========================
 
 ### If  no able to forward X11 using PuTTY to CygwinX
 
-`
+```bash
 [usename@login1.anselm ~]$ gnome-session &
 [1] 23691
 [usename@login1.anselm ~]$ PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused
 PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused
 
   (gnome-session:23691): WARNING **: Cannot open display:**
-`
+```
 
- Â 
-
-1.   Locate and modify
-     Cygwin shortcut that
-    uses
-    Â [startxwin](http://x.cygwin.com/docs/man1/startxwin.1.html)
+1. Locate and modify Cygwin shortcut that uses [startxwin](http://x.cygwin.com/docs/man1/startxwin.1.html)
     locate
     C:cygwin64binXWin.exe
-     
-    
     change it
     to
     C:*cygwin64binXWin.exe -listen tcp*
-    
-    ![XWin-listen-tcp.png](XWinlistentcp.png "XWin-listen-tcp.png")
-    
-     
-    
-2.   
-    Check Putty settings:
-     Enable X11
-    forwarding 
-    
-    
-    
-    ![](cygwinX11forwarding.png)
-    
 
-Â 
+![XWin-listen-tcp.png](XWinlistentcp.png "XWin-listen-tcp.png")
+
+2. Check Putty settings:
+     Enable X11 forwarding
 
+    ![](cygwinX11forwarding.png)
\ No newline at end of file
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/graphical-user-interface.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/graphical-user-interface.md
index 70dc2f50f..517b9a806 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/graphical-user-interface.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/graphical-user-interface.md
@@ -1,29 +1,17 @@
-Graphical User Interface 
+Graphical User Interface
 ========================
 
-  
-
 X Window System
 ---------------
 
-The X Window system is a principal way to get GUI access to the
-clusters.
+The X Window system is a principal way to get GUI access to the clusters.
 
-Read more about configuringÂ [**X Window
-System**](x-window-system/x-window-and-vnc.html).
+Read more about configuringÂ [**X Window System**](x-window-system/x-window-and-vnc.html).
 
 VNC
 ---
 
-The **Virtual Network Computing** (**VNC**) is a graphical 
-[desktop
-sharing](http://en.wikipedia.org/wiki/Desktop_sharing "Desktop sharing")
-system that uses the  [Remote Frame Buffer
-protocol
-(RFB)](http://en.wikipedia.org/wiki/RFB_protocol "RFB protocol")
-to remotely control another 
-[computer](http://en.wikipedia.org/wiki/Computer "Computer").
+The **Virtual Network Computing** (**VNC**) is a graphical [desktop sharing](http://en.wikipedia.org/wiki/Desktop_sharing "Desktop sharing") system that uses the  [Remote Frame Buffer protocol (RFB)](http://en.wikipedia.org/wiki/RFB_protocol "RFB protocol") to remotely control another [computer](http://en.wikipedia.org/wiki/Computer "Computer").
 
-Read more about configuring
-**[VNC](../../../salomon/accessing-the-cluster/graphical-user-interface/vnc.html)**.
+Read more about configuring **[VNC](../../../salomon/accessing-the-cluster/graphical-user-interface/vnc.html)**.
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/vnc.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/vnc.md
index c5a12afdd..65b71eb51 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/vnc.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/vnc.md
@@ -1,141 +1,108 @@
-VNC 
+VNC
 ===
 
-  
-
-The **Virtual Network Computing** (**VNC**) is a graphical [desktop
-sharing](http://en.wikipedia.org/wiki/Desktop_sharing "Desktop sharing")
-system that uses the [Remote Frame Buffer protocol
-(RFB)](http://en.wikipedia.org/wiki/RFB_protocol "RFB protocol") to
-remotely control another
-[computer](http://en.wikipedia.org/wiki/Computer "Computer"). It
-transmits the
-[keyboard](http://en.wikipedia.org/wiki/Computer_keyboard "Computer keyboard")
-and
-[mouse](http://en.wikipedia.org/wiki/Computer_mouse "Computer mouse")
-events from one computer to another, relaying the graphical
-[screen](http://en.wikipedia.org/wiki/Computer_screen "Computer screen")
-updates back in the other direction, over a
-[network](http://en.wikipedia.org/wiki/Computer_network "Computer network").(http://en.wikipedia.org/wiki/Virtual_Network_Computing#cite_note-1)
-
-The recommended clients are
-[TightVNC](http://www.tightvnc.com) or
-[TigerVNC](http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Main_Page)
-(free, open source, available for almost any platform).
+The **Virtual Network Computing** (**VNC**) is a graphical [desktop sharing](http://en.wikipedia.org/wiki/Desktop_sharing "Desktop sharing") system that uses the [Remote Frame Buffer protocol (RFB)](http://en.wikipedia.org/wiki/RFB_protocol "RFB protocol") to remotely control another [computer](http://en.wikipedia.org/wiki/Computer "Computer"). It transmits the [keyboard](http://en.wikipedia.org/wiki/Computer_keyboard "Computer keyboard") and [mouse] http://en.wikipedia.org/wiki/Computer_mouse "Computer mouse") events from one computer to another, relaying the graphical [screen](http://en.wikipedia.org/wiki/Computer_screen "Computer screen") updates back in the other direction, over a [network](http://en.wikipedia.org/wiki/Computer_network "Computer network").
+
+The recommended clients are [TightVNC](http://www.tightvnc.com) or[TigerVNC](http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Main_Page) (free, open source, available for almost any platform).
 
 Create VNC password
 -------------------
 
-Local VNC password should be set before the first login. Do use a strong
-password.
+>Local VNC password should be set before the first login. Do use a strong password.
 
-`
+```bash
 [username@login2 ~]$ vncpasswd
 Password:
 Verify:
-`
+```
 
 Start vncserver
 ---------------
 
-To access VNC a local vncserver must beÂ  started first and also a tunnel
-using SSH port forwarding must be established.
-[See below](vnc.html#linux-example-of-creating-a-tunnel)
-for the details on SSH tunnels. In this example we use port 61.
+>To access VNC a local vncserver must beÂ  started first and also a tunnel using SSH port forwarding must be established.
+[See below](vnc.html#linux-example-of-creating-a-tunnel) for the details on SSH tunnels. In this example we use port 61.
 
-You can find ports which are already occupied. Here you can see that
-ports " /usr/bin/Xvnc :79" and "
-/usr/bin/Xvnc :60" are occupied.
+You can find ports which are already occupied. Here you can see that ports " /usr/bin/Xvnc :79" and " /usr/bin/Xvnc :60" are occupied.
 
-`
+```bash
 [username@login2 ~]$ ps aux | grep Xvnc
 usernameÂ Â Â  5971Â  0.0Â  0.0 201072 92564 ?Â Â Â Â Â Â Â  SNÂ Â  Sep22Â Â  4:19 /usr/bin/Xvnc :79 -desktop login2:79 (username) -auth /home/gre196/.Xauthority -geometry 1024x768 -rfbwait 30000 -rfbauth /home/username/.vnc/passwd -rfbport 5979 -fp catalogue:/etc/X11/fontpath.d -pn
 usernameÂ Â Â  10296Â  0.0Â  0.0 131772 21076 pts/29Â Â  SNÂ Â  13:01Â Â  0:01 /usr/bin/Xvnc :60 -desktop login2:61 (username) -auth /home/username/.Xauthority -geometry 1600x900 -depth 16 -rfbwait 30000 -rfbauth /home/jir13/.vnc/passwd -rfbport 5960 -fp catalogue:/etc/X11/fontpath.d -pn
 .....
-`
+```
 
 Choose free port e.g. 61 and start your VNC server:
 
-`
+```bash
 [username@login2 ~]$ vncserver :61 -geometry 1600x900 -depth 16
 
 New 'login2:1 (username)' desktop is login2:1
 
 Starting applications specified in /home/username/.vnc/xstartup
 Log file is /home/username/.vnc/login2:1.log
-`
+```
 
 Check if VNC server is started on the port (in this example 61):
 
-`
+```bash
 [username@login2 .vnc]$ vncserver -list
 
 TigerVNC server sessions:
 
 X DISPLAY #Â Â Â Â  PROCESS ID
 :61Â Â Â Â Â Â Â Â Â Â Â Â Â  18437
-`
+```
 
-Another command: 
+Another command:
 
-`
+```bash
 [username@login2 .vnc]$ Â ps aux | grep Xvnc
 
 usernameÂ Â Â  10296Â  0.0Â  0.0 131772 21076 pts/29Â Â  SNÂ Â  13:01Â Â  0:01 /usr/bin/Xvnc :61 -desktop login2:61 (username) -auth /home/jir13/.Xauthority -geometry 1600x900 -depth 16 -rfbwait 30000 -rfbauth /home/username/.vnc/passwd -rfbport 5961 -fp catalogue:/etc/X11/fontpath.d -pn
-`
+```
 
-To access the VNC server you have to create a tunnel between the login
-node using TCP **port 5961** and your machine using a free TCP port (for
-simplicity the very same, in this case).
+To access the VNC server you have to create a tunnel between the login node using TCP **port 5961** and your machine using a free TCP port (for simplicity the very same, in this case).
 
-The tunnel must point to the same login node where you launched the VNC
-server, eg. login2. If you use just cluster-name.it4i.cz, the tunnel
-might point to a different node due to DNS round robin.
+>The tunnel must point to the same login node where you launched the VNC server, eg. login2. If you use just cluster-name.it4i.cz, the tunnel might point to a different node due to DNS round robin.
 
 ###Linux/Mac OS example of creating a tunnel
 
 At your machine, create the tunnel:
 
-`
+```bash
 local $Â  ssh -TN -f username@login2.cluster-name.it4i.cz -L 5961:localhost:5961
-`
+```
 
-Issue the following command to check the tunnel is established (please
-note the PID 2022 in the last column, you'll need it for closing the
-tunnel):
+Issue the following command to check the tunnel is established (please note the PID 2022 in the last column, you'll need it for closing the tunnel):
 
-`
+```bash
 local $ netstat -natp | grep 5961
 (Not all processes could be identified, non-owned process info
 Â will not be shown, you would have to be root to see it all.)
-tcpÂ Â Â Â Â Â Â  0Â Â Â Â Â  0 127.0.0.1:5961Â Â Â Â Â Â Â Â Â  0.0.0.0:*Â Â Â Â Â Â Â Â Â Â Â Â Â Â  LISTENÂ Â Â Â Â  2022/sshÂ Â Â Â Â Â Â  
-tcp6Â Â Â Â Â Â  0Â Â Â Â Â  0 ::1:5961Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  :::*Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  LISTENÂ Â Â Â Â  2022/ssh 
-`
+tcpÂ Â Â Â Â Â Â  0Â Â Â Â Â  0 127.0.0.1:5961Â Â Â Â Â Â Â Â Â  0.0.0.0:*Â Â Â Â Â Â Â Â Â Â Â Â Â Â  LISTENÂ Â Â Â Â  2022/ssh
+tcp6Â Â Â Â Â Â  0Â Â Â Â Â  0 ::1:5961Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  :::*Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  LISTENÂ Â Â Â Â  2022/ssh
+```
 
 Or on Mac OS use this command:
 
-`
+```bash
 local-mac $ lsof -n -i4TCP:5961 | grep LISTEN
 ssh 75890 sta545 7u IPv4 0xfb062b5c15a56a3b 0t0 TCP 127.0.0.1:5961 (LISTEN)
-`
+```
 
 Connect with the VNC client:
 
-`
+```bash
 local $ vncviewer 127.0.0.1:5961
-`
+```
 
-In this example, we connect to VNC server on port 5961, via the ssh
-tunnel. The connection is encrypted and secured. The VNC server
-listening on port 5961 provides screen of 1600x900 pixels.
+In this example, we connect to VNC server on port 5961, via the ssh tunnel. The connection is encrypted and secured. The VNC server listening on port 5961 provides screen of 1600x900 pixels.
 
-You have to destroy the SSH tunnel which is still running at the
-background after you finish the work. Use the following command (PID
-2022 in this case, see the netstat command above):
+You have to destroy the SSH tunnel which is still running at the background after you finish the work. Use the following command (PID 2022 in this case, see the netstat command above):
 
-`
+```bash
 kill 2022
-`
+```
 
 ### Windows example of creating a tunnel
 
@@ -143,40 +110,32 @@ Use PuTTY to log in on cluster.
 
 Start vncserver using command vncserver described above.
 
-**Search for the localhost and port number (in this case
-127.0.0.1:5961).**
+Search for the localhost and port number (in this case 127.0.0.1:5961).
 
-`
+```bahs
 [username@login2 .vnc]$ netstat -tanp | grep Xvnc
 (Not all processes could be identified, non-owned process info
 Â will not be shown, you would have to be root to see it all.)
 tcpÂ Â Â Â Â Â Â  0Â Â Â Â Â  0 127.0.0.1:5961Â Â Â Â Â Â Â Â Â Â Â Â Â  0.0.0.0:*Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  LISTENÂ Â Â Â Â  24031/Xvnc
-`
+```
 
-On the PuTTY Configuration screen go to Connection-&gt;SSH-&gt;Tunnels
-to set up the tunnel.
+On the PuTTY Configuration screen go to Connection-&gt;SSH-&gt;Tunnels to set up the tunnel.
 
-Fill the Source port and Destination fields. **Do not forget to click
-the Add button**.
+Fill the Source port and Destination fields. **Do not forget to click the Add button**.
 
 ![](putty-tunnel.png)
 
-Run the VNC client of your choice, select VNC server 127.0.0.1, port
-5961 and connect using VNC password.
+Run the VNC client of your choice, select VNC server 127.0.0.1, port 5961 and connect using VNC password.
 
 ### Example of starting TigerVNC viewer
 
 ![](vncviewer.png)
 
-In this example, we connect to VNC server on port 5961, via the ssh
-tunnel, using TigerVNC viewer. The connection is encrypted and secured.
-The VNC server listening on port 5961 provides screen of 1600x900
-pixels.
+In this example, we connect to VNC server on port 5961, via the ssh tunnel, using TigerVNC viewer. The connection is encrypted and secured. The VNC server listening on port 5961 provides screen of 1600x900 pixels.
 
 ### Example of starting TightVNC Viewer
 
-Use your VNC password to log using TightVNC Viewer and start a Gnome
-Session on the login node.
+Use your VNC password to log using TightVNC Viewer and start a Gnome Session on the login node.
 
 ![](TightVNC_login.png)
 
@@ -199,69 +158,58 @@ Uncheck both options below the slider:
 
 ### Kill screensaver if locked screen
 
-If the screen gets locked you have to kill the screensaver. Do not to
-forget to disable the screensaver then.
+If the screen gets locked you have to kill the screensaver. Do not to forget to disable the screensaver then.
 
-`
+```bash
 [username@login2 .vnc]$ ps aux | grep screen
 usernameÂ Â Â Â  1503Â  0.0Â  0.0 103244Â Â  892 pts/4Â Â Â  S+Â Â  14:37Â Â  0:00 grep screen
 usernameÂ Â Â Â  24316Â  0.0Â  0.0 270564Â  3528 ?Â Â Â Â Â Â Â  SsÂ Â  14:12Â Â  0:00 gnome-screensaver
 
 [username@login2 .vnc]$ kill 24316
-`
+```
 
 ### Kill vncserver after finished work
 
 You should kill your VNC server using command:
 
-`
+```bash
 [username@login2 .vnc]$Â  vncserverÂ  -kill :61
 Killing Xvnc process ID 7074
 Xvnc process ID 7074 already killed
-`
+```
 
 Or this way:
 
-`
+```bash
 [username@login2 .vnc]$Â  pkill vnc
-`
+```
 
 GUI applications on compute nodesÂ over VNC
 ------------------------------------------
 
-The very [same methods as described
-above](https://docs.it4i.cz/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-and-vnc#gui-applications-on-compute-nodes),
-may be used to run the GUI applications on compute nodes. However, for
-maximum performance, proceed following these steps:
+The very [same methods as described above](https://docs.it4i.cz/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-and-vnc#gui-applications-on-compute-nodes), may be used to run the GUI applications on compute nodes. However, for maximum performance, proceed following these steps:
 
-Open a Terminal (Applications -&gt; System Tools -&gt; Terminal). Run
-all the next commands in the terminal.
+Open a Terminal (Applications -&gt; System Tools -&gt; Terminal). Run all the next commands in the terminal.
 
 ![](gnome-terminal.png)
 
 Allow incoming X11 graphics from the compute nodes at the login node:
 
-`
+```bash
 $ xhost +
-`
+```
 
-Get an interactive session on a compute node (for more detailed info
-[look
-here](../../../../anselm-cluster-documentation/resource-allocation-and-job-execution/job-submission-and-execution.html)).
-Use the **-v DISPLAY** option to propagate the DISPLAY on the compute
-node. In this example, we want a complete node (24 cores in this
-example) from the production queue:
+Get an interactive session on a compute node (for more detailed info [look here](../../../../anselm-cluster-documentation/resource-allocation-and-job-execution/job-submission-and-execution.html)). Use the **-v DISPLAY** option to propagate the DISPLAY on the compute node. In this example, we want a complete node (24 cores in this example) from the production queue:
 
-`
+```bash
 $ qsub -I -v DISPLAY=$(uname -n):$(echo $DISPLAY | cut -d ':' -f 2) -A PROJECT_ID -q qprod -l select=1:ncpus=24
-`
+```
 
-Test that the DISPLAY redirection into your VNC session works, by
-running a X11 application (e. g. XTerm) on the assigned compute node:
+Test that the DISPLAY redirection into your VNC session works, by running a X11 application (e. g. XTerm) on the assigned compute node:
 
-`
+```bash
 $ xterm
-`
+```
 
 Example described above:
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-system.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-system.md
index 9f9415f98..ad0311422 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-system.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-system.md
@@ -1,178 +1,131 @@
-X Window System 
+X Window System
 ===============
 
-  
+The X Window system is a principal way to get GUI access to the clusters. The **X Window System** (commonly known as **X11**, based on its current major version being 11, or shortened to simply **X**, and sometimes informally **X-Windows**) is a computer software system and network [protocol](http://en.wikipedia.org/wiki/Protocol_%28computing%29 "Protocol (computing)") that provides a basis for [graphical user interfaces](http://en.wikipedia.org/wiki/Graphical_user_interface "Graphical user interface") (GUIs) and rich input device capability for [networked computers](http://en.wikipedia.org/wiki/Computer_network "Computer network").
 
-The X Window system is a principal way to get GUI access to the
-clusters. The **X Window System** (commonly known as **X11**, based on
-its current major version being 11, or shortened to simply **X**, and
-sometimes informally **X-Windows**) is a computer software system and
-network
-[protocol](http://en.wikipedia.org/wiki/Protocol_%28computing%29 "Protocol (computing)")
-that provides a basis for [graphical user
-interfaces](http://en.wikipedia.org/wiki/Graphical_user_interface "Graphical user interface")
-(GUIs) and rich input device capability for [networked
-computers](http://en.wikipedia.org/wiki/Computer_network "Computer network").
-
-The X display forwarding must be activated and the X server running on
-client side
+>The X display forwarding must be activated and the X server running on client side
 
 ### X display
 
-In order to display graphical user interface GUI of various software
-tools, you need to enable the X display forwarding. On Linux and Mac,
-log in using theÂ -X option tho ssh client:
+In order to display graphical user interface GUI of various software tools, you need to enable the X display forwarding. On Linux and Mac, log in using theÂ -X option tho ssh client:
 
-`
+```bash
  local $ ssh -X username@cluster-name.it4i.cz
-`
+```
 
 ### X Display Forwarding on Windows
 
-On Windows use the PuTTY client to enable X11 forwarding. Â  In PuTTY
-menu, go to Connection-&gt;SSH-&gt;X11, mark the Enable X11 forwarding
-checkbox before logging in. Then log in as usual.
+On Windows use the PuTTY client to enable X11 forwarding. In PuTTY menu, go to Connection-&gt;SSH-&gt;X11, mark the Enable X11 forwarding checkbox before logging in. Then log in as usual.
 
 To verify the forwarding, type
 
-`
+```bash
 $ echo $DISPLAY
-`
+```
 
 if you receive something like
 
-`
+```bash
 localhost:10.0
-`
+```
 
 then the X11 forwarding is enabled.
 
 ### X Server
 
-In order to display graphical user interface GUI of various software
-tools, you need running X server on your desktop computer. For Linux
-users, no action is required as the X server is the default GUI
-environment on most Linux distributions. Mac and Windows users need to
-install and run the X server on their workstations.
+In order to display graphical user interface GUI of various software tools, you need running X server on your desktop computer. For Linux users, no action is required as the X server is the default GUI environment on most Linux distributions. Mac and Windows users need to install and run the X server on their workstations.
 
 ### X Server on OS X
 
-Mac OS users need to install [XQuartz
-server](http://xquartz.macosforge.org/landing/).
+Mac OS users need to install [XQuartz server](http://xquartz.macosforge.org/landing/).
 
 ### X Server on Windows
 
-There are variety of X servers available for Windows environment. The
-commercial Xwin32 is very stable and rich featured. The Cygwin
-environment provides fully featured open-source XWin X server. For
-simplicity, we recommend open-source X server by the [Xming
-project](http://sourceforge.net/projects/xming/). For
-stability and full features we recommend the
+There are variety of X servers available for Windows environment. The commercial Xwin32 is very stable and rich featured. The Cygwin environment provides fully featured open-source XWin X server. For simplicity, we recommend open-source X server by the [Xming project](http://sourceforge.net/projects/xming/). For stability and full features we recommend the
 [XWin](http://x.cygwin.com/) X server by Cygwin
 
  |How to use Xwin |How to use Xming |
  | --- | --- |
- |[Install Cygwin](http://x.cygwin.com/)Find and execute XWin.exeto start the X server on Windows desktop computer.[If no able to forward X11 using PuTTY to CygwinX](x-window-system/cygwin-and-x11-forwarding.html)\ |<p>Use Xlaunch to configure the Xming.<p>Run Xmingto start the X server on Windows desktop computer.\ |
+ |[Install Cygwin](http://x.cygwin.com/)Find and execute XWin.exeto start the X server on Windows desktop computer.[If no able to forward X11 using PuTTY to CygwinX](x-window-system/cygwin-and-x11-forwarding.html) |<p>Use Xlaunch to configure the Xming.<p>Run Xmingto start the X server on Windows desktop computer.|
 
-Read more on
-[http://www.math.umn.edu/systems_guide/putty_xwin32.html](http://www.math.umn.edu/systems_guide/putty_xwin32.shtml)
+Read more on [http://www.math.umn.edu/systems_guide/putty_xwin32.html](http://www.math.umn.edu/systems_guide/putty_xwin32.shtml)
 
 ### Running GUI Enabled Applications
 
-Make sure that X forwarding is activated and the X server is running.
+>Make sure that X forwarding is activated and the X server is running.
 
-Then launch the application as usual. Use the & to run the application
-in background.
+Then launch the application as usual. Use the & to run the application in background.
 
-`
+```bash
 $ module load intel (idb and gvim not installed yet)
 $ gvim &
-`
+```
 
-`
+```bash
 $ xterm
-`
+```
 
-In this example, we activate the intel programing environment tools,
-then start the graphical gvim editor.
+In this example, we activate the intel programing environment tools, then start the graphical gvim editor.
 
 ### GUI Applications on Compute Nodes
 
 Allocate the compute nodes using -X option on the qsub command
 
-`
+```bash
 $ qsub -q qexp -l select=2:ncpus=24 -X -I
-`
+```
 
-In this example, we allocate 2 nodes via qexp queue, interactively. We
-request X11 forwarding with the -X option. It will be possible to run
-the GUI enabled applications directly on the first compute node.
+In this example, we allocate 2 nodes via qexp queue, interactively. We request X11 forwarding with the -X option. It will be possible to run the GUI enabled applications directly on the first compute node.
 
-**Better performance** is obtained by logging on the allocated compute
-node via ssh, using the -X option.
+**Better performance** is obtained by logging on the allocated compute node via ssh, using the -X option.
 
-`
+```bash
 $ ssh -X r24u35n680
-`
-
-In this example, we log in on theÂ r24u35n680 compute node, with the X11
-forwarding enabled.
+```
 
-HTML commented section #1 (no GUI on Compute nodes - Xvfb)
+In this example, we log in on theÂ r24u35n680 compute node, with the X11 forwarding enabled.
 
 ### The Gnome GUI Environment
 
-The Gnome 2.28 GUI environment is available on the clusters. We
-recommend to use separate X server window for displaying the Gnome
-environment.
+The Gnome 2.28 GUI environment is available on the clusters. We recommend to use separate X server window for displaying the Gnome environment.
 
 ### Gnome on Linux and OS X
 
-To run the remote Gnome session in a window on Linux/OS X computer, you
-need to install Xephyr. Ubuntu package is 
-xserver-xephyr, on OS X it is part of
-[XQuartz](http://xquartz.macosforge.org/landing/).
-First, launch Xephyr on local machine:
+To run the remote Gnome session in a window on Linux/OS X computer, you need to install Xephyr. Ubuntu package is
+xserver-xephyr, on OS X it is part of [XQuartz](http://xquartz.macosforge.org/landing/). First, launch Xephyr on local machine:
 
-`
+```bash
 local $ Xephyr -ac -screen 1024x768 -br -reset -terminate :1 &
-`
+```
 
-This will open a new X window with size 1024x768 at DISPLAY :1. Next,
-ssh to the cluster with DISPLAY environment variable set and launch
- gnome-session
+This will open a new X window with size 1024x768 at DISPLAY :1. Next, ssh to the cluster with DISPLAY environment variable set and launch  gnome-session
 
-    local $ DISPLAY=:1.0 ssh -XC yourname@cluster-name.it4i.cz -i ~/.ssh/path_to_your_key
-    ... cluster-name MOTD...
-    yourname@login1.cluster-namen.it4i.cz $Â gnome-session &
+```bash
+local $ DISPLAY=:1.0 ssh -XC yourname@cluster-name.it4i.cz -i ~/.ssh/path_to_your_key
+... cluster-name MOTD...
+yourname@login1.cluster-namen.it4i.cz $Â gnome-session &
+```
 
-On older systems where Xephyr is not available, you may also try Xnest
-instead of Xephyr. Another option is to launch a new X server in a
-separate console, via:
+On older systems where Xephyr is not available, you may also try Xnest instead of Xephyr. Another option is to launch a new X server in a separate console, via:
 
-`
+```bash
 xinit /usr/bin/ssh -XT -i .ssh/path_to_your_key yourname@cluster-namen.it4i.cz gnome-session -- :1 vt12
-`
+```
 
-However this method does not seem to work with recent Linux
-distributions and you will need to manually source 
-/etc/profile to properly set environment
-variables for PBS.
+However this method does not seem to work with recent Linux distributions and you will need to manually source
+/etc/profile to properly set environment variables for PBS.
 
 ### Gnome on Windows
 
-Use Xlaunch to start the Xming server or run the XWin.exe. Select the
-''One window" mode.
+Use Xlaunch to start the Xming server or run the XWin.exe. Select the "One window" mode.
 
-Log in to the cluster, using PuTTY. On the cluster, run the
-gnome-session command.
+Log in to the cluster, using PuTTY. On the cluster, run the gnome-session command.
 
-`
+```bash
 $ gnome-session &
-`
+```
 
-In this way, we run remote gnome session on the cluster, displaying it
-in the local X server
+In this way, we run remote gnome session on the cluster, displaying it in the local X server
 
 Use System-&gt;Log Out to close the gnome-session
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/introduction.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/introduction.md
index bcf136329..2920547b6 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/introduction.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/introduction.md
@@ -1,22 +1,15 @@
-Accessing the Clusters 
+Accessing the Clusters
 ======================
 
-The IT4Innovations clusters are accessed by SSH protocol via login
-nodes.
+The IT4Innovations clusters are accessed by SSH protocol via login nodes.
 
-Read more on [Accessing the Salomon
-Cluste](../salomon/accessing-the-cluster.html)r or
-[Accessing the Anselm
-Cluster](../anselm-cluster-documentation/accessing-the-cluster.html)
-pages.
+>Read more on [Accessing the Salomon Cluste](../salomon/accessing-the-cluster.html)r or [Accessing the Anselm Cluster](../anselm-cluster-documentation/accessing-the-cluster.html) pages.
 
 ### PuTTY
 
-On **Windows**, use [PuTTY ssh
-client](accessing-the-clusters/shell-access-and-data-transfer/putty/putty.html).
+On **Windows**, use [PuTTY ssh client](accessing-the-clusters/shell-access-and-data-transfer/putty/putty.html).
 
-### SSH keys 
+### SSH keys
 
-Read more about [SSH keys
-management](accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.html).
+Read more about [SSH keys management](accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.html).
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/introduction.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/introduction.md
deleted file mode 100644
index 3f5be332a..000000000
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/introduction.md
+++ /dev/null
@@ -1,21 +0,0 @@
-Accessing the Clusters 
-======================
-
-The IT4Innovations clusters are accessed by SSH protocol via login
-nodes.
-
-Read more on [Accessing the Salomon
-Cluste](../../../salomon/accessing-the-cluster.html)r or
-[Accessing the Anselm
-Cluster](../../../anselm-cluster-documentation/accessing-the-cluster.html)
-pages.
-
-### PuTTY
-
-On **Windows**, use [PuTTY ssh
-client](putty/putty.html).
-
-### SSH keys 
-
-Read more about [SSH keys management](ssh-keys.html).
-
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/pageant.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/pageant.md
index eb8d63db1..ca2c2b620 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/pageant.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/pageant.md
@@ -1,19 +1,12 @@
-Pageant SSH agent 
+Pageant SSH agent
 =================
 
-  
-
-Pageant holds your private key in memory without needing to retype a
-passphrase on every login.
+Pageant holds your private key in memory without needing to retype a passphrase on every login.
 
 -   Run Pageant.
--   On Pageant Key List press *Add key* and select your private
-    key (id_rsa.ppk).
+-   On Pageant Key List press *Add key* and select your private key (id_rsa.ppk).
 -   Enter your passphrase.
--   Now you have your private key in memory without needing to retype a
-    passphrase on every login.
-    
-    ![](PageantV.png)
+-   Now you have your private key in memory without needing to retype a passphrase on every login.
 
-Â 
+![](PageantV.png)
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/putty.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/putty.md
index b3e8ac55e..d1889083c 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/putty.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/putty.md
@@ -1,89 +1,56 @@
-PuTTY 
+PuTTY
 =====
 
-  
-
-PuTTY -  before we start SSH connection 
+PuTTY -  before we start SSH connection
 ---------------------------------------------------------------------------------
 
 ### WindowsÂ PuTTY Installer
 
-We recommned you to download "**A Windows installer for everything
-except PuTTYtel**" with **Pageant*** (SSH authentication agent) and
-**PuTTYgen** (PuTTY key generator) which is available
-[here](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html).
-
- After installation you can proceed directly
-to private keys authentication using
-["Putty"](putty.html#putty).
-"Change Password for Existing Private Key" is optional.
-"Generate a New Public/Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)` pair" is intended for users without
-Public/Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)` in the initial email containing login credentials.
+We recommned you to download "**A Windows installer for everything except PuTTYtel**" with **Pageant*** (SSH authentication agent) and **PuTTYgen** (PuTTY key generator) which is available [here](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html).
+
+>After installation you can proceed directly to private keys authentication using ["Putty"](putty.html#putty).
+"Change Password for Existing Private Key" is optional. 
+"Generate a New Public/Private key pair" is intended for users without Public/Private key in the initial email containing login credentials.
 "Pageant" is optional.
 
 ### PuTTYgen
 
-PuTTYgen is the PuTTY key generator. Read more how to load in an
-existing private key and change your passphrase or generate a new
-public/private key pair using [PuTTYgen](puttygen.html)
-if needed.
+PuTTYgen is the PuTTY key generator. Read more how to load in an existing private key and change your passphrase or generate a new public/private key pair using [PuTTYgen](puttygen.html) if needed.
 
 ### Pageant SSH agent
 
-[Pageant](pageant.html) holds your private key in memory
-without needing to retype a passphrase on every login. We recommend its
-usage.
+[Pageant](pageant.html) holds your private key in memory without needing to retype a passphrase on every login. We recommend its usage.
 
 PuTTY - how to connect to the IT4Innovations cluster
 --------------------------------------------------------
 
 -   Run PuTTY
--   Enter Host name and Save session fields with [Login
-    address](../../../../salomon/accessing-the-cluster/shell-and-data-access/shell-and-data-access.html)
-    and browse Connection - &gt; SSH -&gt; Auth menu.
-    The *Host Name* input may be in the format
-    **"username@clustername.it4i.cz"** so you don't have to type your
-    login each time.
-    In this example we will connect to the Salomon cluster using
-    Â **"salomon.it4i.cz"**.
-    
-    ![](PuTTY_host_Salomon.png)
-
-Â 
+-   Enter Host name and Save session fields with [Login     address](../../../../salomon/accessing-the-cluster/shell-and-data-access/shell-and-data-access.html) and browse Connection - &gt; SSH -&gt; Auth menu. The *Host Name* input may be in the format **"username@clustername.it4i.cz"** so you don't have to type your login each time.In this example we will connect to the Salomon cluster usingÂ **"salomon.it4i.cz"**.
+
+![](PuTTY_host_Salomon.png)
 
 -   Category -&gt; Connection - &gt; SSH -&gt; Auth:
     Select Attempt authentication using Pageant.
     Select Allow agent forwarding.
-    Browse and select your [private
-    key](../ssh-keys.html) file.
-    
-    ![](PuTTY_keyV.png)
-    
--   Return to Session page and Save selected configuration with *Save*
-    button.
-    
-    ![](PuTTY_save_Salomon.png)
-    
+    Browse and select your [private key](../ssh-keys.html) file.
+
+![](PuTTY_keyV.png)
+
+-   Return to Session page and Save selected configuration with *Save* button.
+
+![](PuTTY_save_Salomon.png)
+
 -   Now you can log in using *Open* button.
-    
-    ![](PuTTY_open_Salomon.png)
-    
--   Enter yourÂ username if the *Host Name* input is not in the format
-    "username@salomon.it4i.cz".
-    
--   Enter passphrase for selected [private
-    key](../ssh-keys.html) file if Pageant **SSH
-    authentication agent is not used.**
-    
+
+![](PuTTY_open_Salomon.png)
+
+-   Enter yourÂ username if the *Host Name* input is not in the format "username@salomon.it4i.cz".
+-   Enter passphrase for selected [private key](../ssh-keys.html) file if Pageant **SSH authentication agent is not used.**
 
 Another PuTTY Settings
 ----------------------
 
--   Category -&gt; Windows -&gt; Translation -&gt; Remote character set
-    and select **UTF-8**.
-
--   Category -&gt; Terminal -&gt; Features and select **Disable
-    application keypad mode** (enable numpad)
--   Save your configuration on Session page in to Default Settings with
-    *Save* button .
+-   Category -&gt; Windows -&gt; Translation -&gt; Remote character set and select **UTF-8**.
+-   Category -&gt; Terminal -&gt; Features and select **Disable application keypad mode** (enable numpad)
+-   Save your configuration on Session page in to Default Settings with *Save* button .
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/puttygen.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/puttygen.md
index 33228da49..3945358af 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/puttygen.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/puttygen.md
@@ -1,70 +1,51 @@
-PuTTY key generator 
+PuTTY key generator
 ===================
 
-  
-
-PuTTYgen is the PuTTY key generator. You can load in an existing private
-key and change your passphrase or generate a new public/private key
-pair.
+PuTTYgen is the PuTTY key generator. You can load in an existing private key and change your passphrase or generate a new public/private key pair.
 
 ### Change Password for Existing Private Key
 
-You can change the password of your SSH key with "PuTTY Key Generator".
-Make sure to backup the key.
+You can change the password of your SSH key with "PuTTY Key Generator". Make sure to backup the key.
 
--   Load your [private key](../ssh-keys.html) file with
-    *Load* button.
+-   Load your [private key](../ssh-keys.html) file with     *Load* button.
 -   Enter your current passphrase.
 -   Change key passphrase.
 -   Confirm key passphrase.
 -   Save your private key with *Save private key* button.
-    
-    ![](PuttyKeygeneratorV.png)
 
-Â 
+![](PuttyKeygeneratorV.png)
 
-### Generate a New Public/Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)` pair
+### Generate a New Public/Private key
 
-You can generateÂ an additional public/private key pair and insert public
-key into authorized_keys file for authentication with your own private
-key. 
+You can generateÂ an additional public/private key pair and insert public key into authorized_keys file for authentication with your own private key.
 
 -   Start with *Generate* button.
-    
-    ![](PuttyKeygenerator_001V.png)
-    
+
+![](PuttyKeygenerator_001V.png)
+
 -   Generate some randomness.
-    
-    ![](PuttyKeygenerator_002V.png)
-    
+
+![](PuttyKeygenerator_002V.png)
+
 -   Wait.
-    
-    ![](PuttyKeygenerator_003V.png)
-    
--   Enter a *comment* for your key using formatÂ 
-    'username@organization.example.com'.
+
+![](PuttyKeygenerator_003V.png)
+
+-   Enter a *comment* for your key using format 'username@organization.example.com'.
     Enter key passphrase.
     Confirm key passphrase.
-    Save your new private key `in "*.ppk" `format with *Save private
-    key* button.
-    
-    ![](PuttyKeygenerator_004V.png)
-    
+    Save your new private key `in "*.ppk" `format with *Save private key* button.
+
+![](PuttyKeygenerator_004V.png)
+
 -   Save the public key with *Save public key* button.
-    You can copy public key out of the â€Public key for pasting into
-    authorized_keys fileâ€™ box.
-    
-    ![](PuttyKeygenerator_005V.png)
-    
--   Export private key in OpenSSH format "id_rsa" using Conversion
-    -&gt; Export OpenSSH key
-    
-    ![](PuttyKeygenerator_006V.png)
-    
--   Now you can insert additional public key into authorized_keys file
-    for authentication with your own private key.
-    You must log in using ssh key received after registration. Then
-    proceed to [How to add your own
-    key](../ssh-keys.html).
-    
+    You can copy public key out of the â€Public key for pasting into authorized_keys fileâ€™ box.
+
+![](PuttyKeygenerator_005V.png)
+
+-   Export private key in OpenSSH format "id_rsa" using Conversion -&gt; Export OpenSSH key
+
+![](PuttyKeygenerator_006V.png)
 
+-   Now you can insert additional public key into authorized_keys file for authentication with your own private key.
+    You must log in using ssh key received after registration. Then proceed to [How to add your own key](../ssh-keys.html).
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md
index e6055adb4..05c455e9a 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md
@@ -1,14 +1,12 @@
-SSH keys 
+SSH keys
 ========
 
-  
-
- Key management
+Key management
 -------------------------------------------------------------------
 
-After logging in, you can see .ssh/ directory with SSH keys and
-authorized_keys file:
+After logging in, you can see .ssh/ directory with SSH keys and authorized_keys file:
 
+```bash
     $ cd /home/username/
     $ ls -la .ssh/
     total 24
@@ -18,38 +16,17 @@ authorized_keys file:
     -rw------- 1 username username 1675 May 21Â  2014 id_rsa
     -rw------- 1 username username 1460 May 21Â  2014 id_rsa.ppk
     -rw-r--r-- 1 username usernameÂ  392 May 21Â  2014 id_rsa.pub
+```
 
- Please note that private keys in
-.ssh directory are without passphrase and allow you to connect within
-the cluster.
+>Please note that private keys in .ssh directory are without passphrase and allow you to connect within the cluster.
 
 ### Access privileges on .ssh folder
 
--   `.ssh`    Â directory: 700 (drwx------)
-    
-    Â directory: 
-    700 (drwx------)
--   
-    Authorized_keys, known_hosts and public keyÂ (`.pub`Â file):Â `644 (-rw-r--r--)`Â 
-    
-    
-    known_hosts and
-     public keyÂ 
-    (`.pub`
-    
-    Â file):Â 
-    
-    `644 (-rw-r--r--)`
--    
-    ``
-     
-    Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)`
-    (`id_rsa/id_rsa.ppk`
-    ): 
-    `600 (-rw-------)`
-    
-    
+- .ssh directory: 700 (drwx------)
+- Authorized_keys, known_hosts and public keyÂ (.pubÂ file):Â 644 (-rw-r--r--)
+- Private key (id_rsa/id_rsa.ppk): 600 (-rw-------)
 
+```bash
     cd /home/username/
     chmod 700 .ssh/
     chmod 644 .ssh/authorized_keys
@@ -57,22 +34,18 @@ the cluster.
     chmod 644 .ssh/known_hosts
     chmod 600 .ssh/id_rsa
     chmod 600Â .ssh/id_rsa.ppk
+```
 
-Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)`
+Private key
 -----------
 
-The path to a private key is usually /home/username/.ssh/
+>The path to a private key is usually /home/username/.ssh/
 
-Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)` file in "id_rsa" or `"*.ppk" `format is used to
-authenticate with the servers. 
-Private key (`id_rsa/id_rsa.ppk` ): `600 (-rw-------)` is present locally
-on local side and used for example in SSH agent [Pageant (for Windows
-users)](putty/PageantV.png). The private key should
-always be kept in a safe place.
+Private key file in "id_rsa" or `"*.ppk" `format is used to authenticate with the servers. Private key is present locally on local side and used for example in SSH agent [Pageant (for Windows users)](putty/PageantV.png). The private key should always be kept in a safe place.
 
- An example of private key
-format:
+An example of private key format:
 
+```bash
     -----BEGIN RSA PRIVATE KEY-----
     MIIEpAIBAAKCAQEAqbo7jokygnBpG2wYa5NB45ns6+UKTNLMLHF0BO3zmRtKEElE
     aGqXfbYwvXlcuRb2d9/Y5dVpCZHV0kbY3NhtVOcEIe+1ROaiU9BEsUAhMNEvgiLV
@@ -100,47 +73,40 @@ format:
     OqDBtZIuFv9U1WAg0gzGwt/0Y9u2c8m0nXziUS6AePxy5sBHs7g9C9WeZRz/nCWK
     +cHIm7XOwBEzDKz5f9eBqRGipm0skDZNKl8X/5QMTT5K3Eci2n+lTw==
     -----END RSA PRIVATE KEY-----
+```
 
 Public key
 ----------
 
-Public key file in "*.pub" format is used to 
-verify a
-Â 
-digital signature. Public 
-key is present on the remote
-side and  allows access to
-the owner of the matching private key.
+Public key file in "*.pub" format is used to verify a digital signature. Public key is present on the remote side and  allows access to the owner of the matching private key.
 
- An example of public key
-format:
+An example of public key format:
 
-    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCpujuOiTKCcGkbbBhrk0Hjmezr5QpM0swscXQE7fOZG0oQSURoapd9tjC9eVy5FvZ339jl1WkJkdXSRtjc2G1U5wQh77VE5qJT0ESxQCEw0S+CItWBKqXhC9E7gFY+UyP5YBZcOneh6gGHyCVfK6H215vzKr3x+/WvWl5gZGtbf+zhX6o4RJDRdjZPutYJhEsg/qtMxcCtMjfm/dZTnXeafuebV8nug3RCBUflvRb1XUrJuiX28gsd4xfG/P6L/mNMR8s4kmJEZhlhxpj8Th0iIc+XciVtXuGWQrbddcVRLxAmvkYAPGnVVOQeNj69pqAR/GXaFAhvjYkseEowQao1 username@organization.example.com
+```bash
+ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCpujuOiTKCcGkbbBhrk0Hjmezr5QpM0swscXQE7fOZG0oQSURoapd9tjC9eVy5FvZ339jl1WkJkdXSRtjc2G1U5wQh77VE5qJT0ESxQCEw0S+CItWBKqXhC9E7gFY+UyP5YBZcOneh6gGHyCVfK6H215vzKr3x+/WvWl5gZGtbf+zhX6o4RJDRdjZPutYJhEsg/qtMxcCtMjfm/dZTnXeafuebV8nug3RCBUflvRb1XUrJuiX28gsd4xfG/P6L/mNMR8s4kmJEZhlhxpj8Th0iIc+XciVtXuGWQrbddcVRLxAmvkYAPGnVVOQeNj69pqAR/GXaFAhvjYkseEowQao1 username@organization.example.com
+```
 
 ### How to add your own key
 
 First, generate a new keypair of your public and private key:
 
+```bash
     local $ ssh-keygen -C 'username@organization.example.com' -f additional_key
+```
 
-Please, enter **strong** **passphrase** for securing your private key.
+>Please, enter **strong** **passphrase** for securing your private key.
 
-You can insert additional public key into authorized_keys file for
-authentication with your own private key. Additional records in
-authorized_keys file must be delimited by new line. Users are
-not advised to remove the default public key from authorized_keys file.
+You can insert additional public key into authorized_keys file for authentication with your own private key. Additional records in authorized_keys file must be delimited by new line. Users are not advised to remove the default public key from authorized_keys file.
 
 Example:
 
+```bash
     $ cat additional_key.pub > ~/.ssh/authorized_keys
+```
 
-In this example, we add an additional public key, stored in file
-additional_key.pub into the authorized_keys. Next time we log in, we
-will be able to use the private addtional_key key to log in.
+In this example, we add an additional public key, stored in file additional_key.pub into the authorized_keys. Next time we log in, we will be able to use the private addtional_key key to log in.
 
 ### How to remove your own key
 
-Removing your key from authorized_keys can be done simply by deleting
-the corresponding public key which can be identified by a comment at the
-end of line (eg. username@organization.example.com).
+Removing your key from authorized_keys can be done simply by deleting the corresponding public key which can be identified by a comment at the end of line (eg. username@organization.example.com).
 
diff --git a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/vpn-connection-fail-in-win-8.1.md b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/vpn-connection-fail-in-win-8.1.md
index 22f2e4bca..891702710 100644
--- a/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/vpn-connection-fail-in-win-8.1.md
+++ b/docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/vpn-connection-fail-in-win-8.1.md
@@ -1,22 +1,14 @@
 VPN - Connection fail in Win 8.1 
 ================================
 
-**Failed to initialize connection subsystem Win 8.1 - 02-10-15 MS patch
+**Failed to initialize connection subsystem Win 8.1 - 02-10-15 MS patch**
 
-AnyConnect users on Windows 8.1 will receive a "Failed to initialize
-connection subsystem" error after installing the Windows 8.1 02/10/15
-security patch. This OS defect introduced with the 02/10/15 patch update
-will also impact WIndows 7 users with IE11. Windows Server
-2008/2012 are also impacted by this defect, but neither is a supported
-OS for AnyConnect.
+AnyConnect users on Windows 8.1 will receive a "Failed to initialize connection subsystem" error after installing the Windows 8.1 02/10/15 security patch. This OS defect introduced with the 02/10/15 patch update will also impact WIndows 7 users with IE11. Windows Server 2008/2012 are also impacted by this defect, but neither is a supported OS for AnyConnect.
 
 **Workaround:**
 
 -   Close the Cisco AnyConnect Window and the taskbar mini-icon
--   Right click vpnui.exe in the 'Cisco AnyConnect Secure Mobility
-    Client' folder. (C:Program Files (x86)CiscoCisco AnyConnect
-    Secure Mobility
--   Client)
+-   Right click vpnui.exe in the 'Cisco AnyConnect Secure Mobility Client' folder. (C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client)
 -   Click on the 'Run compatibility troubleshooter' button
 -   Choose 'Try recommended settings'
 -   The wizard suggests Windows 8 compatibility.
diff --git a/docs.it4i/get-started-with-it4innovations/applying-for-resources.md b/docs.it4i/get-started-with-it4innovations/applying-for-resources.md
index 165ccc7ba..f29bdf17e 100644
--- a/docs.it4i/get-started-with-it4innovations/applying-for-resources.md
+++ b/docs.it4i/get-started-with-it4innovations/applying-for-resources.md
@@ -1,38 +1,15 @@
-Applying for Resources 
+Applying for Resources
 ======================
 
-  
+Computational resources may be allocated by any of the following [Computing resources allocation](http://www.it4i.cz/computing-resources-allocation/?lang=en) mechanisms.
 
-Computational resources may be allocated by any of the following
-[Computing resources
-allocation](http://www.it4i.cz/computing-resources-allocation/?lang=en)
-mechanisms.
+Academic researchers can apply for computational resources viaÂ  [Open Access Competitions](http://www.it4i.cz/open-access-competition/?lang=en&lang=en).
 
-Academic researchers can apply for computational resources viaÂ  [Open
-Access
-Competitions](http://www.it4i.cz/open-access-competition/?lang=en&lang=en).
+Anyone is welcomed to apply via the [Directors Discretion.](http://www.it4i.cz/obtaining-computational-resources-through-directors-discretion/?lang=en&lang=en)
 
-Anyone is welcomed to apply via the [Directors
-Discretion.](http://www.it4i.cz/obtaining-computational-resources-through-directors-discretion/?lang=en&lang=en)
+Foreign (mostly European) users can obtain computational resources via the [PRACE (DECI) program](http://www.prace-ri.eu/DECI-Projects).
 
-Foreign (mostly European) users can obtain computational resources via
-the [PRACE (DECI)
-program](http://www.prace-ri.eu/DECI-Projects).
-
-In all cases, IT4Innovationsâ€™ access mechanisms are aimed at
-distributing computational resources while taking into account the
-development and application of supercomputing methods and their benefits
-and usefulness for society. The applicants are expected to submit a
-proposal. In the proposal, the applicants **apply for a particular
-amount of core-hours** of computational resources. The requested
-core-hours should be substantiated by scientific excellence of the
-proposal, its computational maturity and expected impacts.
-Proposals do undergo a scientific, technical and economic
+In all cases, IT4Innovationsâ€™ access mechanisms are aimed at distributing computational resources while taking into account the development and application of supercomputing methods and their benefits and usefulness for society. The applicants are expected to submit a proposal. In the proposal, the applicants **apply for a particular amount of core-hours** of computational resources. The requested core-hours should be substantiated by scientific excellence of the
+proposal, its computational maturity and expected impacts. Proposals do undergo a scientific, technical and economic
 evaluation. The allocation decisions are based on this
-evaluation. More information at [Computing resources
-allocation](http://www.it4i.cz/computing-resources-allocation/?lang=en)
-and [Obtaining Login
-Credentials](obtaining-login-credentials.html) page.
-
-Â 
-
+evaluation. More information at [Computing resources allocation](http://www.it4i.cz/computing-resources-allocation/?lang=en) and [Obtaining Login Credentials](obtaining-login-credentials.html) page.
-- 
GitLab