Miscellaneous spelling fixes

Signed-off-by: Pierre R. Mai <[email protected]>

Author: pmai

specification/0___preamble.adoc

@@ -72,7 +72,7 @@ ____
 *Abstract*
 
 The SSP Layered Standard Traceability is a layered standard provided by MAP SSP upon SSP 2.0 to support traceability of simulation tasks.
-The standard is comprised of a set of XML-based formats to interchange process-relevant resources and information in the sense of process metadata for Credible Decision Processes and Credible Simulation Processes, as well as abritrary further metadata as part of SSP packages used to exchange the structural and parametrization aspects of a system.
+The standard is comprised of a set of XML-based formats to interchange process-relevant resources and information in the sense of process metadata for Credible Decision Processes and Credible Simulation Processes, as well as arbitrary further metadata as part of SSP packages used to exchange the structural and parametrization aspects of a system.
 
 <<<
 

specification/3___overview.adoc

@@ -106,7 +106,7 @@ image::STMDBriefSchema.png[]
 [#sec-srmdintroduction]
 === Simulation Resource Meta Data
 
-<<im-srmdbriefschema>> shows the top-level structure of the SRMD XML Schema, which is the structural definition for Simulation Resouce Meta Data files.
+<<im-srmdbriefschema>> shows the top-level structure of the SRMD XML Schema, which is the structural definition for Simulation Resource Meta Data files.
 SRMD files are used to define essential metadata for resources that can help users quickly understand the content and intent of a simulation resource through human-readable attributes without having to examine the resource in detail.
 For example, this support can reduce the effort required to analyze a set of resources received with a simulation request and simplify the selection of appropriate resources from a resource library.
 

specification/4___common.adoc

@@ -22,6 +22,6 @@ Basic Structuring::
 All steps in process descriptions provide the same information structure (input, procedure, output and rationale) across the board, which provides a basic structuring of related resources at a coarse level, that can then be extended through extended links and classifications.
 
 Generic Meta Data through Classifications::
-All relevant modeling elements allow for arbitrary, but well-defined, meta-data provisoning through classifications:
+All relevant modeling elements allow for arbitrary, but well-defined, meta-data provisioning through classifications:
 These are collections of keyword value pairs, including linking capabilities, that are grouped by user-defined namespaces defined by classification types.
 In this way layered standards can provide additional meaning and rules to meta-data meeting domain-specific or company-specific needs, while providing basic processing expectations for tools even in the absence of detailed knowledge of the specific classification type.

specification/5___stc.adoc

@@ -2,7 +2,7 @@
 == SSP Traceability Common
 
 This chapter describes in detail the content and structure of the XML schema stc.xsd, which represent common concepts that are reused in the other XML schemas of the standard.
-The purpose of extractiong these elements is to increase the flexibility and extensibility of the GlueParticles approach and to help to apply the GlueParticles concept to other topics in product and system engineering.
+The purpose of extracting these elements is to increase the flexibility and extensibility of the GlueParticles approach and to help to apply the GlueParticles concept to other topics in product and system engineering.
 
 [#sec-generalinformationtype]
 === GeneralInformationType
@@ -38,7 +38,7 @@ The SSP Traceability package represents a snapshot of the used versions of the l
 Versioning of sources and resources is done in the generating tools and data management systems.
 
 The exception is the derivation chain. Each time an STMD or DTMD file is written, a new entry is created in the derivation chain with a unique identifier of the file from which the new instance is derived.
-When a tool or data management system receives an SSP Traceability container with STDM, DTMD back, it can check, by comparing the derivation chain with the target system's data infrastructure, which version of the DTMD or STMD was sent.
+When a tool or data management system receives an SSP Traceability container with STMD/DTMD back, it can check, by comparing the derivation chain with the target system's data infrastructure, which version of the DTMD or STMD was sent.
 This serves as a basis for controlling the reintegration of received DTMD STMD and it can be determined what is already available, what has been modified, what is new, etc.
 
 The DerivationChain element can be used to provide the appropriated set of information about files that were used to derive the current file.
@@ -593,9 +593,9 @@ __'model'__:: The kind value __'model'__ is used to indicate that a resource con
 
 __'parameter'__:: The kind value __'parameter'__ is used to indicate that a resource contains parameters or sets of consistent parameters for a simulation model.
 
-__'system'__:: A resource of kind __'system'__ is or contains a reference to the s__ystem under test__ in a PDM system or similar IT system or any other kind of description of the __system under test.__
+__'system'__:: A resource of kind __'system'__ is or contains a reference to the __system under test__ in a PDM system or similar IT system or any other kind of description of the __system under test.__
 
-__'testcase'__:: A resource of kind __'testcase'__ should contain information that describe how the simulation objectives are achieved at the operational level by one more test cases. A consistent set of test cases could be considered a technical breakdown of the simulation objectives.#
+__'testcase'__:: A resource of kind __'testcase'__ should contain information that describe how the simulation objectives are achieved at the operational level by one more test cases. A consistent set of test cases could be considered a technical breakdown of the simulation objectives.
 
 __'results'__:: #A resource of kind __'result'__ should contain information that answers questions posed by the simulation requester about the goals and intent of the simulation. In principle, this could be any kind of result data, no matter what it actually represents in detail. If the result is intended to be an aggregated and condensed report, the value __'report'__ can be used instead.
 
@@ -729,4 +729,3 @@ The ResourceReference element is associated with the following attributes.
 | id             | Optional            | This attribute gives the model element a file-wide unique id which can be referenced from other elements or via URI fragment identifier. 
 | description    | Optional            | This attribute gives a human readable longer description of the model element, which can be shown to the user where appropriate.
 |===
-

specification/7___stmd.adoc

@@ -106,7 +106,7 @@ The RequirementsPhase element documents all relevant information.
 .RequirementsPhase element structure and attributes
 image::RequirementsPhaseSchema.png[]
 
-The RequirementsPhase element is structured by the followuing subordinated element.
+The RequirementsPhase element is structured by the following subordinated element.
 
 [#tb-requirementsphasesubelements]
 .RequirementsPhase element structure