EAMxx: more md linting fixes to the docs

components/eamxx/docs/user/model_input.md

@@ -235,10 +235,10 @@ for "float", only digits are allowed, possibly with a negative sign in front and
 only the strings "true" and "false" are allowed (case insensitive). There are two additional types supported:
 "file" and "array(T)", where "T" is any of the other supported types (but not another array):
 
- - "file" is used to inform CIME of the input files that have to be download from E3SM data servers, like initial conditions files,
+- "file" is used to inform CIME of the input files that have to be download from E3SM data servers, like initial conditions files,
 or certain lookup tables.
- - "array(T)" allows to specify a list of items (of the same type), which will be parsed inside EAMxx as
-   a `std::vector<T>`.
+- "array(T)" allows to specify a list of items (of the same type), which will be parsed inside EAMxx as
+  a `std::vector<T>`.
 
 For type "string" and "array(T)", it is also possible to _append_ to the currently stored value
 

components/eamxx/docs/user/model_output.md

@@ -9,7 +9,7 @@ into the RUNDIR/data folder. During this process, the files will be parsed, and
 variable will be resolved accordingly. Therefore, it is not advised to put the original YAML files
 in RUNDIR/data, since upon `buildnml` execution, all the CIME vars will no longer be present in the
 YAML file (replaced by their values), making it harder to tweak it, and even harder to share with
-other users/cases. Another consequence of this is that, much like `scream_input.yaml', the user should
+other users/cases. Another consequence of this is that, much like `scream_input.yaml`, the user should
 not modify the generated YAML files in RUNDIR/data, since any modification will be lost on the next
 run of `buildnml` (e.g., during `case.submit`).
 
@@ -206,6 +206,3 @@ file and the type of the parameter value).
   - `force_new_file` (`Restart` sublist, boolean): this parameter allows to start a fresh new output file
     upon restarts. By default, is is set to `false`, so that EAMxx will attempt to resume filling the
     last produced output file (if any, and if it can accommodate more snapshots).
-
-
-