Small Tweaks

workshop/content/docs/api-deep-dive/features.md

@@ -288,7 +288,7 @@ The API definition describes the capabilities of the server. It can be used by d
 
 There are conformance classes to provide the API definition using [Open API](https://ogcapi-workshop.ogc.org/overview-and-main-concepts/#openapi). Some servers also return a human-readable representation of the definition in HTML, using tools such as Redoc or Swagger. 
 
-This is an extract of an API definition, which uses Open API 3:
+This is an extract of an [API definition](https://demo.ldproxy.net/daraa/api?f=json), which uses Open API 3:
 
 ```json
 {

workshop/content/docs/api-deep-dive/sensorthings.md

@@ -185,13 +185,13 @@ station.
 
 The data returned by the service can be rendered by a desktop Geographic
 Information System (GIS) or a web application. Alternatively, it can be
-forwarded to an OGC WPS for further processing.
+forwarded to an OGC API - Processes service for further processing.
 
 ### Client usage
 
 A client needs to know the location of the SensorThings API service to
 be able to interact with the server. The location is usually called the
-```end point``` of the service and is represented by the service root URI.
+```endpoint``` of the service and is represented by the service root URI.
 Resources available through the service can be accessed by appending a
 resource path and, optionally query options.
 
@@ -208,7 +208,7 @@ http://toronto-bike-snapshot.sensorup.com/v1.0
 The link to the request
 is: <http://toronto-bike-snapshot.sensorup.com/v1.0/Datastreams(206051)/Observations(1593917)?$select=result>
 
-Checkout various available public end points [here](https://github.com/opengeospatial/sensorthings/blob/master/PublicEndPoints.md)
+Checkout various available public endpoints [here](https://github.com/opengeospatial/sensorthings/blob/master/PublicEndPoints.md)
 
 
 ## Operations

workshop/content/docs/api-deep-dive/tiles.md

@@ -147,12 +147,12 @@ following table.
     <td>/api</td>
   </tr>
   <tr>
-    <td>Tiling Schemes</td>
+    <td>Tile matrix sets</td>
     <td>GET</td>
     <td>/tileMatrixSets</td>
   </tr>
   <tr>
-    <td>Tiling Scheme (tile matrix set)</td>
+    <td>Tile matrix set</td>
     <td>GET</td>
     <td>/tileMatrixSets/{tileMatrixSetId}</td>
   </tr>

workshop/content/docs/background-and-context.md

@@ -71,7 +71,7 @@ API (now OGC API - Environmental Data Retrieval).  This represented the origins
 The development and working processes of OGC standards development themselves evolved during this time.  OGC API specifications began to be
 developed on public GitHub repositories, allowing for anyone in the public to discuss and collaboration for a given OGC API standard in the
 open on GitHub.  In addition, the specifications themselves began to be developed in AsciiDoc (an open format for documentation/markup), and
-made available as HTML pages (and PDF).  Collaborative tools used by OGC also proliferated, such as Gitter/Element as well as Discourse.
+made available as HTML pages (and PDF).  Collaborative tools used by OGC also proliferated, such as Gitter/Element as well as Discord.
 
 !!! note
     OGC standards, while primarily developed on GitHub, are voted on by the OGC membership.

workshop/content/docs/overview-and-main-concepts.md

@@ -132,7 +132,7 @@ The OGC API effort is rapidly evolving. Numerous OGC API standards are in develo
 - [Joins](https://ogcapi.ogc.org/joins)  supports the joining of data, from multiple sources, with feature collections or directly with other input files
 - [Discrete Global Grid System](https://ogcapi.ogc.org/dggs) enables applications to organise and access data arranged according to a Discrete Global Grid System (DGGS)
 
-![Approved and candidate OGC API standards](assets/images/ogcapis.png)
+![Approved and candidate OGC API standards](assets/images/ogcapis-overview.png)
 
 #### OpenAPI