Change CRS URLs to HTTPS and fix text formatting

Updated URLs to use HTTPS and corrected hyphenation in text.

Author: chris-little

standard/clause_specification_text.adoc

@@ -352,7 +352,7 @@ Example of a two-dimensional geographic CRS (longitude-latitude):
 ```json
 {
   "type": "GeographicCRS",
-  "id": "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
+  "id": "https://www.opengis.net/def/crs/OGC/1.3/CRS84"
 }
 ```
 
@@ -362,7 +362,7 @@ Example of a three-dimensional geographic CRS (latitude-longitude-height):
 ```json
 {
   "type": "GeographicCRS",
-  "id": "http://www.opengis.net/def/crs/EPSG/0/4979"
+  "id": "https://www.opengis.net/def/crs/EPSG/0/4979"
 }
 ```
 Example of a two-dimensional geographic CRS (longitude-latitude) that needs a separate datum:
@@ -395,7 +395,7 @@ Example of a projected CRS using the http://spatialreference.org/ref/epsg/osgb-1
 ```json
 {
   "type": "ProjectedCRS",
-  "id": "http://www.opengis.net/def/crs/EPSG/0/27700"
+  "id": "https://www.opengis.net/def/crs/EPSG/0/27700"
   "description": "British National Grid, United Kingdom Ordnance Survey" 
 }
 ```
@@ -427,7 +427,7 @@ Example of a vertical CRS, here representing height above the NAVD88 datum in me
 ```json
 {
   "type": "VerticalCRS",
-  "id": "http://www.opengis.net/def/crs/EPSG/0/5703"
+  "id": "https://www.opengis.net/def/crs/EPSG/0/5703"
   "description": "North American Vertical Datum 1988"
 }
 ```
@@ -441,7 +441,7 @@ In the original version, V1.0, of this Community Standard, only a string-based n
 
 This version, V1.0.1, of the Community Standard allows for the alternative notation, allowing the recording of time values as numeric offsets from a given fixed temporal datum (e.g. “days since 1970-01-01”).
 
-The temporal datum, also know as an epoch, for both kinds of Temporal Reference Systems is always specified as a calendar based string.
+The temporal datum, also know as an epoch, for both kinds of Temporal Reference Systems is always specified as a calendar-based string.
 
 - A temporal RS object MUST have a member `"type"`. The only currently defined values are `"TemporalRS"` or `"TemporalCRS"`.
 - A temporal RS object MUST have a member `"calendar"` with value `"Gregorian"` or a URI.
@@ -462,7 +462,7 @@ The temporal datum, also know as an epoch, for both kinds of Temporal Reference
 //#### 6.2.1 Temporal calendar-based Reference Systems
 ===== Temporal, calendar-based, Reference Systems
 
-A Temporal Reference System used a calendar-based string notation to specify a date-time with respect to an epoch.
+A Temporal Reference System uses a calendar-based string notation to specify a date-time with respect to an epoch.
 
 Example of a calendar-based Temporal Reference System:
 
@@ -473,6 +473,7 @@ Example of a calendar-based Temporal Reference System:
   "calendar": "Gregorian"
 }
 ```
+
 //#### 6.2.2 Temporal Coordinate Reference Systems
 ===== Temporal Coordinate Reference Systems