diff --git a/met/docs/Users_Guide/appendixA.rst b/met/docs/Users_Guide/appendixA.rst
index 8b92b3de91..666d98708c 100644
--- a/met/docs/Users_Guide/appendixA.rst
+++ b/met/docs/Users_Guide/appendixA.rst
@@ -412,34 +412,7 @@ Setting vld_thresh = 1.0 will ensure that FSS will only be computed at
 points where all NxN values contain valid data. Setting it to 0.5 only
 requires half of them.
 
-
-**Q. Grid-Stat - How do I use config file setup to read a NetCDF file?**
-
-A.
-Setting up the Grid-Stat config file to read a netcdf file
-generated by a MET tool:
-
-.. code-block:: none
-
-  		fcst = { field =
-		          [ 
-		           { name = "HGT_P500"; level = [ "(*,*)" ]; }
-			  ];
-		       }
-
-Do not use numbers, such as "(181,360)", please use "(\*,\*)" instead.
-NetCDF variables can have an arbitrary number of dimensions.
-For example, many variables in the NetCDF output WRF have 4 dimensions -
-time, vertical level, lat, and lon. That cryptic level string
-with \*'s in it tells MET which 2D slice of lat/lon data to process.
-For a WRF file "(3, 5, \*, \*)"
-would say get data from the 3rd time dimension and 5th vertical level.
-
-However the NetCDF files that the MET tools generate are much simpler,
-and only contain 2 dimensional variables. So using "(\*,\*)" suffices.
-
-**Q. Grid-Stat - What would be an example of verifying probabilities?
-Example 1**
+**Q. Grid-Stat - Is an example of verifying probabilities?**
 
 A.
 There is an example of verifying probabilities in the test scripts
@@ -476,47 +449,11 @@ The config file should look something like this:
 			       ];
 		       };
 
-Without seeing how it's encoded in the GRIB file, it is unclear how to
-handle “name” in the forecast section. The PROB flag is set to TRUE
-to tell grid_stat to process this as probability data. The cat_thresh
-is set to partition the probability values between 0 and 1.
-
-This case is evaluating a forecast probability of wind speed
-exceeding 34kts, and likely comparing it against the wind speed values.
-The observed cat_thresh is set to >=34 to be consistent with the
-forecast probability definition.
-
-**Q. Grid-Stat - What would be an example of verifying probabilities?
-Example 2**
-
-A.
-An example of verifying a probability of precipitation field is
-included in the test scripts distributed with the MET tarball. Please
-take a look at
-
-
-.. code-block:: none
-
-		${MET_BUILD_BASE}/scripts/test_grid_stat.sh
-
-The second call to grid_stat is used to evaluate probability of precip
-using this config file: 
-
-
-.. code-block:: none
-
-		${MET_BUILD_BASE}/scripts/config/GridStatConfig_POP_12
-
-Note in there the following:
-
-.. code-block:: none
-		    
-		"prob = TRUE;"  # tells MET to interpret this data as a probability field. 
-		"cat_thresh = [ >=0.0, >=0.1, >=0.2, >=0.3, >=0.4, >=0.5, >=0.6, >=0.7, >=0.8, >=0.9]; "
-
-Here the thresholds are used to fully partition the probability space
-from 0 to 1. Note that if the probability data contains values from
-0 to 100, MET automatically divides by 100 to rescale to the 0 to 1 range.
+The PROB flag is set to TRUE to tell grid_stat to process this as
+probability data. The cat_thresh is set to partition the probability
+values between 0 and 1. Note that if the probability data contains
+values from 0 to 100, MET automatically divides by 100 to rescale to
+the 0 to 1 range.
 
 **Q. What is an example of using Grid-Stat with regridding and masking
 turned on?**
@@ -578,19 +515,19 @@ gen_vx_mask tool and pass the NetCDF output of that tool to grid_stat.
 The advantage to gen_vx_mask is that it will make grid_stat run a
 bit faster. It can be used to construct much more complex masking areas.
 
-**Q. How do I use different masks in MET tools using MODE?**
+**Q. How do I use one mask for the forecast field and a different
+mask for the observation field??**
 
 A.
-You'd like to apply one mask to the forecast field and a *different*
-mask to the observation field. However, you can't define different
-masks for the forecast and observation fields. MODE only lets you
+You can't define different
+masks for the forecast and observation fields in MET tools. MET only lets you
 define a single mask (a masking grid or polyline) and then you choose
 whether you want to apply it to the FCST, OBS, or BOTH of them.
 
 Nonetheless, there is a way you can accomplish this logic using the
 gen_vx_mask tool. You run it once to pre-process the forecast field
 and a second time to pre-process the observation field. And then pass
-those output files to MODE.
+those output files to your desired MET tool.
 
 Below is an example using sample data that is included with the MET
 release tarball. To illustrate, this command will read 3-hour