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

@@ -803,19 +803,19 @@ initial conditions (IC). To do this the user must program the function
 primary physical variables on the mesh, that are
 $\{\varrho,\mathbf{m},e,\mathbf{B},C_c,n_s\}$ -- gas density,
 momentum,total energy density, magnetic field, tracer
-($c=0,{\tt\_C.tracer}-1$), species number densities
-($s=0,{\tt\_C.species}-1$). The parameter `_C.tracer` (`_C.species`)
+(c=0..`_C.tracer`-1), species number densities
+(s=0..`_C.species`-1). The parameter `_C.tracer` (`_C.species`)
 denotes the number of tracer variables (species). However, those primary
 variables which are irrelevant for the problem under study need not to
 be assigned. For example, in simulations with isothermal EOS the total
-energy density $e$ is irrelevant since no energy equation is solved. In
+energy density, e, is irrelevant since no energy equation is solved. In
 HD simulations, the assignment of the magnetic field is redundant, of
 course, and would lead to an error because arrays for the magnetic field
 components are not allocated in the HD case. Likewise, arrays for tracer
 and species, $C_c$ and $n_s$, are not declared unless the parameters
-`_C.tracer`$>0$ respective ${\tt\_C.species}>0$. If the TESTFIELDS
-infrastructure is used (`_C.testfields`$>0$) testfields fluctuation
-variables, $\mathbf{b}_t,\,t=0,{\tt\_C.testfields}-1$, are also
+`_C.tracer`>0 respective `_C.species`>0. If the TESTFIELDS
+infrastructure is used (`_C.testfields`>0) testfields fluctuation
+variables, $\mathbf{b}_t$, t=0..`_C.testfields`-1, are also
 considered as primary variables and must be assigned by the user. The
 parameter `_C.testfields` denotes the number of testfields.