repair external and internal links

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/vnc.md

@@ -7,8 +7,8 @@ The recommended clients are [TightVNC](http://www.tightvnc.com)![external](../..
 
 Create VNC password
 -------------------
-
->Local VNC password should be set before the first login. Do use a strong password.
+!!! Note "Note"
+	Local VNC password should be set before the first login. Do use a strong password.
 
 ```bash
 [username@login2 ~]$ vncpasswd
@@ -18,9 +18,10 @@ Verify:
 
 Start vncserver
 ---------------
+!!! Note "Note"
+	To access VNC a local vncserver must be  started first and also a tunnel using SSH port forwarding must be established.
 
->To access VNC a local vncserver must be  started first and also a tunnel using SSH port forwarding must be established.
-[See below](vnc.md#linux-example-of-creating-a-tunnel) for the details on SSH tunnels. In this example we use port 61.
+    [See below](vnc.md#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.
 
@@ -63,7 +64,8 @@ username    10296  0.0  0.0 131772 21076 pts/29   SN   13:01   0:01 /
 
 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.
+!!! Note "Note"
+	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
 

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-system.md

@@ -3,7 +3,8 @@ 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)")![external](../../../img/external.png) that provides a basis for [graphical user interfaces](http://en.wikipedia.org/wiki/Graphical_user_interface "Graphical user interface")![external](../../../img/external.png) (GUIs) and rich input device capability for [networked computers](http://en.wikipedia.org/wiki/Computer_network "Computer network")![external](../../../img/external.png).
 
->The X display forwarding must be activated and the X server running on client side
+!!! Note "Note"
+	The X display forwarding must be activated and the X server running on client side
 
 ### X display
 
@@ -52,7 +53,8 @@ Read more on [http://www.math.umn.edu/systems_guide/putty_xwin32.html](http://ww
 
 ### Running GUI Enabled Applications
 
->Make sure that X forwarding is activated and the X server is running.
+!!! Note "Note"
+	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.
 

docs.it4i/get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md

@@ -38,8 +38,8 @@ After logging in, you can see .ssh/ directory with SSH keys and authorized_keys
 
 Private key
 -----------
-
->The path to a private key is usually /home/username/.ssh/
+!!! Note "Note"
+    The path to a private key is usually /home/username/.ssh/
 
 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). The private key should always be kept in a safe place.
 
@@ -94,7 +94,8 @@ First, generate a new keypair of your public and private key:
     local $ ssh-keygen -C 'username@organization.example.com' -f additional_key
 ```
 
->Please, enter **strong** **passphrase** for securing your private key.
+!!! Note "Note"
+	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.