fix typo (#290)

Author: Mackenzie-OO7

src/topics/creating-files-at-runtime.md

@@ -1,10 +1,10 @@
 # Creating Files at Runtime
 
 Sometimes you need to create a file on the fly from input parameters,
-such as tools which expect to read their input configuration from a file
+such as tools that expect to read their input configuration from a file
 rather than the command line parameters, or need a small wrapper shell script.
 
-To generate such files we can use the `InitialWorkDirRequirement`.
+To generate such files, we can use the `InitialWorkDirRequirement`.
 
 ```{literalinclude} /_includes/cwl/creating-files-at-runtime/createfile.cwl
 :language: cwl
@@ -13,32 +13,32 @@ To generate such files we can use the `InitialWorkDirRequirement`.
 ```
 
 Any [expressions](../topics/expressions.md) like `$(inputs.message)` are
-expanded by the CWL engine before creating the file;
-here inserting the value at the input `message`.
+expanded by the CWL engine before creating the file.
+Here, insert the value at the input `message`.
 
 ```{tip}
 The _CWL expressions_ are independent of any _shell variables_
 used later during command line tool invocation. That means that any genuine
-need for the character `$` must be **escaped** with `\`,
-for instance `\${PREFIX}` above is expanded to `${PREFIX}` in the generated file
+need for the character `$` must be **escaped** with `\`.
+For instance, `\${PREFIX}` above is expanded to `${PREFIX}` in the generated file
 to be evaluated by the shell script instead of the CWL engine.
 ```
 
-To test the above CWL tool use this job to provide the input value `message`:
+To test the above CWL tool, use this job to provide the input value `message`:
 
 ```{literalinclude} /_includes/cwl/creating-files-at-runtime/echo-job.yml
 :language: yaml
 :caption: "`echo-job.yml`"
 :name: echo-job.yml
 ```
 
-Before we run this, lets look at each step in a little more detail.
+Before we run this, let us look at each step in a little more detail.
 The base command `baseCommand: ["sh", "example.sh"]`
 will execute the command `sh example.sh`.
 This will run the file we create in the shell.
 
 `InitialWorkDirRequirement` requires a `listing`.
-As the `listing` is a YAML array we need a `-` on the first line of
+As the `listing` is a YAML array, we need a `-` on the first line of
 each element of the array, in this case we have just one element.
 `entryname:` can have any value,
 but it must match what was specified in the `baseCommand`.

src/topics/using-containers.md

@@ -30,7 +30,7 @@ then print "Hello World" to the standard output.
 :name: docker-job.yml
 ```
 
-Before we run this, lets just break it down and see what some bits do.  Most of this
+Before we run this, let's just break it down and see what some bits do.  Most of this
 has been explained in previous sections, the only part that is really new is the `dockerRequirement`
 section.
 
@@ -46,7 +46,7 @@ then need to specify some `hints` for how to find the container we want.  In thi
 just our requirements for the docker container in `DockerRequirements`.  The `dockerPull:`
 parameter takes the same value that you would pass to a `docker pull` command. That is,
 the name of the container image (you can even specify the tag, which is good idea for
-best practises when using containers for reproducible research). In this case we have
+best practices when using containers for reproducible research). In this case we have
 used a container called `node:slim`.
 
 Provide a "hello.js" and invoke `cwltool` providing the tool description and the