Merge branch 'main' into show-more-of-cwltool

Author: mr-c

src/topics/best-practices.md

@@ -1,4 +1,4 @@
-# Best practices
+# Best Practices
 
 Below are a set of recommended good practices to keep in mind when writing a
 Common Workflow Language description for a tool or workflow. These guidelines

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

@@ -1,4 +1,4 @@
-# Creating files at runtime
+# 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

src/topics/file-formats.md

@@ -1,4 +1,4 @@
-# File formats
+# File Formats
 
 Tools and workflows can take `File` types as input and produce them as output.
 We also recommend indicating the format for `File` types. This helps document

src/topics/metadata-and-authorship.md

@@ -1,4 +1,4 @@
-# Metadata and authorship
+# Metadata and Authorship
 
 Implementation extensions not required for correct execution (for example,
 fields related to GUI presentation) and metadata about the tool or workflow

src/topics/specifying-software-requirements.md

@@ -1,4 +1,4 @@
-# Specifying software requirements
+# Specifying Software Requirements
 
 Often tool descriptions will be written for a specific version of a software. To
 make it easier for others to use your descriptions, you can include a

src/topics/staging-input-files.md

@@ -1,4 +1,4 @@
-# Staging input files
+# Staging Input Files
 
 Normally, input files are located in a read-only directory separate from
 the output directory.  This causes problems if the underlying tool expects to

src/topics/using-containers.md

@@ -1,6 +1,6 @@
-# Using containers
+# Using Containers
 
-## Running tools inside Docker
+## Running Tools Inside Docker
 
 [Docker][docker] containers simplify software installation by providing a
 complete known-good runtime for software and its dependencies.  However,

src/topics/workflows.md

@@ -519,7 +519,7 @@ two-step workflow to a single step subworkflow:
 Now the scatter acts on a single step, but that step consists of two steps so each step is performed
 in parallel.
 
-## Conditional workflows
+## Conditional Workflows
 
 This workflow contains a conditional step and is executed based on the input.
 This allows workflows to skip additional steps based on input parameters given at the start of the program or by previous steps.