Merge pull request #493 from cbrueffer/cb-fixes

Various fixes

Author: mribeirodantas

docs/basic_training/channels.md

@@ -331,7 +331,7 @@ It will produce an output similar to the following:
 
 !!! warning
 
-    The glob pattern _must_ contain at least a star wildcard character (`*`).
+    The glob pattern _must_ contain at least an asterisk wildcard character (`*`).
 
 The `fromFilePairs` channel factory also has options to help you control its behaviour:
 
@@ -431,7 +431,7 @@ Channel
 
     Read pairs are implicitly managed and are returned as a list of files.
 
-It’s straightforward to use this channel as an input using the usual Nextflow syntax
+It’s straightforward to use this channel as an input using the usual Nextflow syntax.
 
 The code below creates a channel containing two samples from a public SRA study and runs `FASTQC` on the resulting files. See:
 

docs/basic_training/operators.md

@@ -170,7 +170,7 @@ z
 
 !!! warning
 
-    The items in the resulting channel have the same order as in the respective original channels. However, there is no guarantee that the element of the second channel are appended after the elements of the first. Indeed, in the example above, the element `a` has been printed before `3`.
+    The items in the resulting channel have the same order as in the respective original channels. However, there is no guarantee that the elements of the second channel are appended after the elements of the first. Indeed, in the example above, the element `a` has been printed before `3`.
 
 ### `flatten()`
 
@@ -390,7 +390,7 @@ The `splitCsv` operator allows you to parse text items emitted by a channel, tha
 
 It then splits them into records or groups them as a list of records with a specified length.
 
-In the simplest case, just apply the `splitCsv` operator to a channel emitting a CSV formatted text files or text entries. For example, to view only the first and fourth columns:
+In the simplest case, just apply the `splitCsv` operator to a channel emitting a CSV formatted text file or text entries. For example, to view only the first and fourth columns:
 
 ```groovy linenums="1" title="snippet.nf"
 Channel

docs/basic_training/processes.md

@@ -197,7 +197,7 @@ Your expected output will look something like this:
 The current directory is /workspace/gitpod/nf-training/work/7a/4b050a6cdef4b6c1333ce29f7059a0
 ```
 
-However, this using the single quotes (`'`) will block the usage of Nextflow variables in the command script.
+However, using the single quotes (`'`) will block the usage of Nextflow variables in the command script.
 
 Another alternative is to use a `shell` statement instead of `script` and use a different syntax for Nextflow variables, e.g., `!{..}`. This allows the use of both Nextflow and Bash variables in the same script.
 
@@ -540,7 +540,7 @@ workflow {
 3 and a
 ```
 
-As `ch2` is now a _value_ channel, it can be consumed multiple times and do not affect process termination.
+As `ch2` is now a _value_ channel, it can be consumed multiple times and does not affect process termination.
 
 !!! question "Exercise"
 
@@ -760,7 +760,7 @@ Some caveats on glob pattern behavior:
 
 - Input files are not included in the list of possible matches
 - Glob pattern matches both files and directory paths
-- When a two stars pattern `**` is used to recourse across directories, only file paths are matched i.e., directories are not included in the result list.
+- When a two asterisks pattern `**` is used to recourse across directories, only file paths are matched i.e., directories are not included in the result list.
 
 !!! question "Exercise"
 
@@ -1141,7 +1141,7 @@ workflow {
 }
 ```
 
-The above example will copy all blast script files created by the `BLASTSEQ` process into the directory path `results`.
+The above example will copy all BAM files created by the `FOO` process into the directory path `results`.
 
 !!! tip