Proof read edits

Signed-off-by: Christopher Hakkaart <[email protected]>

Author: christopher-hakkaart

docs/module.md

@@ -196,14 +196,14 @@ Project L
     └── P2-template.sh
 ```
 
-Projects A contains a workflow that includes processes P1 and P2:
+Project A contains a workflow that includes processes P1 and P2:
 
 ```
 Project A
 └── main.nf
 ```
 
-Pipeline B contains a workflow that also includes process P1 and P2:
+Project B contains a workflow that also includes process P1 and P2:
 
 ```
 Project B
@@ -212,11 +212,11 @@ Project B
 
 As the template files are stored with the modules inside the Project L, Projects A and B can include them without any changing any code. Future projects would also be able to include these modules by cloning Project L and including its module (if they were not available on the system).
 
-Keeping the module template within the script path has several advantages beyond facilitating module sharing across pipelines:
+Beyond facilitating module sharing across pipelines, keeping the module template within the script path has several advantages, including:
 
-1. Modules are self-contained
-2. Modules can be tested independently from the pipeline(s) that import them
-3. Modules can be made into libraries
+- Modules are self-contained.
+- Modules can be tested independently from the pipeline(s) that import them.
+- Modules can be made into libraries.
 
 Organizing templates locations allows for a well-structured project. In projects with multiple modules that rely on templates, you can organize module scripts and their corresponding templates into logical groups. For example:
 
@@ -276,7 +276,7 @@ Binary scripts must be placed in the module directory named `<module-dir>/resour
 Module binary scripts require a local or shared file system for the pipeline work directory, or {ref}`wave-page` when using cloud-based executors.
 :::
 
-Scripts can also be stored at the pipeline level using the `bin` directory. See {ref}`bin directory <bundling-executable>` for more information. 
+Scripts can also be stored at the pipeline level using the `bin` directory. See {ref}`bundling-executables` for more information. 
 
 ## Sharing modules
 

docs/process.md

@@ -112,7 +112,7 @@ workflow {
 ```
 
 :::{tip}
-As the location of the interpreter binary file can differ across platforms. Use `env` to resolve the interpreter's location instead of hard-coding the interpreter path. For example:
+Use `env` to resolve the interpreter's location instead of hard-coding the interpreter path. For example:
 
 ```
 #!/usr/bin/env python
@@ -160,7 +160,7 @@ In the above example, the process will execute one of several scripts depending
 
 ### Template
 
-Process scripts can be externalized to **template** files and accessed using the `template` function in the script section. For example:
+Process scripts can be externalized to **template** files and reused across multiple processes. Templates can be accessed using the `template` function in the script section. For example:
 
 ```nextflow
 process templateExample {
@@ -176,7 +176,7 @@ workflow {
 }
 ```
 
-By default, Nextflow looks for template scripts in the `templates` directory, located alongside the Nextflow script that defines the process. A template can be reused across multiple processes. An absolute path can be used to specify a different template location. However, this practice is discouraged because it hinders pipeline portability. 
+By default, Nextflow looks for template scripts in the `templates` directory, located alongside the Nextflow script that defines the process. An absolute path can be used to specify a different template location. However, this practice is discouraged because it hinders pipeline portability.
 
 Templates can be tested independently of pipeline execution. However, variables prefixed with the dollar character (`$`) are interpreted as Nextflow variables when the template script is executed by Nextflow and Bash variables when executed directly. Consider the following template script:
 

docs/sharing.md

@@ -108,15 +108,15 @@ Executable scripts can be included in the pipeline `bin` directory located at th
 Each script should include a shebang line to specify the interpreter for the script.
 
 :::{tip}
-As the location of the interpreter binary file can differ across platforms. Use `env` to resolve the interpreter's location instead of hard-coding the interpreter path. For example:
+Use `env` to resolve the interpreter's location instead of hard-coding the interpreter path. For example:
 
 ```
 #!/usr/bin/env python
 ```
 
 :::
 
-Scripts placed in the `bin` directory must have executable permissions. Use the `chmod` command to grant the required permissions. For example:
+Scripts placed in the `bin` directory must have executable permissions. Use `chmod` to grant the required permissions. For example:
 
 ```
 chmod a+x bin/custom_script.py