diff --git a/docs.it4i/software/debuggers/allinea-ddt.md b/docs.it4i/software/debuggers/allinea-ddt.md
index 42d3b3327ad0162f726e726750bdee8415e3e05d..5c837b23d27a615cb40491c4ea81ba670e670927 100644
--- a/docs.it4i/software/debuggers/allinea-ddt.md
+++ b/docs.it4i/software/debuggers/allinea-ddt.md
@@ -1,16 +1,16 @@
-# Allinea Forge (DDT,MAP)
+# Allinea Forge (DDT, MAP)
 
 Allinea Forge consist of two tools - debugger DDT and profiler MAP.
 
-Allinea DDT, is a commercial debugger primarily for debugging parallel MPI or OpenMP programs. It also has a support for GPU (CUDA) and Intel Xeon Phi accelerators. DDT provides all the standard debugging features (stack trace, breakpoints, watches, view variables, threads etc.) for every thread running as part of your program, or for every process - even if these processes are distributed across a cluster using an MPI implementation.
+Allinea DDT is a commercial debugger primarily for debugging parallel MPI or OpenMP programs. It also supports for GPU (CUDA) and Intel Xeon Phi accelerators. DDT provides all the standard debugging features (stack trace, breakpoints, watches, view variables, threads, etc.) for every thread running as a part of your program, or for every process - even if these processes are distributed across a cluster using an MPI implementation.
 
-Allinea MAP is a profiler for C/C++/Fortran HPC codes. It is designed for profiling parallel code, which uses pthreads, OpenMP or MPI.
+Allinea MAP is a profiler for C/C++/Fortran HPC codes. It is designed for profiling parallel code, which uses pthreads, OpenMP, or MPI.
 
 ## License and Limitations for Anselm Users
 
-On Anselm users can debug OpenMP or MPI code that runs up to 64 parallel processes. In case of debugging GPU or Xeon Phi accelerated codes the limit is 8 accelerators. These limitation means that:
+On Anselm users can debug OpenMP or MPI code that runs up to 64 parallel processes. In case of debugging GPU or Xeon Phi accelerated codes, the limit is 8 accelerators. This limitation means that:
 
-* 1 user can debug up 64 processes, or
+* 1 user can debug up to 64 processes, or
 * 32 users can debug 2 processes, etc.
 
 In case of debugging on accelerators:
@@ -22,7 +22,7 @@ In case of debugging on accelerators:
 
 ### Modules
 
-Load all necessary modules to compile the code. For example:
+Load all necessary modules to compile the code, for example:
 
 ```console
 $ ml intel
@@ -44,12 +44,12 @@ $ mpif90 -g -O0 -o test_debug test.f
 
 ### Compiler Flags
 
-Before debugging, you need to compile your code with theses flags:
+Before debugging, you need to compile your code with these flags:
 
 !!! note
-    \- **g** : Generates extra debugging information usable by GDB. -g3 includes even more debugging information. This option is available for GNU and INTEL C/C++ and Fortran compilers.
+    \- **g**: Generates extra debugging information usable by GDB. -**g3** includes even more debugging information. This option is available for GNU and Intel C/C++ and Fortran compilers.
 
-    - - **O0** : Suppress all optimizations.
+    \- **O0**: Suppresses all optimizations.
 
 ## Starting a Job With DDT
 
@@ -59,9 +59,9 @@ Be sure to log in with an X window forwarding enabled. This could mean using the
 $ ssh -X username@anselm.it4i.cz
 ```
 
-Other options is to access login node using VNC. See the detailed information on how to [use graphic user interface on Anselm][1].
+Another options is to access the login node using VNC. See the detailed information on how to [use graphic user interface on Anselm][1].
 
-From the login node an interactive session **with X windows forwarding** (-X option) can be started by following command:
+From the login node, an interactive session **with X windows forwarding** (-X option) can be started by the following command:
 
 ```console
 $ qsub -I -X -A NONE-0-0 -q qexp -lselect=1:ncpus=16:mpiprocs=16,walltime=01:00:00
@@ -73,11 +73,11 @@ Then launch the debugger with the ddt command followed by the name of the execut
 $ ddt test_debug
 ```
 
-A submission window that appears have a prefilled path to the executable to debug. You can select the number of MPI processors and/or OpenMP threads on which to run and press run. Command line arguments to a program can be entered to the "Arguments " box.
+A submission window appears with a prefilled path to the executable to debug. Select the number of MPI processors and/or OpenMP threads on which to run, then press run. Command line arguments to a program can be entered to the "Arguments " box.
 
 ![](../../img/ddt1.png)
 
-To start the debugging directly without the submission window, user can specify the debugging and execution parameters from the command line. For example the number of MPI processes is set by option "-np 4". Skipping the dialog is done by "-start" option. To see the list of the "ddt" command line parameters, run "ddt --help".
+To start the debugging directly without the submission window, the user can specify the debugging and execution parameters from the command line. For example, the number of MPI processes is set by the "-np 4" option. Skipping the dialog is done by the "-start" option. To see the list of the "ddt" command line parameters, run "ddt --help".
 
 ```console
 ddt -start -np 4 ./hello_debug_impi
@@ -85,7 +85,7 @@ ddt -start -np 4 ./hello_debug_impi
 
 ## Documentation
 
-Users can find original User Guide after loading the DDT module:
+Users can find the original User Guide after loading the DDT module:
 
 ```console
 $DDTPATH/doc/userguide.pdf