diff --git a/met/docs/Users_Guide/mode.rst b/met/docs/Users_Guide/mode.rst
index 9e0cc3e601..4715cad60c 100644
--- a/met/docs/Users_Guide/mode.rst
+++ b/met/docs/Users_Guide/mode.rst
@@ -108,7 +108,11 @@ Once MODE has been run, summary statistics are written to an output file. These
 Multi-Variate MODE
 ------------------
 
-Traditionally, MODE defines objects by smoothing and thresholding data from a single input field. MET version 10.1.0 extends MODE by adding the option to define objects using multiple input fields. As described in :numref:`MODE-configuration-file`, the **field** entry in the forecast and observation dictionaries define the input data to be processed. If **field** is defined as a dictionary, the tradition method for running MODE is invokes, where objects are defined using a single input field. If **field** is defined as an array of dictionaries, each specifying a different input field, then the multi-variate MODE logic is invoked. The object definition criteria can be specified separately within in field array entry to define objects for that field. The **multivar_logic** string defines the boolean logic for combining objects together from each of the inputs. The boolean logic uses integers from 1 to N, the number of input fields, to refer to the N-th field. Note that the multi-variate MODE forecast and observation object definition logic does not need to match. The result of the boolean logic is the creation of forecast and observation *super* objects, which are written to NetCDF output files. Users can then configure and run traditional MODE to compare the forecast super object to the observed super object.
+Traditionally, MODE defines objects by smoothing and thresholding data from a single input field. MET version 10.1.0 extends MODE by adding the option to define objects using multiple input fields.
+
+As described in :numref:`MODE-configuration-file`, the **field** entry in the forecast and observation dictionaries define the input data to be processed. If **field** is defined as a dictionary, the traditional method for running MODE is invoked, where objects are defined using a single input field. If **field** is defined as an array of dictionaries, each specifying a different input field, then the multi-variate MODE logic is invoked. Traditional MODE is run once for each input field to define objects for that field. Note that the object definition criteria can be defined separately for each field array entry. The objects from each input field are combined into a *super* object for both the forecast and observation data.
+
+The **multivar_logic** configuration entry, described in :numref:`MODE-configuration-file`, defines the boolean logic for combining objects from multiple fields into a *super* object. Note that the multi-variate MODE forecast and observation input fields and combination logic do not need to match. The resulting forecast and observation *super* objects are written to NetCDF output files. Users can then configure and run traditional MODE to compare the forecast super object to the observed super object.
 
 Practical information
 =====================