diff --git a/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/outgoing-connections.md b/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/outgoing-connections.md
index c127c9b0b956fffa494d5f0d769b360a2733c01c..658374a27617d7a4ec6276e61155815fd4ca76f2 100644
--- a/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/outgoing-connections.md
+++ b/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/outgoing-connections.md
@@ -12,7 +12,8 @@ Outgoing connections, from Anselm Cluster login nodes to the outside world, are
 |443|https|
 |9418|git|
 
->Please use **ssh port forwarding** and proxy servers to connect from Anselm to all other remote ports.
+!!! Note "Note"
+	Please use **ssh port forwarding** and proxy servers to connect from Anselm to all other remote ports.
 
 Outgoing connections, from Anselm Cluster compute nodes are restricted to the internal network. Direct connections form compute nodes to outside world are cut.
 
@@ -21,7 +22,8 @@ Port forwarding
 
 ### Port forwarding from login nodes
 
->Port forwarding allows an application running on Anselm to connect to arbitrary remote host and port.
+!!! Note "Note"
+	Port forwarding allows an application running on Anselm to connect to arbitrary remote host and port.
 
 It works by tunneling the connection from Anselm back to users workstation and forwarding from the workstation to the remote host.
 
@@ -62,7 +64,8 @@ In this example, we assume that port forwarding from login1:6000 to remote.host.
 
 Port forwarding is static, each single port is mapped to a particular port on remote host. Connection to other remote host, requires new forward.
 
->Applications with inbuilt proxy support, experience unlimited access to remote hosts, via single proxy server.
+!!! Note "Note"
+	Applications with inbuilt proxy support, experience unlimited access to remote hosts, via single proxy server.
 
 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:
 
@@ -72,11 +75,10 @@ local $ ssh -D 1080 localhost
 
 On Windows, install and run the free, open source [Sock Puppet](http://sockspuppet.com/)![external](../../img/external.png) server.
 
-Once the proxy server is running, establish ssh port forwarding from Anselm to the proxy server, port 1080, exactly as [described above](outgoing-connections.html#port-forwarding-from-login-nodes).
+Once the proxy server is running, establish ssh port forwarding from Anselm to the proxy server, port 1080, exactly as [described above](outgoing-connections/#port-forwarding-from-login-nodes).
 
 ```bash
 local $ 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](outgoing-connections.html#port-forwarding-from-compute-nodes) as well .
-
+Now, configure the applications proxy settings to **localhost:6000**. Use port forwarding  to access the [proxy server from compute nodes](outgoing-connections/#port-forwarding-from-compute-nodes) as well .
\ No newline at end of file
diff --git a/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access.md b/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access.md
index 4ceaee780818a6023d43ea5a0f3ee431dfa926ee..266590b71dd211f6b40d569aaa925f8d767fd404 100644
--- a/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access.md
+++ b/docs.it4i/anselm-cluster-documentation/accessing-the-cluster/shell-and-data-access.md
@@ -11,11 +11,13 @@ The Anselm cluster is accessed by SSH protocol via login nodes login1 and login2
 |login1.anselm.it4i.cz|22|ssh|login1|
 |login2.anselm.it4i.cz|22|ssh|login2|
 
-The authentication is by the [private key](../../../get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.html)
+The authentication is by the [private key](../../../get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys/)
+
+!!! Note "Note"
+	Please verify SSH fingerprints during the first logon. They are identical on all login nodes:
 
->Please verify SSH fingerprints during the first logon. They are identical on all login nodes:
-29:b3:f4:64:b0:73:f5:6f:a7:85:0f:e0:0d:be:76:bf (DSA)
-d4:6f:5c:18:f4:3f:70:ef:bc:fc:cc:2b:fd:13:36:b7 (RSA)
+	29:b3:f4:64:b0:73:f5:6f:a7:85:0f:e0:0d:be:76:bf (DSA)
+	d4:6f:5c:18:f4:3f:70:ef:bc:fc:cc:2b:fd:13:36:b7 (RSA)
 
 Private key authentication:
 
@@ -31,7 +33,7 @@ If you see warning message "UNPROTECTED PRIVATE KEY FILE!", use this command to
 local $ chmod 600 /path/to/id_rsa
 ```
 
-On **Windows**, use [PuTTY ssh client](../../../get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/putty/putty.html).
+On **Windows**, use [PuTTY ssh client](../../../get-started-with-it4innovations/accessing-the-clusters/shell-access-and-data-transfer/putty/putty/).
 
 After logging in, you will see the command prompt:
 
diff --git a/docs.it4i/anselm-cluster-documentation/environment-and-modules.md b/docs.it4i/anselm-cluster-documentation/environment-and-modules.md
index 62a7da453c7dec182cd116777a0fdc81f3f88684..fc263ee7637dfeab012ee26765f08cced759000b 100644
--- a/docs.it4i/anselm-cluster-documentation/environment-and-modules.md
+++ b/docs.it4i/anselm-cluster-documentation/environment-and-modules.md
@@ -24,15 +24,17 @@ then
 fi
 ```
 
->Do not run commands outputing to standard output (echo, module list, etc) in .bashrc  for non-interactive SSH sessions. It breaks fundamental functionality (scp, PBS) of your account! Take care for SSH session interactivity for such commands as stated in the previous example.
+!!! Note "Note"
+	Do not run commands outputing to standard output (echo, module list, etc) in .bashrc  for non-interactive SSH sessions. It breaks fundamental functionality (scp, PBS) of your account! Take care for SSH session interactivity for such commands as stated in the previous example.
 
 ### Application Modules
 
 In order to configure your shell for  running particular application on Anselm we use Module package interface.
 
->The modules set up the application paths, library paths and environment variables for running particular application.
+!!! Note "Note"
+	The modules set up the application paths, library paths and environment variables for running particular application.
 
->We have also second modules repository. This modules repository is created using tool called EasyBuild. On Salomon cluster, all modules will be build by this tool. If you want to use software from this modules repository, please follow instructions in section [Application Modules Path Expansion](environment-and-modules/#EasyBuild).
+    We have also second modules repository. This modules repository is created using tool called EasyBuild. On Salomon cluster, all modules will be build by this tool. If you want to use software from this modules repository, please follow instructions in section [Application Modules Path Expansion](environment-and-modules/#EasyBuild).
 
 The modules may be loaded, unloaded and switched, according to momentary needs.
 
diff --git a/docs.it4i/anselm-cluster-documentation/network.md b/docs.it4i/anselm-cluster-documentation/network.md
index 11bbcbb5c05f8f395b951b7cb50985a7a0b946c1..498ba52e697535a7dcd7abac853e7be08186b790 100644
--- a/docs.it4i/anselm-cluster-documentation/network.md
+++ b/docs.it4i/anselm-cluster-documentation/network.md
@@ -9,7 +9,8 @@ All compute and login nodes of Anselm are interconnected by a high-bandwidth, lo
 
 The compute nodes may be accessed via the Infiniband network using ib0 network interface, in address range 10.2.1.1-209. The MPI may be used to establish native Infiniband connection among the nodes.
 
->The network provides **2170MB/s** transfer rates via the TCP connection (single stream) and up to **3600MB/s** via native Infiniband protocol.
+!!! Note "Note"
+	The network provides **2170MB/s** transfer rates via the TCP connection (single stream) and up to **3600MB/s** via native Infiniband protocol.
 
 The Fat tree topology ensures that peak transfer rates are achieved between any two nodes, independent of network traffic exchanged among other nodes concurrently.