Add some text for the parameters and remove markdown horizontal break

schema/docs/versions.md

@@ -295,7 +295,7 @@ Now that we know how to encode version objects, that would be written as:
 Type identifier: `semver-2.0.0`
 Formally specified here at https://semver.org/spec/v2.0.0.html
 `semver-2.0.0` is new type introduced to formally specify usage of semantic versioning. 
----
+
 `semver-2.0.0` in its simplest form is a dot separated triple. eg `1.2.3`. The three parts have names with the first being the `MAJOR`, the second being `MINOR` and the third `PATCH`. The [Semantic](https://en.wikipedia.org/wiki/Semantics) meaning of each is described as 
 1. MAJOR version when you make incompatible API changes
 2. MINOR version when you add functionality in a backward compatible manner
@@ -308,6 +308,8 @@ While the triple can only contain numeric values the `pre-release` and `build` a
 A complete definition of this version type can be viewed here
 https://semver.org/spec/v2.0.0.html#backusnaur-form-grammar-for-valid-semver-versions
 
+In the interest of simplicity the `semver-2.0.0` version type has two parameters which define a continuous range. `lowerBound` and `upperBound` each must be a valid semver triple with optional pre-release/build extensions.
+
 ##### Example
 
 ```