Merge pull request #160 from opengeospatial/final_review_for_publication

Final review of Part 1 for publication

Author: ghobona

api/part1/standard/sections/clause_4_terms_and_definitions.adoc

@@ -50,10 +50,11 @@ The thing whose property is being estimated or calculated in the course of an Ob
 
 
 === Observation
-Act of observing a property
+Act of carrying out an (Observation) Procedure to estimate or calculate a value of a property of a Feature of Interest.
 
 [.source]
-<<ISO19156, ISO-19156, definition 4.10>>
+<<SOSA-SSN, SOSA/SSN, http://www.w3.org/ns/sosa/Observation[Observation Class]>>
+
 
 
 === Platform

api/part1/standard/sections/clause_5_conventions.adoc

@@ -59,7 +59,7 @@ In this document the following abbreviations and acronyms are used or introduced
 - URI: Uniform Resource Identifier
 - UTC: Coordinated Universal Time
 - WKT: Well-Known Text
-- XML: eXtended Markup Language
+- XML: eXtensible Markup Language
 - 1D:	One Dimensional
 - 2D:	Two Dimensional
 - 3D:	Three Dimensional

api/part1/standard/sections/clause_6_overview.adoc

@@ -66,7 +66,7 @@ Encodings are specified in <<clause-encodings>> of this Standard. Each encoding
 
 === Resource Collections
 
-The CS API Standard defines several resource types that are intended to be offered by the server via separate collections. These resource collections are governed by requirements from ogcapi-features-1. Such collections will be referred to as OGC API Collections in the rest of this document.
+The CS API Standard defines several resource types that are intended to be offered by the server via separate collections. These resource collections are governed by requirements from {ogcapi-features-1}. Such collections will be referred to as OGC API Collections in the rest of this document.
 
 The CS API makes use of this collection mechanism to allow a server to provide a more organized view of its content, by grouping them into logical collections according to any criteria.
 
@@ -110,7 +110,7 @@ Several types of API endpoints are defined by the CS API Standard:
 
 ==== Canonical Resources Endpoints
 
-A canonical resource**s** endpoint exposes all resources of a given type hosted by the server. It provides a default endpoint for creating new resources (using HTTP POST), and retrieving/searching resources (using HTTP GET) of this type. Canonical resource**s** endpoint have simple URLs located directly at the API root.
+A canonical resource**s** endpoint exposes all resources of a given type hosted by the server. It provides a default endpoint for creating new resources (using HTTP POST), and retrieving/searching resources (using HTTP GET) of this type. The canonical resource**s** endpoints have simple URLs located directly at the API root.
 
 The canonical resources endpoints for resource types defined in Part 1 of the CS API Standard are:
 
@@ -222,10 +222,10 @@ The following link relation types are defined and used in this Standard:
 | `ogc-rel:sampleOf`                 | <<sf-assocs,`Sampling Feature`>>            | Link to other sampling features that the sampling feature is a sample of.
 | `ogc-rel:datastreams`              | <<system-assocs,`System`>>,
                                        <<deployment-assocs,`Deployment`>>,
-                                       <<sf-assocs,`Sampling Feature`>>            | Link to the datastreams that are associated to the entity,
+                                       <<sf-assocs,`Sampling Feature`>>            | Link to the datastreams that are associated to the entity.
 | `ogc-rel:controlStreams`           | <<system-assocs,`System`>>,
                                        <<deployment-assocs,`Deployment`>>,
-                                       <<sf-assocs,`Sampling Feature`>>            | Link to the controlstreams that are associated to the entity,
+                                       <<sf-assocs,`Sampling Feature`>>            | Link to the controlstreams that are associated to the entity.
 |====
 
 

api/part2/standard/sections/clause_5_conventions.adoc

@@ -32,7 +32,7 @@ In this document the following abbreviations and acronyms are used or introduced
 - TAI:	Temps Atomique International (International Atomic Time)
 - UML:	Unified Modeling Language
 - UTC:	Coordinated Universal Time
-- XML:	eXtended Markup Language
+- XML:	eXtensible Markup Language
 - 1D:	One Dimensional
 - 2D:	Two Dimensional
 - 3D:	Three Dimensional