Fix typos and wording.

core/sections/clause_8_ogc-process-description.adoc

@@ -159,10 +159,10 @@ The following JSON Schema fragment illustrates the use of the `format` key to in
 
 ==== Data class
 
-One common input type that a process might accept is a collection of data indicating that the process will somehow operate over the items of the specified collection.  This implies that the process will have certain expections about the structure of the data collection with regard to which properties the data collection contains, their types, etc.  In order to properly process any arbitrary data collection input value a process would have to inspect the structure of that collection to ensure that all the expected properties are present with the expected types, etc.  In order to alleviate the server from having to perform a tedious, and perhaps computationally expensive, schema validation process this Standard introduces the concept of the _Geo-Data Class_ via the `geoDataClass` parameter.  
-The value of the `geoDataClass` parameter is a URI that identifies a predefined set of properties or a sub-schema.  Two data collections tagged with the same `geoDataClass` value can be assumed to contain all the properties defined by the class.  This equivalence allows a server to quickly validate that a specified data collection input value meets the server's expections in terms of the properties available for processing and their types simply by comparing `geoDataClass` values.  If the `geoDataClass` of the input data collection value matches the `geoDataClass` specified in the description of the input then the server can be assured that the process can operate on that collection.  Of course data collections tagged with the same `geoDataClass` URI may contain additional properties not defined by the _Geo-Data Class_ but a process expecting an input value of a particular `geoDataClass` value would simply ignore those extraneous properties.
+One common input type that a process might accept is a collection of data indicating that the process will somehow operate over the items of the specified collection.  This implies that the process will have certain expections about the structure of the data collection with regard to which properties the data collection contains, their types, etc.  In order to properly handle any arbitrary data collection input value a process would need to inspect the structure of the input collection to ensure that all the expected properties are present with the expected types, etc.  To alleviate the server from having to perform such a tedious, and perhaps computationally expensive, schema validation process this Standard introduces the concept of the _Geo-Data Class_ via the `geoDataClass` parameter.  
+The value of the `geoDataClass` parameter is a URI that identifies a predefined set of properties or a sub-schema.  Two data collections tagged with the same `geoDataClass` URI value can be assumed to contain all the properties defined by the class.  This equivalence allows a server to quickly validate that a specified data collection input value meets the server's expections in terms of the properties available for processing, their types, etc. simply by comparing `geoDataClass` values.  If the `geoDataClass` of the input data collection value matches the `geoDataClass` specified in the description of the input then the server can be assured that the process can operate on that collection.  Of course data collections tagged with the same `geoDataClass` URI may contain additional properties not defined by the _Geo-Data Class_ but a process expecting an input value of a particular `geoDataClass` value would simply ignore those extraneous properties.
 
-For example, a specific _Geo-Data Class_ might be defined to include a geometry property _fenceLine_ or type _polygon_.  Thus, any input data collection tagged with this URI can be expected to include a _fenceLine_ property and its type can be assumed to be _polygon_.
+For example, a specific _Geo-Data Class_ might be defined to include a geometry property _fenceLine_ of type _polygon_.  Thus, any input data collection tagged with this URI can be expected to include a _fenceLine_ property and its type can be assumed to be _polygon_.
 
 NOTE: In order for the `geoDataClass` concept to be most effective a registry aking to that found at https://schema.org[Schema.org] would need to be created and maintained.  The OGC definition server is likely the best place to maintain _Geo-Data Class_ URIs.