3-NIRVANA-user-guide/3.2-User-interfaces.md

@@ -1607,7 +1607,7 @@ for obvious reasons of consistency.
 and are needed in the numerical procedure.*
 
 An analytic EOS is enabled by appropriate choice in the parameter
-interface `nirvana.par` under category `PHYSICS SPECIFICATIONS` (code
+interface `nirvana.par` under category PHYSICS SPECIFICATIONS (code
 paramter: `_C.eos`).
 
 #### Tabulated EOS
@@ -1745,7 +1745,7 @@ vicinity of the given testpoint should be resolved with the limitation
 \|`level`\|≤`_C.imr` where code paramter `_C.imr` is
 the maximum allowed initial mesh refinement level specified by the user
 in the parameter interface `nirvana.par` under the category
-`MESH REFINEMENT`. In practice, the user defines spatial domains in
+MESH REFINEMENT. In practice, the user defines spatial domains in
 `initDomainUser.c` via mathematical relations, checks whether the
 testpoint is contained and then returns the requested refinement level.
 The following code fragment illustrates the procedure for a spherical
@@ -1826,7 +1826,7 @@ value `level`>0 forces mesh refinement up to refinement
 level `level` with the limitation `level`≤`_C.amr`
 where code parameter `_C.amr` is the maximum allowed mesh refinement
 level specified by the user in the parameter interface `nirvana.par`
-under category `MESH REFINEMENT`. Like in the `initDomainUser.c`
+under category MESH REFINEMENT. Like in the `initDomainUser.c`
 interface the user can define spatial domains via mathematical
 relations, checks whether the testpoint is contained and then returns
 the requested refinement control parameter.