Changes per review

Author: WardBrian

src/reference-manual/transforms.qmd

@@ -33,19 +33,20 @@ However, observed behavior can be different from the exact arithmetic.
 Stan’s arithmetic is implemented using double-precision
 floating-point numbers, which may cause computation to behave
 differently than mathematics. For example, the lower bound constraint
-is defined with a logarithm constraint which mathematically excludes
+is defined above by an exponential inverse transform which mathematically excludes
 the lower bound, but if the closest floating-point number for the
 inverse transformed value is the boundary, then the value is
 rounded to the boundary. This may cause unexpected warnings or
 errors, if in other parts of the code the boundary value is
 invalid. For example, we may observe floating-point value 0 for
-a variance parameter that has been declared to be larger than 0.
+a variance parameter that has been declared with `lower=0`.
 In general, double-precision floating-point numbers cannot reliably store
 more than 16 digits of a number in decimal.
-See more about [Floating point Arithmetic in Stan user's guide](../stan-users-guide/floating-point.qmd).
+See more about [floating point arithmetic](../stan-users-guide/floating-point.qmd)
+in the *Stan User's Guide*.
 
-These issues can be exacerbated by the fact that CmdStan stores the output to
-CSV files with 8 digits accuracy by default. More digits can be requested by the user
+These issues are exacerbated by the fact that CmdStan stores the output to
+CSV files with 8 digits precision by default. More digits can be requested by the user
 at the cost of additional disk usage, as discussed in the
 [CmdStan Command-Line Interface Overview](../cmdstan-guide/command_line_options.qmd).