Delete duplicate entry

docs/forcing.rst

@@ -1,23 +1,23 @@
 Forcing
 =======
 Data Override
--------
+-------------
 When running MOM6 with the Flexible Modelling System (FMS) coupler, forcing can be specified by a `data_table` file. This is particularly useful when running MOM6 with a data atmosphere, as paths to the relevent atmospheric forcing products (eg. JRA55-do or ERA5) can be provided here. Each item in the data table must be separated by a new line, and contains the following information:
 
 | ``gridname``: The component of the model this data applies to. eg. `atm` `ocn` `lnd` `ice`.
 | ``fieldname_code``: The field name according to the model component. eg. `salt`
-| ``fieldname_file``: The name of the field within the source file. 
+| ``fieldname_file``: The name of the field within the source file.
 | ``file_name``: Path to the source file.
 | ``interpol_method``: Interpolation method eg. `bilinear`
-| ``factor``: A scalar by which to multiply the field ahead of passing it onto the model. This is a quick way to do unit conversions for example. 
+| ``factor``: A scalar by which to multiply the field ahead of passing it onto the model. This is a quick way to do unit conversions for example.
+|
 
-| 
 The data table is commonly formatted by specifying each of the fields in the order listed above, with a new line for each entry.
 
 Example Format:
     "ATM", "t_bot",  "t2m", "./INPUT/2t_ERA5.nc", "bilinear", 1.0
 
-A `yaml` format is also possible if you prefer. This is outlined in the `FMS data override <https://github.com/NOAA-GFDL/FMS/tree/main/data_override>`_ github page, along with other details. 
+A `yaml` format is also possible if you prefer. This is outlined in the `FMS data override <https://github.com/NOAA-GFDL/FMS/tree/main/data_override>`_ github page, along with other details.
 
 Speficying a constant value:
     Rather than overriding with data from a file, one can also set a field to constant. To do this, pass empty strings to `fieldname_file` and `file_name`. The `factor` now corresponds to the override value. For example, the following sets the temperature at the bottom of the atmosphere to 290 Kelvin.
@@ -26,7 +26,7 @@ Speficying a constant value:
     "ATM", "t_bot",  "", "", "bilinear", 290.0
 
 Which units do I need?
-    For configurations using SIS2 and MOM, a list of available surface flux variables along with the expected units can be found in the `flux_exchange <https://github.com/NOAA-GFDL/FMScoupler/blob/f4782c2c033df086eeac29fbbefb4a0bdac1649f/full/flux_exchange.F90>`_ file. 
+    For configurations using SIS2 and MOM, a list of available surface flux variables along with the expected units can be found in the `flux_exchange <https://github.com/NOAA-GFDL/FMScoupler/blob/f4782c2c033df086eeac29fbbefb4a0bdac1649f/full/flux_exchange.F90>`_ file.
 
 
 .. toctree::

docs/zotero.bib

@@ -2775,17 +2775,6 @@ @article{Bodner2023
 	pages={323-–339}
 }
 
-@incollection{Niiler1977,
-	author={P. P. Niiler and E. B. Kraus},
-	title={One-dimensional models of the upper ocean},
-	booktitle={Modeling and Prediction of the Upper Layers of the Ocean},
-	editor={E. B. Kraus},
-	publisher={Pergamon},
-	address={New York},
-	pages={143-–172},
-	year={1977}
-}
-
 @article{Oberhuber1993,
 	title={Simulation of the Atlantic Circulation with a Coupled Sea Ice-Mixed Layer-Isopycnal General Circulation Model. Part I: Model Description},
 	volume={23},

src/parameterizations/vertical/MOM_bulk_mixed_layer.F90

@@ -4256,7 +4256,7 @@ end function EF4
 !!
 !!   This file contains the subroutine (bulkmixedlayer) that
 !! implements a Kraus-Turner-like bulk mixed layer, based on the work
-!! of various people, as described in the review paper by \cite Niiler1977,
+!! of various people, as described in the review paper by \cite niiler1977,
 !! with particular attention to the form proposed by \cite Oberhuber1993,
 !! with an extension to a refined bulk mixed layer as described in
 !! Hallberg (\cite muller2003). The physical processes portrayed in