diff --git a/met/docs/Users_Guide/appendixA.rst b/met/docs/Users_Guide/appendixA.rst
index e93da729c7..0d57632e66 100644
--- a/met/docs/Users_Guide/appendixA.rst
+++ b/met/docs/Users_Guide/appendixA.rst
@@ -32,7 +32,7 @@ lat/lon points.
 
 Here's an example of that, using data from the MET tarball:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/gen_vx_mask \
 		data/sample_fcst/2005080700/wrfprs_ruc13_12.tm00_G212 \
@@ -71,7 +71,7 @@ the following steps:
 Use the regrid_data_plane tool to regrid 2m temperature
 to a smaller domain centered on China:
 
-.. code-block:: ini
+.. code-block:: none
 				  
 		${MET_BUILD_BASE}/bin/regrid_data_plane \ 
 		gfs_2012040900_F012.grib \ 
@@ -82,7 +82,7 @@ to a smaller domain centered on China:
 2.
 Run plot_data_plane to plot with the default map background:
 
-.. code-block:: ini
+.. code-block:: none
 				
      ${MET_BUILD_BASE}/bin/plot_data_plane 
      china_tmp_2m.nc china_tmp_2m.ps \ 
@@ -91,7 +91,7 @@ Run plot_data_plane to plot with the default map background:
 3.
 Re-run but pointing only to the admin_China_data:
 
-.. code-block:: ini
+.. code-block:: none
 		
      ${MET_BUILD_BASE}/bin/plot_data_plane 
      china_tmp_2m.nc china_tmp_2m_admin.ps \ 
@@ -158,7 +158,7 @@ other than selecting the time index.
 
 Let's use plot_data_plane as an example:
 
-.. code-block:: ini
+.. code-block:: none
 		      
 		${MET_BUILD_BASE}/bin/plot_data_plane \ 
 		MERGE_20161201_20170228.nc \ 
@@ -173,7 +173,7 @@ time slice of the APCP data and plot it.
 A.
 Regarding the timing information in the NetCDF variable attributes...
 
-.. code-block:: ini
+.. code-block:: none
 		      
      APCP_24:init_time_ut = 1306886400 ;
 		      
@@ -185,14 +185,14 @@ can be used to convert back/forth between unix time and time strings:
 1.
 Convert unix time to ymd_hms date
 
-.. code-block:: ini
+.. code-block:: none
 		
     		date -ud '1970-01-01 UTC '1306886400' seconds' +%Y%m%d_%H%M%S 20110601_000000
 
 2.
 Convert ymd_hms to unix date
 
-.. code-block:: ini
+.. code-block:: none
 		      
 		date -ud ''2011-06-01' UTC '00:00:00'' +%s 1306886400
 		  
@@ -297,13 +297,13 @@ NetCDF doesn't like including that character in the NetCDF variable name.
 
 One easy way to strip them off is the "dos2unix" utility: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		dos2unix POLAND.poly
 
 Grab a sample GFS file: 
 
-.. code-block:: ini
+.. code-block:: none
 		      
 		wget 
 		http://www.ftp.ncep.noaa.gov/data/nccf/com/gfs/prod/gfs/2016102512/gfs.t12z.pgrb2.0p50.f000
@@ -311,20 +311,20 @@ Grab a sample GFS file:
 Use the MET regrid_data_plane tool to put some data on a
 lat/lon grid over Europe:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/regrid_data_plane gfs.t12z.pgrb2.0p50.f000 \
 		'latlon 100 100 25 0 0.5 0.5' gfs_euro.nc -field 'name="TMP"; level="Z2";'
 
 Run the MET gen_vx_mask tool to apply your polyline to the European domain:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/gen_vx_mask gfs_euro.nc POLAND.poly POLAND_mask.nc
 
 Run the MET plot_data_plane tool to display the resulting mask field:
 
-.. code-block:: ini
+.. code-block:: none
 		      
 		${MET_BUILD_BASE}/bin/plot_data_plane POLAND_mask.nc POLAND_mask.ps 'name="POLAND"; level="(*,*)";'
 
@@ -351,7 +351,7 @@ freezing with non-zero precip. We'll run gen_vx_mask twice...
 once to define the temperature mask and a second time to intersect
 that with the precip mask:
 
-.. code-block:: ini
+.. code-block:: none
 
 		gen_vx_mask fcst.grb fcst.grb tmp_mask.nc \ 
 		-type data \ 
@@ -443,7 +443,7 @@ of a monsoon season. This will result in 122 FSS values. These
 can be viewed as a time series, or the Stat-Analysis tool could
 be used to aggregate them together into a single FSS value, like this:
 
-.. code-block:: ini
+.. code-block:: none
 		     
 		stat_analysis -job aggregate -line_type NBRCNT \
 		-lookin out/grid_stat
@@ -457,7 +457,7 @@ A.
 Setting up the Grid-Stat config file to read a netcdf file
 generated by a MET tool:
 
-.. code-block:: ini
+.. code-block:: none
 
   		fcst = { field =
 		          [ 
@@ -483,13 +483,13 @@ A.
 There is an example of verifying probabilities in the test scripts
 included with the MET release. Take a look in: 
 
-.. code-block:: ini
+.. code-block:: none
 		   
 		${MET_BUILD_BASE}/scripts/config/GridStatConfig_POP_12
 
 The config file should look something like this...
 
-.. code-block:: ini
+.. code-block:: none
 
 		fcst = { 
 		        wind_thresh = [ NA ];
@@ -533,7 +533,7 @@ included in the test scripts distributed with the MET tarball. Please
 take a look at
 
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/scripts/test_grid_stat.sh
 
@@ -541,13 +541,13 @@ The second call to grid_stat is used to evaluate probability of precip
 using this config file: 
 
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/scripts/config/GridStatConfig_POP_12
 
 Note in there the following... 
 
-.. code-block:: ini
+.. code-block:: none
 		    
 		"prob = TRUE;"  # tells MET to interpret this data 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]; "
@@ -562,7 +562,7 @@ Turned On?**
 A.
 Run Grid-Stat using the following commands and the attached config file 
 
-.. code-block:: ini
+.. code-block:: none
 		   
 		mkdir out 
 		${MET_BUILD_BASE}/bin/grid_stat \ 
@@ -573,7 +573,7 @@ Run Grid-Stat using the following commands and the attached config file
 
 Note the following two sections of the Grid-Stat config file: 
 
-.. code-block:: ini
+.. code-block:: none
 		   
 		regrid = { 
 		          to_grid = OBS; 
@@ -590,7 +590,7 @@ grid or a grid specification string to regrid both the forecast and
 observation to a common grid. For example, to_grid = "G212"; will
 regrid both to NCEP Grid 212 before comparing them.
 
-.. code-block:: ini
+.. code-block:: none
 		   
 		mask = { grid = [ "FULL" ]; 	
 		poly = [ "MET_BASE/poly/CONUS.poly" ]; } 
@@ -601,7 +601,7 @@ as the CONUS masking area.
 To demonstrate that Grid-Stat worked as expected, run the following
 commands to plot its NetCDF matched pairs output file:
 
-.. code-block:: ini
+.. code-block:: none
 		   
 		${MET_BUILD_BASE}/bin/plot_data_plane \ 
 		out/grid_stat_120000L_20160220_120000V_pairs.nc \ 
@@ -635,7 +635,7 @@ release tarball to illustrate... using met. This will read 3-hour
 precip and 2-meter temperature, and resetts the precip at any grid
 point where the temperature is less than 290 K to a value of 0:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		{MET_BUILD_BASE}/bin/gen_vx_mask \ 
 		data/sample_fcst/2005080700/wrfprs_ruc13_12.tm00_G212 \ 
@@ -679,7 +679,7 @@ by a value of 0.
 To more easily demonstrate this, I changed to using "-value 10" and ran
 the output through plot_data_plane: 
 
-.. code-block:: ini
+.. code-block:: none
 		
         {MET_BUILD_BASE}/bin/plot_data_plane \ 
 
@@ -698,7 +698,7 @@ Pcp-Combine
 A.
 Problems configuring a good set of options for pcp_combine. Run the command in the following way:
 
-.. code-block:: ini
+.. code-block:: none
 
 		#!/bin/sh
 		/usr/local/met/bin/pcp_combine -add \
@@ -718,7 +718,7 @@ Run the MET pcp_combine tool to put the NAM data into 3-hourly accumulations.
 0-3 hour accumulation is already in the 03UTC file. Run this file
 through pcp_combine as a pass-through to put it into NetCDF format: 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		[MET_BUILD_BASE}/pcp_combine -add 03_file.grb 03 APCP_00_03.nc
 		3-6 hour accumulation. Subtract 0-6 and 0-3 accumulations: 
@@ -730,13 +730,13 @@ through pcp_combine as a pass-through to put it into NetCDF format:
 		
 12-15 hour accumulation. Just run as a pass-through again: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		[MET_BUILD_BASE}/pcp_combine -add 15_file.grb 03 APCP_12_15.nc
 
 15-18 hour accumulation. Subtract 12-18 and 12-15 accumulations: 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		[MET_BUILD_BASE}/pcp_combine -subtract 18_file.grb 06 15_file.grb 03 APCP_15_18.nc
 
@@ -755,7 +755,7 @@ A.
 The "-sum" command assumes the same initialization time. Use the "-add"
 option instead.
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/pcp_combine -add \ 
 		WRFPRS_1997-06-03_APCP_A12.nc 'name="APCP_12"; level="(*,*)";' \ 
@@ -775,7 +775,7 @@ the accumulation interval with a Config file string.
 
 Here are 3 commands you could use to plot these data files:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/plot_data_plane WRFPRS_1997-06-03_APCP_A12.nc \
 		WRFPRS_1997-06-03_APCP_A12.ps 'name="APCP_12"; level="(*,*)";' 
@@ -794,7 +794,7 @@ meanings: http://www.nco.ncep.noaa.gov/pmb/docs/on388/table5.html
 For example, take a look at the APCP in the GRIB files included in the
 MET tar ball:
 
-.. code-block:: ini
+.. code-block:: none
 
 		wgrib ${MET_BUILD_BASE}/data/sample_fcst/2005080700/wrfprs_ruc13_12.tm00_G212 | grep APCP
 		1:0:d=05080700:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0: \
@@ -809,7 +809,7 @@ between 9 and 12 hours.
 
 However, the GRIB data uses a time range indicator of 5, not 4.
 
-.. code-block:: ini
+.. code-block:: none
 
 		wgrib rmf_gra_2016040600.24 | grep APCP
 		291:28360360:d=16040600:APCP:kpds5=61:kpds6=1:kpds7=0: \
@@ -825,7 +825,7 @@ pcp_combine to look for a particular accumulation interval, give it a
 more complete description of the chosen field to use from each file.
 Here is an example:
 
-.. code-block:: ini
+.. code-block:: none
 
 		pcp_combine -add rmf_gra_2016040600.24 'name="APCP"; level="L0-24";' \
 		rmf_gra_2016040600_APCP_00_24.nc
@@ -854,7 +854,7 @@ Looking at the accumulation interval of the precipitation data in the WRF
 output files from UPP, use the "wgrib" utility to dump out that sort
 of information:
 
-.. code-block:: ini
+.. code-block:: none
 
 		wgrib wrfprs_d01.02 
 		wgrib wrfprs_d01.03 
@@ -876,7 +876,7 @@ Use the pcp_combine "-subtract" option instead of "-sum". Suppose the
 6 hours of precip between the 6hr and 12hr forecasts is wanted. Run the
 following:
 
-.. code-block:: ini
+.. code-block:: none
 
 		pcp_combine -subtract wrfprs_d01.12 12 \
 		wrfprs_d01.06 06 apcp_06_to_12.nc
@@ -903,7 +903,7 @@ pcp_combine as a pass-through to simply reformat from GRIB to NetCDF.
 Listed below is an example of passing a single record to the
 pcp_combine -add option to do the reformatting:
 
-.. code-block:: ini
+.. code-block:: none
 
 		$MET_BUILD/bin/pcp_combine -add forecast_F06.grb \
 		'name="APCP"; level="A6";' \
@@ -915,7 +915,7 @@ NetCDF output variable name. Presuming this file is then passed to
 another MET tool, the new variable name (CompositeReflectivity) will
 appear in the output of downstream tools:
 
-.. code-block:: ini
+.. code-block:: none
 
 		$MET_BUILD/bin/pcp_combine -add forecast.grb \
 		'name="REFC"; level="L0"; GRIB1_ptv=129; lead_time="120000";' \
@@ -928,7 +928,7 @@ To run a project faster, the “-pcprx” option may be used to narrow the
 search down to whatever regular expression you provide. Here are a two
 examples:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		# Only using Stage IV data (ST4)
 		${MET_BUILD_BASE}/bin/pcp_combine -sum 00000000_000000 06 \
@@ -947,7 +947,7 @@ A.
 Here is an **incorrect example** of running pcp_combine with sub-hourly
 accumulation intervals: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		# incorrect example:
 		pcp_combine -subtract forecast.grb 0055 \
@@ -965,7 +965,7 @@ hours/minutes/seconds. The incorrect example is using hours/minutes.
 
 Below is the **correct example**. Add the seconds to the end of the time strings, like this: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		# correct example:
 		pcp_combine -subtract forecast.grb 005500 \
@@ -976,7 +976,7 @@ Below is the **correct example**. Add the seconds to the end of the time strings
 A.
 Run wgrib on the data files and the output is listed below:
 
-.. code-block:: ini
+.. code-block:: none
 
 		279:503477484:d=15062313:APCP:kpds5=61:kpds6=1:kpds7=0:TR= 10:P1=3:P2=247:TimeU=0:sfc:1015min \
 		fcst:NAve=0 \
@@ -997,7 +997,7 @@ arguments need to be more specific to tell pcp_combine exactly what to do.
 
 Try the command:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/pcp_combine -subtract \ 
 		forecast.grb 'name="APCP"; level="L0"; lead_time="165500";' \ 
@@ -1050,7 +1050,7 @@ to generate the desired 24-hour accumulation.
 Here is an example. Run pcp_combine to compute 24-hour accumulations for
 GFS. In this example, process the 20150220 00Z initialization of GFS.
 
-.. code-block:: ini
+.. code-block:: none
 		
 		${MET_BUILD_BASE}/bin/pcp_combine \ 
 		-sum 20150220_00 06 20150221_00 24 \ 
@@ -1070,7 +1070,7 @@ forecast hours 0 and 24.
 The following command will compute the 24-hour accumulation between forecast
 hours 12 and 36:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/pcp_combine \ 
 		-sum 20150220_00 06 20150221_12 24 \ 
@@ -1084,7 +1084,7 @@ directory. But instead of using "-sum", another option would be the
 from the 6-hour APCP and add them up to 24. In the directory structure,
 the previous "-sum" job could be rewritten with "-add" like this:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/pcp_combine -add \ 
 		/d1/model_data/20150220/gfs_4_20150220_0000_018.grb2 06 \ 
@@ -1101,7 +1101,7 @@ output should be identical to the output of the "-sum" command.
 
 A.To run a project faster, -pcprx is an option.
 
-.. code-block:: ini
+.. code-block:: none
 		
 		${MET_BUILD_BASE}/bin/pcp_combine \
 		-sum 20160221_18 06 20160222_18 24 \
@@ -1113,7 +1113,7 @@ But this only matches 2-digit forecast hours.
 
 The "-add" command could be used instead of the “-sum” command:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		${MET_BUILD_BASE}/bin/pcp_combine -add \
 		model_out/temp/pgbq06.gfs.2016022118 06 \
@@ -1131,7 +1131,7 @@ by using a calling script.
 A.
 In this example, record 735 needs to be selected. 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		pcp_combine -add 20160101_i12_f015_HRRR_wrfnat.grb2 \ 
 		'name="APCP"; level="R735";' \
@@ -1149,7 +1149,7 @@ A.
 The gen_vx_mask tool is successfully writing a NetCDF file, but the
 pcp_combine tool errors out when trying to write a NetCDF file: 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		ERROR : write_netcdf() -> error with pcp_var->put()
 
@@ -1157,7 +1157,7 @@ The question is why? Let's check to see if the call to gen_vx_mask
 actually did create good output. Try running the following command
 from the top-level ${MET_BUILD_BASE} directory:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		bin/plot_data_plane \ 
 		out/gen_vx_mask/CONUS_poly.nc \ 
@@ -1167,7 +1167,7 @@ from the top-level ${MET_BUILD_BASE} directory:
 And then view that postscript output file, using something like "gv"
 for ghostview: 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		gv out/gen_vx_mask/CONUS_poly.ps
 
@@ -1188,14 +1188,14 @@ the "file_type" configuration option.
 
 The examples below use the plot_data_plane tool to plot the data. Set 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		"file_type = GRIB2;"
 
 To keep them named this way, add "file_type = GRIB2;" to all the
 MET configuration files (i.e. Grid-Stat, MODE, and so on) that you use:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		{MET_BASE}/bin/plot_data_plane \ 
 		test_2.5_prog.grib \ 
@@ -1211,13 +1211,13 @@ plot_data_plane tool to test it out.
 A.
 Making sure MET can read GRIB2 data. Plot the data from that GRIB2 file by running: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/plot_data_plane LTIA98_KWBR_201305180600.grb2 tmp_z2.ps 'name="TMP"; level="R2";
 
 "R2" tells MET to plot record number 2. Record numbers 1 and 2 both contain temperature data and 2-meters. Here's some wgrib2 output:
 
-.. code-block:: ini
+.. code-block:: none
 
 		1:0:d=2013051806:TMP:2 m above ground:anl:analysis/forecast error 2:3323062:d=2013051806:TMP:2 m above ground:anl:
 
@@ -1236,7 +1236,7 @@ U and V records and derive wind speed to use on the fly.
 In this example the RTMA file is named rtma.grb2 and the UPP file is
 named wrf.grb, please try running the following commands to plot wind speed:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/plot_data_plane wrf.grb wrf_wind.ps \
 		'name"WIND"; level="Z10";' -v 3 
@@ -1245,7 +1245,7 @@ named wrf.grb, please try running the following commands to plot wind speed:
 		
 In the first call, the log message should be similar to this: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		DEBUG 3: MetGrib1DataFile::data_plane_array() -> 
 		Attempt to derive winds from U and V components.
@@ -1284,7 +1284,7 @@ With met-5.2 and later versions, one option is to apply column string
 matching using the "-column_str" option to define the list of station
 ID's you would like to aggregate. That job would look something like this:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		stat_analysis -lookin path/to/mpr/directory \
 		-job aggregate_stat -line_type MPR -out_line_type CNT \ 
@@ -1309,7 +1309,7 @@ is for aggregating scores for the accumulated precipitation (APCP) field.
 
 Run the "aggregate" job type in stat_analysis to do this:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/stat_analysis -lookin directory/file*_nbrcnt.txt \
 		-job aggregate -line_type NBRCNT -by FCST_VAR,FCST_LEAD,FCST_THRESH,INTERP_MTHD,INTERP_PNTS -out_stat agg_nbrcnt.txt
@@ -1336,7 +1336,7 @@ define the probabilistic forecast thresholds, define the single observation
 threshold, and compute a PSTD output line. Using "-by FCST_VAR" tells it
 to run the job separately for each unique entry found in the FCST_VAR column.
 
-.. code-block:: ini
+.. code-block:: none
 		
 		${MET_BUILD_BASE}/bin/stat_analysis \ 
 		-lookin point_stat_model2_120000L_20160501_120000V.stat \ 
@@ -1356,7 +1356,7 @@ CNT lines (continuous statistics) where the forecast rate and observation
 rate are less than 0.05. This is an alternative way of tossing out those
 cases without having to modify the source code.
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/stat_analysis \ 
 		-lookin out/grid_stat/grid_stat_120000L_20050807_120000V.stat \ 
@@ -1388,7 +1388,7 @@ of say RMSE, with each of the forecast variables (UGRD,VGRD and WIND).
 Run the following job on the output from Grid-Stat generated when the
 "make test" command is run:
 
-.. code-block:: ini
+.. code-block:: none
 		
 		${MET_BUILD_BASE}/bin/stat_analysis -lookin out/grid_stat \ 
 		-job aggregate_stat -line_type SL1L2 -out_line_type CNT \ 
@@ -1423,7 +1423,7 @@ This will create a long list of values in the OBTYPE column. To avoid the
 long, OBTYPE column value, manually set the output using
 "-set_hdr OBTYPE ALL_TYPES". Or set its value to whatever is needed.
 
-.. code-block:: ini
+.. code-block:: none
 		
 		${MET_BUILD_BASE}/bin/stat_analysis \ 
 		-lookin diag_conv_anl.2015060100.stat \ 
@@ -1448,7 +1448,7 @@ In this case the tc_stat job looked at the 48 hour lead time for the HWRF
 and H3HW models. Without the “-by AMODEL” option, the output would be
 all grouped together. 
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/tc_stat \ 
 		-lookin d2014_vx_20141117_reset/al/tc_pairs/tc_pairs_H3WI_* \ 
@@ -1465,7 +1465,7 @@ are any more useful log messages.
 
 To get the most output, run something like this...
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/tc_stat \ 
 		-lookin path/to/tc_pairs/output \ 
@@ -1479,7 +1479,7 @@ and -rirw_thresh options. Set -rirw_window to something larger than 0
 to enable false alarms to be considered hits when they were "close enough"
 in time.
 
-.. code-block:: ini
+.. code-block:: none
 
 		{MET_BASE}/bin/tc_stat \ 
 		-lookin path/to/tc_pairs/output \ 
@@ -1490,7 +1490,7 @@ in time.
 To evaluate Rapid Weakening (RW) by setting "-rirw_thresh <=-30".
 To stratify your results by lead time, you could add "-by LEAD" option.
 
-.. code-block:: ini
+.. code-block:: none
 
 		{MET_BASE}/bin/tc_stat \ 
 		-lookin path/to/tc_pairs/output \ 
@@ -1510,7 +1510,7 @@ including passing in variables. This shell script listed below to run
 Grid-Stat, call Plot-Data-Plane to plot the resulting difference field,
 and call convert to reformat from PostScript to PNG.
 
-.. code-block:: ini
+.. code-block:: none
 
 		#!/bin/sh
 		for case in `echo "FCST OBS"`; do 
@@ -1533,7 +1533,7 @@ is an option for accessing that same TRMM data, following links from the
 MET website:
 http://www.dtcenter.org/met/users/downloads/observation_data.php
 
-.. code-block:: ini
+.. code-block:: none
 
 		# Pull binary 3-hourly TRMM data file 
 		wget 
@@ -1568,7 +1568,7 @@ of the configuration files for the MET tools may be used to do the
 regridding on the fly. For example, run Grid-Stat to compare to the model
 output to TRMM and say 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		"regrid = { field = FCST; 
 		...}"
@@ -1582,13 +1582,13 @@ A.
 Use the linux “convert” tool to convert a Plot-Data-Plane PostScript
 file to a png: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		convert -rotate 90 -background white plot_dbz.ps plot_dbz.png
 
 To convert a MODE PostScript to png
 
-.. code-block:: ini
+.. code-block:: none
 
 		convert mode_out.ps mode_out.png
 
@@ -1614,7 +1614,7 @@ plot_tcmpr.R Rscript. It makes a call to the tc_stat tool to the track
 data down to the desired subset, compute pairwise difference if needed,
 and then plot the result. 
 
-.. code-block:: ini
+.. code-block:: none
 
 		setenv MET_BUILD_BASE `pwd` 
 		Rscript scripts/Rscripts/plot_tcmpr.R \
@@ -1640,7 +1640,7 @@ A.
 Here is an example of the NetCDF variable attributes that MET uses to
 define a LatLon grid...
 
-.. code-block:: ini
+.. code-block:: none
 
 		:Projection = "LatLon" ; 
 		:lat_ll = "25.063000 degrees_north" ; 
@@ -1653,7 +1653,7 @@ define a LatLon grid...
 This can be created by running the "regrid_data_plane" tool to regrid
 some GFS data to a LatLon grid:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/regrid_data_plane \ 
 		gfs_2012040900_F012.grib G110 \ 
@@ -1673,7 +1673,7 @@ regridding all fields, the wgrib2 utility may be more useful. Here's an
 example of using wgrib2 and pcp_combine to generate NetCDF files
 MET can read:
 
-.. code-block:: ini
+.. code-block:: none
 
 		wgrib2 gfsrain06.grb -new_grid latlon 112:131:0.1 \
 		25:121:0.1 gfsrain06_regrid.grb2
@@ -1681,14 +1681,14 @@ MET can read:
 And then run that GRIB2 file through pcp_combine using the "-add" option
 with only one file provided:
 
-.. code-block:: ini
+.. code-block:: none
 
 		pcp_combine -add gfsrain06_regrid.grb2 'name="APCP"; \
 		level="A6";' gfsrain06_regrid.nc
 
 Then the output NetCDF file does not have this problem:
 
-.. code-block:: ini
+.. code-block:: none
 
 		ncdump -h 2a_wgrib2_regrid.nc | grep "_ll"
 		:lat_ll = "25.000000 degrees_north" ;
@@ -1700,7 +1700,7 @@ Model Suffix?**
 A.
 Below is a command example to run:
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/tc_pairs \ 
 		-adeck aep142014.h4hw.dat \ 
@@ -1712,7 +1712,7 @@ Below is a command example to run:
 
 Below is a warning message:
 
-.. code-block:: ini
+.. code-block:: none
 
 		WARNING: TrackInfo::add(const ATCFLine &) -> 
 		skipping ATCFLine since the valid time is not
@@ -1729,7 +1729,7 @@ are probably passing tc_pairs duplicate track data.
 Using grep, notice that the same track data shows up in
 "aal032014.h4hw.dat" and "aal032014_hfip_d2014_BERTHA.dat". Try this: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		grep H4HW aal*.dat | grep 2014080100 | grep ", 000,"
 		aal032014.h4hw.dat:AL, 03, 2014080100, 03, H4HW, 000, 
@@ -1757,7 +1757,7 @@ actually differs from that in the second file, there is another option.
 You can specify a model suffix to be used for each ADECK source, as in
 this example (suffix=_EXP):
 
-.. code-block:: ini
+.. code-block:: none
 
 		${MET_BUILD_BASE}/bin/tc_pairs \ 
 		-adeck aal032014.h4hw.dat suffix=_EXP \ 
@@ -1921,7 +1921,7 @@ on other things to check if you are having problems installing or running MET.
 
 **BUFRLIB Errors during MET installation**
 
-.. code-block:: ini
+.. code-block:: none
 
 		error message: /usr/bin/ld: cannot find -lbufr
 		The linker can not find the BUFRLIB library archive file it needs. 
@@ -1938,14 +1938,14 @@ Try the following 2 things:
 1.
 Check to make sure this file exists: 
 
-.. code-block:: ini
+.. code-block:: none
 
 		ls /home/username/BUFRLIB_v10.2.3/libbufr.a
 
 2.		
 Rerun the MET configure command using the following option on the command line: 
 
-.. code-block:: ini
+.. code-block:: none
 		
 		MET_BUFRLIB=/home/username/BUFRLIB_v10.2.3 
 
@@ -1959,7 +1959,7 @@ Single quotes, double quotes, and escape characters can be difficult for
 MET to parse. If there are problems, especially in Python code, try
 breaking the command up like the below example.
 
-.. code-block:: ini
+.. code-block:: none
 
 		['/h/WXQC/{MET_BUILD_BASE}/bin/regrid_data_plane', 
 		'/h/data/global/WXQC/data/umm/1701150006', 
@@ -1971,7 +1971,7 @@ breaking the command up like the below example.
 In the below incorrect example for many environment variables have both
 the main variable set and the INC and LIB variables set:
 
-.. code-block:: ini
+.. code-block:: none
 
 		export MET_GSL=$MET_LIB_DIR/gsl 
 		export MET_GSLINC=$MET_LIB_DIR/gsl/include/gsl 
@@ -1980,13 +1980,13 @@ the main variable set and the INC and LIB variables set:
 **only MET_GSL *OR *MET_GSLINC *AND *MET_GSLLIB need to be set.**
 So, for example, either set:
 
-.. code-block:: ini
+.. code-block:: none
 
 		export MET_GSL=$MET_LIB_DIR/gsl
 
 or set:
 
-.. code-block:: ini
+.. code-block:: none
 
 		export MET_GSLINC=$MET_LIB_DIR/gsl/include/gsl export MET_GSLLIB=$MET_LIB_DIR/gsl/lib
 
@@ -2001,7 +2001,7 @@ http://www.dtcenter.org/met/users/support/online_tutorial/METv6.0/tutorial.php?n
 
 This example shows a problem with NetCDF in the make_install.log file:
 
-.. code-block:: ini
+.. code-block:: none
 
 		/usr/bin/ld: warning: libnetcdf.so.11, 
 		needed by /home/zzheng25/metinstall//lib/libnetcdf_c++4.so, 
@@ -2009,7 +2009,7 @@ This example shows a problem with NetCDF in the make_install.log file:
 
 Below are examples of too many MET_NETCDF options:
 
-.. code-block:: ini
+.. code-block:: none
 
 		MET_NETCDF='/home/username/metinstall/' 
 		MET_NETCDFINC='/home/username/local/include'