Update CONFORMANCE_TESTS.md

Author: mr-c

CONFORMANCE_TESTS.md

@@ -23,7 +23,7 @@ The CWL implementation to be tested.
 
 `--tags`
 
-A comman separated list of [tags](#tags-for-conformance-tests); only tests with these tags will be tested.
+A comma separated list of [tags](#tags-for-conformance-tests); only tests with these tags will be tested.
 `--tags shell_command` will run all tests with `shell_command` in their `tags` list.
 
 `-n{test_range}`
@@ -93,15 +93,16 @@ system some needed GNU-like tools like `greadlink`.
 
 ## Format of the conformance test file
 
-Conformance tests consist of input CWL descriptions + a input CWL object and the expected outputs (or `should_fail: true` if the test is deliberately broken)
+Conformance tests consist of input CWL descriptions plus an input CWL object
+and the expected outputs (or `should_fail: true` if the test is deliberately broken)
 
 They are stored in [`conformance_tests.yaml`](https://github.com/common-workflow-language/cwl-v1.2/blob/main/conformance_tests.yaml)
 (or a file `$import`ed into that one)
 
-You can examine [the formal schema of this file](https://github.com/common-workflow-language/cwltest/blob/main/cwltest/cwltest-schema.yml)
+You can examine [the formal schema of this file](https://github.com/common-workflow-language/cwltest/blob/main/cwltest/cwltest-schema.yml),
 or just continue reading here for an explanation.
 
-The conformante test file is a YAML document: a list of key-value pairs.
+The conformance test file is a YAML document: a list of key-value pairs.
 
 We will use this single entry to explain the format
 ``` yaml
@@ -114,15 +115,15 @@ We will use this single entry to explain the format
    tags: [ required, command_line_tool ]
 ```
 - `doc`: A sentence that explain what is being tested. Will be printed at test execution time. Should be unique.
-- `label`: a short list of  underscore (`_`) seperated words that succintly identifies and explains the test.
+- `label`: a short list of  underscore (`_`) separated words that succinctly identifies and explains the test.
 - `tool` the path to the CWL description to run
 - `job`: the CWL input object in YAML/JSON format. If there are no inputs then use `tests/empty.json`.
 - `output` [the CWL output object expected.](#output-matching)
 - `tags`: a yaml list of tag names, see [the list of canonical tags below](#tags-for-conformance-tests).
 
-Because this is a `schema-salad` processed document, `$import` can be used to organize the tests into seperate files.
+Because this is a `schema-salad` processed document, `$import` can be used to organize the tests into separate files.
 
-Currently the main file is too big (over 3400 lines); we are slowly re-organizing it.
+Currently, the main file is too big (over 3400 lines); we are slowly re-organizing it.
 
 Eventually it would be good to organize the tests so that the test for each optional feature and other logical groups of tests are in their own separate file;
 with the supporting CWL documents and their inputs in separate sub-folders of `tests` as well.
@@ -135,20 +136,20 @@ as entries in the main conformance test file.
 
 In each test entry there is an `output` field that contains a mapping of the expected outputs names and their values.
 
-If a particular value could vary and it doesn't matter to the proper functioning of the test then it can be represented by the special token `Any`.
+If a particular value could vary and it doesn't matter to the proper functioning of the test, then it can be represented by the special token `Any`.
 
 At any level, if there is an extra field, then that will be considered an error.
 An exception to this is `class: File` and `class: Directory` objects, the `cwl-runner` under test can add additional fields here.
-Likewise if you don't want to test some aspect of a `class: File` or `class: Directory` object (like `nameext`) you can just omit it.
+Likewise, if you don't want to test some aspect of a `class: File` or `class: Directory` object (like `nameext`) you can just omit it.
 
 [According to the CWL standards](https://www.commonwl.org/v1.2/CommandLineTool.html#File), the format of the `location` field in 
 `class: File` and `class: Directory` is implementation specific and we should not be testing them.
 Please remember to use `location: any` for them.
 
-Currently we do [test the contents of the location field in some older tests, but we should stop](https://github.com/common-workflow-language/common-workflow-language/issues/930)
+Currently, we do [test the contents of the location field in some older tests, but we should stop](https://github.com/common-workflow-language/common-workflow-language/issues/930)
 If you are editing those old tests, you may be interested in some special processing for  `class: File` and `class: Directory` output objects:
 any `location` value specified will succeed if there is either an exact match to the real output, or it matches the end of the real output.
-Additionall, for `class: Directory` the location reported by the actual execution will have any trailing forward slash (`/`) trimmed off before comparison.
+Additionally, for `class: Directory` the location reported by the actual execution will have any trailing forward slash (`/`) trimmed off before comparison.
 
 ## Writing a new conformance test