diff --git a/docs.it4i/anselm-cluster-documentation/software/intel-xeon-phi.md b/docs.it4i/anselm-cluster-documentation/software/intel-xeon-phi.md
index baa0e6b531398be43761ac5198d430ea1f032d5e..6937a4453e27aa9cc8b10b5594d7d2c48a72b03a 100644
--- a/docs.it4i/anselm-cluster-documentation/software/intel-xeon-phi.md
+++ b/docs.it4i/anselm-cluster-documentation/software/intel-xeon-phi.md
@@ -632,7 +632,7 @@ The output should be similar to:
There are two ways how to execute an MPI code on a single coprocessor: 1.) lunch the program using "**mpirun**" from the
coprocessor; or 2.) lunch the task using "**mpiexec.hydra**" from a host.
-#### Execution on coprocessor
+#### Execution on Coprocessor
Similarly to execution of OpenMP programs in native mode, since the environmental module are not supported on MIC, user has to setup paths to Intel MPI libraries and binaries manually. One time setup can be done by creating a "**.profile**" file in user's home directory. This file sets up the environment on the MIC automatically once user access to the accelerator through the SSH.
@@ -681,7 +681,7 @@ The output should be similar to:
Hello world from process 0 of 4 on host cn207-mic0
```
-#### Execution on host
+#### Execution on Host
If the MPI program is launched from host instead of the coprocessor, the environmental variables are not set using the ".profile" file. Therefore user has to specify library paths from the command line when calling "mpiexec".
@@ -726,7 +726,7 @@ A simple test to see if the file is present is to execute:
/bin/pmi_proxy
```
-#### Execution on host - MPI processes distributed over multiple accelerators on multiple nodes**
+#### Execution on Host - MPI Processes Distributed Over Multiple Accelerators on Multiple Nodes**
To get access to multiple nodes with MIC accelerator, user has to use PBS to allocate the resources. To start interactive session, that allocates 2 compute nodes = 2 MIC accelerators run qsub command with following parameters:
@@ -886,7 +886,7 @@ A possible output of the MPI "hello-world" example executed on two hosts and two
!!! note
At this point the MPI communication between MIC accelerators on different nodes uses 1Gb Ethernet only.
-### Using the PBS automatically generated node-files
+### Using the PBS Automatically Generated Node-Files
PBS also generates a set of node-files that can be used instead of manually creating a new one every time. Three node-files are genereated:
diff --git a/docs.it4i/anselm-cluster-documentation/software/isv_licenses.md b/docs.it4i/anselm-cluster-documentation/software/isv_licenses.md
index e728270c2a8d8b26407e47519a3ca456e254972b..56270b51feca30fe2ec4f297da6cb0d6ee62d6e7 100644
--- a/docs.it4i/anselm-cluster-documentation/software/isv_licenses.md
+++ b/docs.it4i/anselm-cluster-documentation/software/isv_licenses.md
@@ -69,7 +69,7 @@ Names of applications (APP):
To get the FEATUREs of a license take a look into the corresponding state file ([see above](isv_licenses/#Licence)), or use:
-### Application and List of provided features
+### Application and List of Provided Features
* **ansys** $ grep -v "#" /apps/user/licenses/ansys_features_state.txt | cut -f1 -d' '
* **comsol** $ grep -v "#" /apps/user/licenses/comsol_features_state.txt | cut -f1 -d' '
diff --git a/docs.it4i/anselm-cluster-documentation/software/kvirtualization.md b/docs.it4i/anselm-cluster-documentation/software/kvirtualization.md
index a5e8238c7d39dc20bf542a547d583cee7df867b2..b838944b0b6c1914a55a900ef306a61e2561f340 100644
--- a/docs.it4i/anselm-cluster-documentation/software/kvirtualization.md
+++ b/docs.it4i/anselm-cluster-documentation/software/kvirtualization.md
@@ -279,7 +279,7 @@ Optimized network setup with sharing and port forwarding
### Advanced Networking
-#### Internet access
+#### Internet Access
Sometime your virtual machine needs access to internet (install software, updates, software activation, etc). We suggest solution using Virtual Distributed Ethernet (VDE) enabled QEMU with SLIRP running on login node tunneled to compute node. Be aware, this setup has very low performance, the worst performance of all described solutions.
@@ -321,7 +321,7 @@ Optimized setup
$ qemu-system-x86_64 ... -device virtio-net-pci,netdev=net0 -netdev vde,id=net0,sock=/tmp/sw0
```
-#### TAP interconnect
+#### TAP Interconnect
Both user and vde network back-end have low performance. For fast interconnect (10 Gbit/s and more) of compute node (host) and virtual machine (guest) we suggest using Linux kernel TAP device.
diff --git a/docs.it4i/salomon/introduction.md b/docs.it4i/salomon/introduction.md
index e9c133dbc70500c0791101aa67d492176e71c4e4..020f7f27c33d76341caa390302a01f0b66a16953 100644
--- a/docs.it4i/salomon/introduction.md
+++ b/docs.it4i/salomon/introduction.md
@@ -4,7 +4,7 @@ Welcome to Salomon supercomputer cluster. The Salomon cluster consists of 1008 c
The cluster runs [CentOS Linux](http://www.bull.com/bullx-logiciels/systeme-exploitation.html) operating system, which is compatible with the RedHat [Linux family.](http://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg)
-## Water-cooled Compute Nodes With MIC Accelerator
+## Water-Cooled Compute Nodes With MIC Accelerator
diff --git a/docs.it4i/salomon/prace.md b/docs.it4i/salomon/prace.md
index 8406726ba38f1ccf662f4e7f654f66107b2442b2..86749dfb438d7e15f4821b923b8997febee99013 100644
--- a/docs.it4i/salomon/prace.md
+++ b/docs.it4i/salomon/prace.md
@@ -48,7 +48,7 @@ To check whether your proxy certificate is still valid (by default it's valid 12
To access Salomon cluster, two login nodes running GSI SSH service are available. The service is available from public Internet as well as from the internal PRACE network (accessible only from other PRACE partners).
-#### Access from PRACE network:
+#### Access From PRACE Network:
It is recommended to use the single DNS name salomon-prace.it4i.cz which is distributed between the two login nodes. If needed, user can login directly to one of the login nodes. The addresses are:
@@ -70,7 +70,7 @@ When logging from other PRACE system, the prace_service script can be used:
$ gsissh `prace_service -i -s salomon`
```
-#### Access from public Internet:
+#### Access From Public Internet:
It is recommended to use the single DNS name salomon.it4i.cz which is distributed between the two login nodes. If needed, user can login directly to one of the login nodes. The addresses are:
@@ -127,7 +127,7 @@ Apart from the standard mechanisms, for PRACE users to transfer data to/from Sal
There's one control server and three backend servers for striping and/or backup in case one of them would fail.
-### Access from PRACE network
+### Access From PRACE Network
| Login address | Port | Node role |
| ----------------------------- | ---- | --------------------------- |
@@ -160,7 +160,7 @@ Or by using prace_service script:
$ globus-url-copy gsiftp://`prace_service -i -f salomon`/home/prace/_YOUR_ACCOUNT_ON_SALOMON_/_PATH_TO_YOUR_FILE_ file://_LOCAL_PATH_TO_YOUR_FILE_
```
-### Access from public Internet
+### Access From Public Internet
| Login address | Port | Node role |
| ----------------------- | ---- | --------------------------- |
diff --git a/docs.it4i/salomon/software/intel-xeon-phi.md b/docs.it4i/salomon/software/intel-xeon-phi.md
index 634cb913c30f56f10b3a6d864d9d28e16f50deee..26c87cb2aab21e606d205161f2a3b62bf4058d2c 100644
--- a/docs.it4i/salomon/software/intel-xeon-phi.md
+++ b/docs.it4i/salomon/software/intel-xeon-phi.md
@@ -631,7 +631,7 @@ The output should be similar to:
There are two ways how to execute an MPI code on a single coprocessor: 1.) lunch the program using "**mpirun**" from the
coprocessor; or 2.) lunch the task using "**mpiexec.hydra**" from a host.
-#### Execution on coprocessor
+#### Execution on Coprocessor
Similarly to execution of OpenMP programs in native mode, since the environmental module are not supported on MIC, user has to setup paths to Intel MPI libraries and binaries manually. One time setup can be done by creating a "**.profile**" file in user's home directory. This file sets up the environment on the MIC automatically once user access to the accelerator through the SSH.
@@ -680,7 +680,7 @@ The output should be similar to:
Hello world from process 0 of 4 on host cn207-mic0
```
-#### Execution on host
+#### Execution on Host
If the MPI program is launched from host instead of the coprocessor, the environmental variables are not set using the ".profile" file. Therefore user has to specify library paths from the command line when calling "mpiexec".
@@ -725,7 +725,7 @@ A simple test to see if the file is present is to execute:
/bin/pmi_proxy
```
-#### Execution on host - MPI processes distributed over multiple accelerators on multiple nodes
+#### Execution on Host - MPI Processes Distributed Over Multiple Accelerators on Multiple Nodes
To get access to multiple nodes with MIC accelerator, user has to use PBS to allocate the resources. To start interactive session, that allocates 2 compute nodes = 2 MIC accelerators run qsub command with following parameters:
@@ -885,7 +885,7 @@ A possible output of the MPI "hello-world" example executed on two hosts and two
!!! note
At this point the MPI communication between MIC accelerators on different nodes uses 1Gb Ethernet only.
-#### Using the PBS automatically generated node-files
+#### Using the PBS Automatically Generated Node-Files
PBS also generates a set of node-files that can be used instead of manually creating a new one every time. Three node-files are genereated: