fix document rst

eclare108213 · Mar 8, 2020 · d704ff8 · d704ff8
1 parent 4d5bb57
commit d704ff8
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/doc/source/developer_guide/dg_col_phys.rst b/doc/source/developer_guide/dg_col_phys.rst
@@ -95,17 +95,17 @@ Overall, columnphysics changes in the Icepack model should include the following
 
     call icepack_warnings_add(subname//' algorithm did not converge')
 
-    To formally set the abort flag, use::
+  To formally set the abort flag, use::
 
     call icepack_warnings_setabort(.true.,__FILE__,__LINE__)
 
-    See also :ref:`aborts` for more information about how the external calling program will write those message and check whether Icepack aborted.
+  See also :ref:`aborts` for more information about how the external calling program will write those message and check whether Icepack aborted.
 
   - Every interface call within the columnphysics should be followed by::
 
     if (icepack_warnings_aborted(subname)) return
 
-    to support errors backing up the call tree to the external program
+  to support errors backing up the call tree to the external program
 
   - Variables defined in icepack_kinds, icepack_tracers, icepack_parameters, and icepack_orbital should be accessed within Icepack by Fortran use statements.  It's also possible to access some of those variables thru methods that query for the value, but this tends to be a little more cumbersome, so Fortran use statements are recommended within columnphysics.  From the icepack driver or other external programs, the columnphysics variables should ALWAYS be access thru the interface methods and icepack_intfc (see also :ref:`calling`).