Fixed a few typos in GDAL TiledWMS documentation

docs/map-library-usage.md

@@ -89,7 +89,7 @@ In the above XML block, the following values may be changed to meet your needs:
 * **Tiled Group Name** - When accessing visualizations through TWMS, the *TiledGroupName* value is utilized instead of the layers identifier. The *TiledGroupName* can also be generated by replacing all underscores in a visualization's *Identifier* from GetCapabilities with spaces and appending " tileset". For example:
     * **Identifier** - MODIS_Aqua_CorrectedReflectance_TrueColor
     * **Tiled Group Name** - MODIS Aqua CorrectedReflectance TrueColor tileset
-* **Time** - Insert the date (e.g. 2013-08-21) or datetime (e.g. 2013-08-21T00:00:00Z) you are requesting. If not time is provided, you can add an option to your GDAL command to specify the value, e.g., `-oo Change=time:2020-02-05` 
+* **Time** - Insert the date (e.g. 2013-08-21) or datetime (e.g. 2013-08-21T00:00:00Z) you are requesting. If no time is provided, you can add an option to your GDAL command to specify the value, e.g., `-oo Change=time:2020-02-05` 
 
 
 
@@ -111,7 +111,7 @@ Let's save the XML as a file named `GIBS_Aqua_MODIS_true.xml`
 ```
 gdal_translate -of GTiff -outsize 1200 1000 -projwin -105 42 -93 32 GIBS_Aqua_MODIS_true.xml GreatPlainsSmoke1.tif
 ```
-The XML file can be opened in any GDAL based GIS software. However, in In ArcGIS Pro, TileWMS is not recognized without some extra configuration steps, but it can be dragged and dropped into a map and it will work. Alternatively, we can change the extension into something supported, like .tif for example.
+The XML file can be opened in any GDAL based GIS software. However, in ArcGIS Pro, TileWMS is not recognized without some extra configuration steps, but it can be dragged and dropped into a map and it will work. Alternatively, we can change the extension into something supported, like .tif for example.
 
 This file shows one of the main advantages of the TiledWMS over other GDAL WMS minidriver protocols. Only the minimum amount of information is stored in the handle file. No fiddling with bounding boxes, tile sizes, number of levels is required. Getting the detail correct becomes the responsibility of the source server. All that is needed is the server URL, the name of the tiled group and optionally a set of parameter changes supported by the tiled group.
 
@@ -136,7 +136,7 @@ gdal_translate -of JPEG -outsize 2560 1280 -oo TiledGroupName="MODIS Aqua Correc
 ```
 
 ##### #4 - Generate "TiledWMS" Configuration Files for Specified Datasets
-gdal_translate has a `-sds` option where each subdataset of the input is copied, in sequence. This can be used to generate multiple handle files in a single command. We can use the open options to restrict which gets generated. For example, this generates all the handle files for patterns that contain the word infrared:
+gdal_translate has a `-sds` option where each subdataset of the input is copied, in sequence. This can be used to generate multiple handle files in a single command. We can use the open options to restrict which gets generated. For example, this generates all the handle files for patterns that contain the word "infrared":
 ``` shell
 gdal_translate -of WMS -sds -oo TiledGroupName="infrared" -oo Change=time:2019-10-21 "https://gibs.earthdata.nasa.gov/twms/epsg4326/best/twms.cgi?request=GetTileService" Infrared.tWMS
 ```