linter!

Author: rem1776

diag_manager/diag_manager.F90

@@ -21,8 +21,8 @@
 !!   on distributed systems. It is geared toward the writing of data in netCDF
 !!   format. The diag_manager differs from the fms2_io module in that it reads in
 !!   a diag_table describing which fields are expected in the output file, and also
-!!   buffers the sent in data prior to writing. This allows users to send in data for a field multiple times for a timestep
-!!   and output the average,max/min, etc. based on the 'reduction' method specified in the table.
+!!   buffers the sent in data prior to writing. This allows users to send in data for a field multiple times for a
+!!   timestep and output the average,max/min, etc. based on the 'reduction' method specified in the table.
 !!   It also allows for setting custom frequencies for output and file creation, for example outputting every 2 hours
 !!   while creating a new file every 6 hours.
 !!

diag_manager/fms_diag_axis_object.F90

@@ -563,7 +563,7 @@ end subroutine write_axis_data
   !! The time_of_day_<N> axis will have the midpoint of the sampled segment and the time_of_day_edges_<N> will have
   !! the bounds. This will be written out in hours of a day, so edges will always start at 0 and end at 24, and
   !! minutes will be represented as decimals.
-  !! 
+  !!
   !! For example, if n_diurnal_samples = 3, the time_of_day_03 axis will have the values [4, 12, 20], representing the
   !! time at the midpoint (4:00 am, 12:00 pm, 8:00 pm) for each of the 3 samples and the time_of_day_edges_03 axis
   !! will have the values [0, 8, 16, 24], representing the start/end times of each sample (12:00 am, 8:00 am, 4:00 pm,