fix: spell checking everything

completed a full spell check of templates, and exchange readme files

.github/ISSUE_TEMPLATE/dataset_bug_report.md

@@ -12,16 +12,16 @@ assignees: ''
 
 ### **Bug Type**
 
-- [ ] Syntax - invalid ifc syntax or encoding
+- [ ] Syntax - invalid Ifc syntax or encoding
 - [ ] Usage & Logic - content not representative or invalid against purpose
-- [ ] Validiation Criteria - does not satisfy defined criteria
+- [ ] Validation Criteria - does not satisfy defined criteria
 - [ ] Coverage - does not provide adequate coverage of variations
 
 **Test Case Code**: [MVD_Ex_XXXX](url)
 
 
 ### **Expected content/behaviour**
-*A clear and concise description of what the expected behavour or content is.*
+*A clear and concise description of what the expected behaviour or content is.*
 
 ***Screenshots**
 If applicable, add screenshots to help explain your problem.*

.github/ISSUE_TEMPLATE/documentation_bug_report.md

@@ -1,5 +1,5 @@
 ---
-name: Documenation Bug report
+name: Documentation Bug report
 about: Create a report to help us improve documentation
 title: '[Bug Docs]: '
 labels: bug, documentation
@@ -16,8 +16,8 @@ assignees: ''
 
 - [ ] Exchange documentation
 - [ ] Test case documentation
-- [ ] Test case principles or valdiation criteria
-- [ ] Test case datasets documentaiton
+- [ ] Test case principles or validation criteria
+- [ ] Test case datasets documentation
 
 **Reference Code**: [MVD_Ex_XXXX](url)
 

.github/pull_request_template.md

@@ -1,9 +1,9 @@
 ## Summary
 
-*Outline of the content and tasks addressed by this pull request, dont forget to link the relevent issue(s)*
+*Outline of the content and tasks addressed by this pull request, don't forget to link the relevant issue(s)*
 
 ## Purpose
-Please mark the relevent tasks that this pull request creates or updates:
+Please mark the relevant tasks that this pull request creates or updates:
 
 ### Exchanges
 

E1-ALRF/README.md

@@ -1,6 +1,6 @@
 # Alignment Reference Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name                | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name                | Test Cases |
 |--------------------|--------------|------------------------------|------------|
 | **IFC4x3_AbRV-E1** | ALRF         | Alignment Reference Exchange | 2          |
 

E10-MTME/README.md

@@ -1,8 +1,8 @@
 # Maritime Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name               | Test Cases |
-|--------------------|--------------|-----------------------------|------------|
-| **IFC4x3_AbRV-E10** | TECO        | Maritime Elements Exchange  | XX         |
+| Exchange Code       | Abbreviation | Exchange Name               | Test Cases |
+|---------------------|--------------|-----------------------------|------------|
+| **IFC4x3_AbRV-E10** | TECO         | Maritime Elements Exchange  | XX         |
 
 Exchange Lead: @AlexBrad1eyCT
 

E1a-ARSE/README.md

@@ -1,6 +1,6 @@
 # Alignment Reference Super Elevation Exchange
 
-| Exhange Code        | Abbreviation | Exchange Name                                | Test Cases |
+| Exchange Code       | Abbreviation | Exchange Name                                | Test Cases |
 |---------------------|--------------|----------------------------------------------|------------|
 | **IFC4x3_AbRV-E1a** | ARSE         | Alignment Reference Super Elevation Exchange | 2          |
 
@@ -20,7 +20,7 @@ TBC
 
 ## Test Instructions
 
-| TI Code                            | Test Instruction Title           |
-|------------------------------------|----------------------------------|
-| [**IFC4x3_AbRV-E1a-ALIN**](./ALIN) | Alignment Infrastructure Curves  |
-| [**IFC4x3_AbRV-E1a-ALSE**](./ALSE) | Alignment Superelevation & Width |
+| TI Code                            | Test Instruction Title            |
+|------------------------------------|-----------------------------------|
+| [**IFC4x3_AbRV-E1a-ALIN**](./ALIN) | Alignment Infrastructure Curves   |
+| [**IFC4x3_AbRV-E1a-ALSE**](./ALSE) | Alignment Super Elevation & Width |

E1b-ARCT/README.md

@@ -1,6 +1,6 @@
 # Alignment Reference Cant Exchange
 
-| Exhange Code        | Abbreviation | Exchange Name                     | Test Cases |
+| Exchange Code       | Abbreviation | Exchange Name                     | Test Cases |
 |---------------------|--------------|-----------------------------------|------------|
 | **IFC4x3_AbRV-E1b** | ALCT         | Alignment Reference Cant Exchange | 2          |
 

E2-AGST/README.md

@@ -1,6 +1,6 @@
 # Aggregate Structures Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name                 | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name                 | Test Cases |
 |--------------------|--------------|-------------------------------|------------|
 | **IFC4x3_AbRV-E2** | AGST         | Aggregate Structures Exchange | 5          |
 

E2a-TRST/README.md

@@ -1,6 +1,6 @@
 # Track Structures Exchange
 
-| Exhange Code        | Abbreviation | Exchange Name             | Test Cases |
+| Exchange Code       | Abbreviation | Exchange Name             | Test Cases |
 |---------------------|--------------|---------------------------|------------|
 | **IFC4x3_AbRV-E2a** | AGST         | Track Structures Exchange | 1          |
 

E3-EWKS/README.md

@@ -1,6 +1,6 @@
 # Earthworks Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name       | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name       | Test Cases |
 |--------------------|--------------|---------------------|------------|
 | **IFC4x3_AbRV-E3** | EWKS         | Earthworks Exchange | 4          |
 

E4-BRST/README.md

@@ -1,6 +1,6 @@
 # Bridge Structural Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name              | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name              | Test Cases |
 |--------------------|--------------|----------------------------|------------|
 | **IFC4x3_AbRV-E4** | BRST         | Bridge Structural Exchange | XX         |
 

E5-SIGN/README.md

@@ -1,6 +1,6 @@
 # Signalling Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name       | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name       | Test Cases |
 |--------------------|--------------|---------------------|------------|
 | **IFC4x3_AbRV-E5** | SIGN         | Signalling Exchange | XX         |
 

E6-ENGY/README.md

@@ -1,6 +1,6 @@
 # Energy Exchange (Railway)
 
-| Exhange Code       | Abbreviation | Exchange Name             | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name             | Test Cases |
 |--------------------|--------------|---------------------------|------------|
 | **IFC4x3_AbRV-E6** | ENGY         | Energy Exchange (Railway) | XX         |
 

E7-GEOT/README.md

@@ -1,6 +1,6 @@
 # Geotechnics Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name        | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name        | Test Cases |
 |--------------------|--------------|----------------------|------------|
 | **IFC4x3_AbRV-E7** | GEOT         | Geotechnics Exchange | 5          |
 

E8-TECO/README.md

@@ -1,6 +1,6 @@
 # Telecommunications Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name               | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name               | Test Cases |
 |--------------------|--------------|-----------------------------|------------|
 | **IFC4x3_AbRV-E7** | TECO         | Telecommunications Exchange | XX         |
 

E9-DNGE/README.md

@@ -1,6 +1,6 @@
 # Drainage Exchange
 
-| Exhange Code       | Abbreviation | Exchange Name     | Test Cases |
+| Exchange Code      | Abbreviation | Exchange Name     | Test Cases |
 |--------------------|--------------|-------------------|------------|
 | **IFC4x3_AbRV-E8** | TECO         | Drainage Exchange | XX         |
 

docs/CONTRIBUTING.md

@@ -6,7 +6,7 @@ Use the table of contents icon <img src="../assets/images/table-of-contents.png"
 ## Getting Started
 This repository contains the working content for the documentation and certification of the draft Alignment based Reference View (Model View Definition) or AbRV for the reference exchange of infrastructure information.
 
-It also serves as an initial proof of concept for the use of a git repository for the development and dissemination of MVD certification information, with the objective to speed up the development of the certification test cases and content, and provide greater access and readability of the certification critieria content.
+It also serves as an initial proof of concept for the use of a git repository for the development and dissemination of MVD certification information, with the objective to speed up the development of the certification test cases and content, and provide greater access and readability of the certification criteria content.
 
 The repository is structured into the following layers breaking down the content in to the MVD exchange definitions and associated Test cases & Test case datasets:
 
@@ -18,14 +18,14 @@ The repository is structured into the following layers breaking down the content
       - *Readme*: Documentation of the Test case
       - **Test Case Dataset**
         - *Readme*: Documentation of the test case dataset
-        - IFC dataset, images, and supplimentary files
+        - IFC dataset, images, and supplementary files
 
 The content of the readme's and folders is further explained below in the [templates](#templates) section of the guide.
 
 ## Issues & Proposals
-If you spot an problem or have a proposal for additional content such as exchange definitions or test cases, this should be logged as an issue. Before logging a new issue make sure to [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments), to avoid duplication. If a related issue or proposal doesn't exist, you can open a new issue using a relevent [issue form](https://github.com/bSI-InfraRoom/MVD-Infra-Test-Instructions/issues/new/choose).
+If you spot an problem or have a proposal for additional content such as exchange definitions or test cases, this should be logged as an issue. Before logging a new issue make sure to [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments), to avoid duplication. If a related issue or proposal doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/bSI-InfraRoom/MVD-Infra-Test-Instructions/issues/new/choose).
 
-Please label your issues appropriately using the currently defined labels of the repository. Labels are based on the catagory of issue and the effect a solution will have on the content base.
+Please label your issues appropriately using the currently defined labels of the repository. Labels are based on the category of issue and the effect a solution will have on the content base.
 
 ## Content Contribution
 To contribute to the content being developed or solve outstanding issues brought up by the community, this repository uses a Fork & Pull Request workflow to ensure quality and control contribution to the content base.
@@ -37,7 +37,7 @@ The repository has 2 main branches:
 - master: containing primary released content
 - develop: completed and/or quality assured content for the next release.
 
-feature branches should be named `feature/xxxx` to destinguish them from other types of branches such as bugfixes or release branches.
+feature branches should be named `feature/xxxx` to distinguish them from other types of branches such as bugfixes or release branches.
 
 ### Content & Templates
 Once a fork and branch has been setup, you are free to develop your content. this should be developed using the templates in the [docs](./) folder for an exchange definition or test case. detailed content of the readme's and folders is further explained below in the [templates](#templates) section of the guide.
@@ -47,7 +47,7 @@ once the content is complete or is ready to be initially reviewed by the maintai
 
 use the provide pull request template to specify the content being submitted and assign the appropriate labels. Assignees are those developing the pull request (aka you!) and Reviewers will be assigned appropriately based on content.
 
-Make sure to Link the relevent issue to your pull request via the Linked issues interface or key words such as `fixes #XX` in the PR summary. [Information on linking issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+Make sure to Link the relevant issue to your pull request via the Linked issues interface or key words such as `fixes #XX` in the PR summary. [Information on linking issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
 
 
 ## Templates

docs/En-XXXX/README.md

@@ -0,0 +1,22 @@
+# Template Exchange
+
+| Exchange Code       | Abbreviation | Exchange Name               | Test Cases |
+|---------------------|--------------|-----------------------------|------------|
+| **IFC4x3_AbRV-En**  | XXXX         | Template Exchange           | XX         |
+
+Exchange Lead: @XXX
+
+## Summary
+
+TBC
+
+### Scope
+
+TBC
+
+## Test Instructions
+
+| TI Code                            | Test Instruction Title             |
+|------------------------------------|------------------------------------|
+| [**IFC4x3_AbRV-E10-XXXX**](./XXXX) | Test Instruction                   |
+

docs/XXXX/README.md

@@ -86,7 +86,7 @@ For certification of capabilities the only source will be:
 
 - n. 1 IFC file containing the information as requested. The file shall be named using the following syntax: `MVDCode`-`ExchangeCode`-`TestCode`-`SoftwareVendor`.`ifc` (Example: `IFC4.3_AbRV-E2b-ASTPC-AmazingSoft.ifc`)
 
-Considering the aim of this test, other **optional** results, not subject to the bSI certification process, yet usefull to illustrate test results are:
+Considering the aim of this test, other **optional** results, not subject to the bSI certification process, yet useful to illustrate test results are:
 - Screen-shot of ...
 - CSV export of ...