Merge remote-tracking branch 'origin/release'

Author: mr-c

src/faq.md

@@ -87,8 +87,8 @@ the file using the new name for subsequent steps or as a workflow-level output.
 
 There are two ways to reference a local script:
 
-The first method involves adding the folder containing your scripts to the `PATH` environment variable.
-This allows you to run the shell script directly without using `sh` or `bash` commands.
+The first method involves adding the path to a folder containing your scripts to the `PATH` environment variable. This
+allows you to execute the shell script directly (without explicitly using the `sh` or `bash` commands).
 
 Start with adding a _shebang_ at the top of your file:
 
@@ -135,10 +135,6 @@ baseCommand: sh
 outputs: []
 ```
 
-```{note}
-In CWL, everything must be directly stated.
-```
-
 ## How can I set `self`-based input bindings for optional inputs?
 
 Currently, `cwltool` can't cope with missing optional inputs if their

src/introduction/basic-concepts.md

@@ -159,8 +159,8 @@ in detail in the [Requirements](../topics/requirements-and-hints.md) section.
 > machine accessibility and that all digital assets should be Findable,
 > Accessible, Interoperable, and Reusable. Workflows encode the methods
 > by which the scientific process is conducted and via which data are
-> created. It is thus important that workflows support the creation
-> of FAIR data and adhere to the FAIR principles.
+> created. It is thus important that workflows both support the creation
+> of FAIR data and themselves adhere to the FAIR principles.
 > — [FAIR Computational Workflows](https://workflows.community/groups/fair/),
 > Workflows Community Initiative.
 

src/introduction/prerequisites.md

@@ -26,9 +26,8 @@ of the following options for your operating system:
 - Windows
 
 ```{note}
-If you are using Windows, you will have to install the [Windows Subsystem for Linux 2](https://learn.microsoft.com/en-us/windows/wsl/install) (WSL2).
-Visit the `cwltool` [documentation](https://cwltool.readthedocs.io/en/latest/#ms-windows-users)
-for details on installing WSL2.
+If you are using Windows, you will have to install the Windows Subsystem for Linux 2 as documented in the
+[`cwltool` documentation for Microsoft Windows users](https://github.com/common-workflow-language/cwltool/blob/main/README.rst#ms-windows-users).
 Your operating system also needs internet access and a recent version of Python (3.6+).
 ```
 
@@ -76,7 +75,7 @@ You can run the CWL tool description by omitting the `--validate` option:
 :caption: Running `true.cwl` with `cwltool`.
 ```
 
-### Cwl-runner Python Module
+### Generic ``cwl-runner`` alias
 
 `cwl-runner` is an implementation-agnostic alias for any CWL compliant runner. This simply means
 that the `cwl-runner` alias command can be invoked independently, and is not reliant on a particular

src/topics/command-line-tool.md

@@ -66,9 +66,10 @@ and in the [Outputs](../topics/outputs.md) sections.
 
 
 ## Network Access
-This indicates whether a process requires outgoing IPv4/IPv6 network access.
-If a command-line tool is written manually in CWL v1.1+, there is a need to 
-specify when network access is required.
+This indicates whether a process requires outgoing IPv4/IPv6 network
+access.  Starting with CWL v1.1, programs are not granted network
+access by default, so you must include the requirement for network
+access in the specification of your tool.
 
 ```cwl
 cwlVersion: v1.2
@@ -80,6 +81,6 @@ requirements:
 ```
 
 ```{note}
-CWL v1.0 command-line tools that are upgraded to v1.1 
-or v1.2 get Network Access automatically.
+CWL v1.0 command-line tools that are upgraded to v1.1
+or v1.2 or v1.2 will have `networkAccess: true` set automatically.
 ```

src/topics/operations.md

@@ -53,8 +53,8 @@ style=dashed;
 }
 ```
 
-If you try running it with `cwltool`, the command will fail since `cwltool`
-does not have enough information to know how to execute it:
+The operation file will fail to run with `cwltool` because `cwltool`
+lacks the necessary information to execute it:
 
 ```{runcmd} cwltool operations.cwl --message Hello
 :working-directory: src/_includes/cwl/operations/