update OGC services

Author: jmckenna

en/ogc/wcs_format.txt

@@ -140,7 +140,7 @@ DEM
 It is possible to deliver 16 bit DEM data through the MapServer Web Coverage
 Service.
 
-Firstly it is necessary to specify the output format in the map file
+Firstly it is necessary to specify the output format in the mapfile:
 
 .. code-block:: mapfile
 
@@ -152,7 +152,7 @@ Firstly it is necessary to specify the output format in the map file
       EXTENSION "tif"
     END
 
-and the corresponding layer
+and the corresponding layer:
 
 .. code-block:: mapfile
 
@@ -175,8 +175,9 @@ and the corresponding layer
       END
     END
 
-Performance gains can be made by using the `gdaladdo <https://gdal.org/programs/gdaladdo.html>`__ 
-utility.
+.. TIP::
+   Performance gains can be made by using the `gdaladdo <https://gdal.org/programs/gdaladdo.html>`__ 
+   utility on your source rasters.
 
 NetCDF
 ======
@@ -266,7 +267,7 @@ like::
     POLYGON ((xxx,xxxx,.......))
 
 
-Define your output format as
+Define your output format as:
 
 .. code-block:: mapfile
 
@@ -278,7 +279,7 @@ Define your output format as
       EXTENSION 'tif'
     END
 
-Then you need to define your tile index within the mapfile.
+Then you need to define your tile index within the mapfile:
 
 .. NOTE::
    You must setup a :ref:`VALIDATION <validation>` block for MapServer to 
@@ -297,7 +298,7 @@ Then you need to define your tile index within the mapfile.
       END
     END
 
-and the actual layer
+and the corresponding layer:
 
 .. code-block:: mapfile
 
@@ -356,7 +357,7 @@ This requires MapServer 7.2.0 for format-specific and layer-specific
 creation options mechanism, as well as GDAL 2.3.0 for GRIB2 output support.
 
 
-Define your output format as
+Define your output format as:
 
 .. code-block:: mapfile
 
@@ -372,7 +373,7 @@ Define your output format as
 (consult `GDAL GRIB driver documentation`_ for more options that can be 
 provided in FORMATOPTION)
 
-and the actual layer
+and the corresponding layer:
 
 .. code-block:: mapfile