0206-Compilation-PETSc-Windows.md

@@ -60,7 +60,7 @@ Now switch to the petsc_source_dir directory. Type `bin/win32fe/win32fe.exe cl`
 [[pics/compile_petsc_4.png]]
 
 
-Now for win32fe.exe to be accessable from console type `export PATH="$PATH:\`pwd\`/bin/win32fe"`. Check that you can run win32fe from console
+Now for win32fe.exe to be accessable from console type ``export PATH="$PATH:`pwd`/bin/win32fe"``. Check that you can run win32fe from console
 
 
 [[pics/compile_petsc_5.png]]
@@ -76,13 +76,13 @@ Now we will run PETSc configure script. We will have to tell it where to find Mi
 Please note that there are also flags provided for compilers. First `-O2` flag tells compiler to optimize everything, then `-MD` tells which runtime library should be used. It is very important that runtime libraries match across all of your libraries, otherwise your final executable will not compile or running it will result in segmentation faults or heap corruption which will be really hard to resolve. Flag for runtime library provided here should match with flag in your final application as well as flag in INMOST library. The `-wd4996` flag suppress specific compiler warning from output.
 
 
-Be patient since configuration script takes quite a time. Once finished PETSc script will provide you with some information on build options.
+Be patient since configuration script takes quite a time. Once finished, PETSc script will provide you with some information on build options.
 
 
 [[pics/compile_petsc_6.png]]
 
 
-Copy and enter make command with PETSC_ARCH and PETSC_DIR as script output suggests you. You have to wait quite a while again while PETSc library is being built. Once finished it will suggest you to run tests.
+Copy and enter make command with PETSC_ARCH and PETSC_DIR as script output suggests you. You have to wait quite a while again while PETSc library is being built. Once finished, it will suggest you to run tests.
 
 
 [[pics/compile_petsc_7.png]]