Clarifications in hello_nextflow docs

docs/hello_nextflow/01_hello_world.md

@@ -651,7 +651,7 @@ Check the output in the results directory:
 Holà mundo!
 ```
 
-Nextflow used the default value to name the output.
+Nextflow used the default value of the greeting parameter to create the output.
 
 #### 4.2.3. Run the workflow again with the parameter to override the default value
 

docs/hello_nextflow/02_hello_channels.md

@@ -8,7 +8,7 @@
 :fontawesome-brands-youtube:{ .youtube } See the [whole playlist on the Nextflow YouTube channel](https://www.youtube.com/playlist?list=PLPZ8WHdZGxmXiHf8B26oB_fTfoKQdhlik).
 ///
 
-In Part 1 of this course (Hello World), we showed you how to provide a variable input to a process by providing the input in the process call directly: `sayHello(params.greet)`.
+In Part 1 of this course (Hello World), we showed you how to provide a variable input to a process by providing the input in the process call directly: `sayHello(params.greeting)`.
 That was a deliberately simplified approach.
 In practice, that approach has major limitations; namely that it only works for very simple cases where we only want to run the process once, on a single value.
 In most realistic workflow use cases, we want to process multiple values (experimental data for multiple samples, for example), so we need a more sophisticated way to handle inputs.
@@ -651,7 +651,7 @@ _Before:_
 /*
  * Pipeline parameters
  */
-params.greeting = ['Hello','Bonjour','Holà']
+params.greeting = 'Holà mundo!'
 ```
 
 _After:_
@@ -673,6 +673,9 @@ In the workflow block, make the following code change:
 _Before:_
 
 ```groovy title="hello-channels.nf" linenums="31"
+    // declare an array of input greetings
+    greetings_array = ['Hello','Bonjour','Holà']
+
     // create a channel for inputs
     greeting_ch = Channel.of(greetings_array)
                          .flatten()

docs/hello_nextflow/05_hello_containers.md

@@ -650,8 +650,9 @@ You see that the character is saying all the greetings, just as it did when we r
 
 Let's take a look at the work subdirectory for one of the `cowpy` process calls to get a bit more insight on how Nextflow works with containers under the hood.
 
-Check the output from your `nextflow run` command to find the call ID for the `cowpy` process.
-Then navigate to the work subdirectory.
+Check the output from your `nextflow run` command to find the path to the work subdirectory for the `cowpy` process. 
+Looking at what we got for the run shown above, the console log line for the `cowpy` process starts with `[7f/caf718]`. 
+That corresponds to the following truncated directory path: `work/7f/caf718`.
 In it, you will find the `.command.run` file that contains all the commands Nextflow ran on your behalf in the course of executing the pipeline.
 
 Open the `.command.run` file and search for `nxf_launch`; you should see something like this: