Use new schema URLs

Author: avillar

Diff for: _pages/create/examples.md

@@ -28,7 +28,7 @@ examples:
 ```
 
 Please refer to
-[the updated JSON schema for `examples.yaml`](https://raw.githubusercontent.com/opengeospatial/bblocks-postprocess/master/ogc/bblocks/examples-schema.yaml)
+[the updated JSON schema for `examples.yaml`](https://raw.githubusercontent.com/opengeospatial/bblocks-postprocess/master/ogc/bblocks/schemas/examples.schema.yaml)
 for more information.
 
 The `examples.yaml` file in `my-building-block` can be used as a template.

Diff for: _pages/create/structure.md

@@ -12,7 +12,7 @@ The following image summarizes the general usage of a building block:
 The `_sources` directory will contain the sources for the building blocks inside this repository.
 
 - `bblock.json`: Contains the metadata for the building block. Please refer to this
-  [JSON schema](https://raw.githubusercontent.com/opengeospatial/bblocks-postprocess/master/ogc/bblocks/metadata-schema.yaml)
+  [JSON schema](https://raw.githubusercontent.com/opengeospatial/bblocks-postprocess/master/ogc/bblocks/schemas/metadata.schema.yaml)
   for more information.
 - `description.md`: Human-readable, Markdown document with the description of this building block.
   See [Adding documentation](documentation) for more information.

Diff for: _pages/create/validation.md

@@ -15,7 +15,7 @@ Test cases defines in the `tests/` subdirectory of each building block get valid
 can be added in `tests.yaml` as a list of objects with a `ref` property pointing to the test resource's location,
 and optionally defining the `output-filename` and/or `require-fail` properties (for more information, see the 
 example `tests.yaml` file provided in the template and 
-[the JSON Schema for `tests.yaml`](https://github.com/opengeospatial/bblocks-postprocess/blob/master/ogc/bblocks/extra-tests-schema.yaml){:target="_blank"}.
+[the JSON Schema for `tests.yaml`](https://github.com/opengeospatial/bblocks-postprocess/blob/master/ogc/bblocks/schemas/tests.schema.yaml){:target="_blank"}.
 
 In each case, the `/build/tests/` directory contains a set of validation outputs.
 

Diff for: _pages/index.markdown

@@ -9,10 +9,10 @@ This is the documentation for the OGC Building Blocks framework, a **specificati
 This supports the FAIR principles for **specifications** - with every specification being a component that can be
 re-used. For more discussion see [Design Principles](overview/principles)
 
-Building Blocks can be used to **add documentation** to existing specification components, or to **design** and *
-*assemble** reusable specification components cost-effectively using a test-driven approach.
+Building Blocks can be used to **add documentation** to existing specification components, or to **design** and 
+**assemble** reusable specification components cost-effectively using a test-driven approach.
 
-Building Blocks are _"technology agnostic"_ - i.e. may be various [types](overview/types) - however an emphasis is
+Building Blocks are *technology-agnostic* - i.e. may be various [types](overview/types) - however an emphasis is
 support for semantically annotated JSON schemas for use in OGC API definitions.
 
 Building Blocks can be organised into [registers](overview/registers) for convenience, each repository creating a local