diff --git a/.project b/.project
new file mode 100644
index 0000000000000000000000000000000000000000..22a642a3e40cda48c079041a4a3a83ce08e78535
--- /dev/null
+++ b/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>use-nextflow-nfcore-course</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+	</buildSpec>
+	<natures>
+	</natures>
+</projectDescription>
diff --git a/.settings/org.eclipse.core.resources.prefs b/.settings/org.eclipse.core.resources.prefs
new file mode 100644
index 0000000000000000000000000000000000000000..4824b8026319a8fb303971008a7d59a816d58bd6
--- /dev/null
+++ b/.settings/org.eclipse.core.resources.prefs
@@ -0,0 +1,2 @@
+eclipse.preferences.version=1
+encoding/<project>=UTF-8
diff --git a/FAQ.md b/FAQ.md
index f2e63fa11061d667bcfc5752a5b0ff6d9796ad12..db2e052c2fe06b6071a7e55ba93f99c3e0baeed4 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -25,7 +25,7 @@ You enabled singularity usage but you didn't load singularity module.
 module load system/singularity-3.0.1
 ```
 
-##Files exists but during workflow execution there are not found
+##Files exist but during workflow execution they are not found
 
 ```
 nextflow run nextflow-io/rnaseq
@@ -65,7 +65,7 @@ Work dir:
   /work/pervenche/nextflow-tutorial/work/50/a073c950ec60bc12445e7b54c64568
 ```
 
-If fasta file exist is workdir, thus implies that /work dir is not accessible in singularity image.
-Check config file does input directory is in line `runOptions = '-B /bank -B /work2 -B /save -B /home'`
+If fasta file exists in workdir, thus it implies that /work dir is not accessible in singularity image.
+Check config file : does input directory is in line ? `runOptions = '-B /bank -B /work2 -B /save -B /home'`
 
 Correction : add the directory with -B.
diff --git a/README.md b/README.md
index 9d17029403bb7fad6a601195948f57b1d41687e0..3e62b87816a2b261a61e83cb2c839834d8e5f055 100644
--- a/README.md
+++ b/README.md
@@ -13,12 +13,12 @@
 ## Introduction
 
 
-### What is _nf-core_
-[_nf-core_](https://nf-co.re/) is a community-led project to develop ***a set of best-practice pipelines*** built using Nextflow. A suite of helper tools aim to help people run and develop pipelines. Actually, 25 pipelines are available for different application such as RNAseq, BSseq, Hi-C, annotation ...
+### What is _nf-core_?
+[_nf-core_](https://nf-co.re/) is a community-led project to develop ***a set of best-practice pipelines*** built using Nextflow. A suite of helper tools aims to help people run and develop pipelines. Actually, 25 pipelines are available for different application such as RNAseq, BSseq, Hi-C, annotation ...
 It can be used on any computer or cluster without large prerequisites. It's based on nextflow.
 
 
-### What is Nextflow
+### What is Nextflow?
 [Nextflow](https://www.nextflow.io) is :
 * a programming language that is designed to manage computational workflows
 * and a software that can run a workflow on any infrasctructure.
@@ -26,11 +26,11 @@ It can be used on any computer or cluster without large prerequisites. It's base
 So, it enables scalable and reproducible scientific workflows using software containers.
 Nextflow is developed by the Comparative Bioinformatics group at the Barcelona Centre for Genomic Regulation (CRG).
 
-All workflow software dependancies can be embebed into a container.
+All workflow software dependencies can be embedded into a container.
 
 ![environment](img/environment.png)
 
-### What are containers
+### What are containers?
 A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another.
 [Singularity](https://sylabs.io) and Docker are containers system. On HPC such as Genotoul, you can only use Singularity containers.
 
@@ -55,7 +55,7 @@ One additional tool which this nf-core author swears by is [tldr](https://tldr.s
 
 * ***about nf-core pipelines***
 
-The beauty of _nf-core_ is that there is lots of help on offer! The main place for this is Slack - an instant messaging service. The _nf-core_ Slack organisation has channels dedicated for each pipeline, as well as specific topics (_eg._ `#new-pipelines`, `#tools` and `#aws`).
+The beauty of _nf-core_ is that there are a lot of help on offer! The main place for this is Slack - an instant messaging service. The _nf-core_ Slack organization has channels dedicated for each pipeline, as well as specific topics (_eg._ `#new-pipelines`, `#tools` and `#aws`).
 
 The _nf-core_  Slack can be found at [https://nfcore.slack.com](https://nfcore.slack.com/) (_NB: no hyphen in `nfcore`!_). To join you will need an invite, which you can get at [https://nf-co.re/join/slack](https://nf-co.re/join/slack).
 
diff --git a/doc/slides.odp b/doc/slides.odp
index 631cfba4cbeead650f94ebe35ce91516352a4572..90f0cfe8ab9580486016ea46cd9e7086fd0218fd 100644
Binary files a/doc/slides.odp and b/doc/slides.odp differ
diff --git a/nextflow/NEXTFLOW.md b/nextflow/NEXTFLOW.md
index 9cf73f183b7780a8925ca0506994399a4af9c96b..2a4d4da606a5cfbec4ddb4d5c54aff683aa1a593 100644
--- a/nextflow/NEXTFLOW.md
+++ b/nextflow/NEXTFLOW.md
@@ -9,7 +9,7 @@
 ```
 ssh -X <username>@genologin.toulouse.inrae.fr
 ```
-* Create tutorial working directory and log in a node
+* Create tutorial working directory and log on a node
 ```
 cd work
 mkdir nextflow-tutorial
@@ -44,7 +44,7 @@ module load bioinfo/Nextflow-v20.01.0
 ## Nextflow usage
 ---
 
-The Nextflow command has lot of sub-command to handle workflows. Workflows in Nextflow sub (called projets)
+The Nextflow command has a lot of sub-commands to handle workflows. Workflows in Nextflow sub (called projects)
 ```
 Usage: nextflow [options] COMMAND [arg...]      
 ```
@@ -55,14 +55,14 @@ nextflow help COMMAND
 ```
 
 
-### Exercice 1 :
+### Exercise 1 :
 * Log into a node (with 4G of memory)
 * Create one time only the Nextflow directories with script the `create_nfx_dirs.sh`
 * Follow all the previous instructions to create your running environment.
 * Execute Nextflow without any parameters
 * How many sub command has Nextflow ?
 * Get help on run sub-command.
-* Load Python 3.6.3 to get `tldr` tool and execute it with "nextflow" as parameter.
+* Load Python 3.6.3 module to access `tldr` tool and execute it with "nextflow" as parameter.
 
 [View correction](./correction.md)
 
@@ -83,7 +83,7 @@ Usage: run [options] Project name or repository url
 ![image](../img/nextflow-hyphen.png)
 
 
-### Run a workflow from a file `*.nf`
+### Run a workflow from a file `*.nf`
 
 Copy the content of [tutorial workflow](https://genotoul-bioinfo.pages.mia.inra.fr/use-nextflow-nfcore-course/nextflow/tutorial.nf) into a file named `tutorial.nf`.
 ```nextflow
@@ -110,7 +110,7 @@ process convertToUpper {
 result.view { it.trim() }
 ```
 
-The workflow contains 2 main steps (called process), the first process splits a string into 6-character chunks,
+The workflow contains 2 main steps (called processes), the first process splits a string into 6-character chunks,
 writing each one to a file with the prefix chunk_, and the second receives these
 files and transforms their contents to uppercase letters.
 
@@ -123,16 +123,16 @@ It will output something similar to the text shown below:
 N E X T F L O W  ~  version 19.10.0
 Launching `tutorial.nf` [lonely_fourier] - revision: e3b475a61b
 executor >  local (3)
-[8a/f998c2] process > splitLetters       [100%] 1 of 1 ✔
-[20/6d0533] process > convertToUpper (2) [100%] 2 of 2 ✔
+[8a/f998c2] process > splitLetters       [100%] 1 of 1 ✔
+[20/6d0533] process > convertToUpper (2) [100%] 2 of 2 ✔
 HELLO
 WORLD!
 ```
-You can see that the first process is executed once, and the second twice. Finally the result string is printed.
+You can see that the first process is executed once, and the second twice. Finally, the result string is printed.
 
 It's worth noting that the process convertToUpper is executed in parallel, so there's no guarantee that the instance processing the first split (the chunk Hello) will be executed before the one processing the second split (the chunk world!).
 
-Thus, it is perfectly possible that you will get the final result printed out in a different order:
+Thus, it is possible that you will get the final result printed out in a different order:
 ```
 WORLD!
 HELLO
@@ -156,7 +156,7 @@ drwxr-xr-x 3 pervenche formation 4096 20 janv. 15:08 .nextflow
 ```
 The content of these directories is explained in section [outputs](nextflow/NEXTFLOW.md#nextflow-outputs).
 
-### Pass a value by a parameter
+### Pass a value by a parameter
 
 This workflow has one parameter named `str` (not documented), to change the default value use `--str`
 ```
@@ -167,8 +167,8 @@ It will output something similar to the text shown below:
 N E X T F L O W  ~  version 19.10.0
 Launching `tutorial.nf` [goofy_kilby] - revision: e3b475a61b
 executor >  local (7)
-[ed/5b43df] process > splitLetters       [100%] 1 of 1 ✔
-[6f/51ab49] process > convertToUpper (6) [100%] 6 of 6 ✔
+[ed/5b43df] process > splitLetters       [100%] 1 of 1 ✔
+[6f/51ab49] process > convertToUpper (6) [100%] 6 of 6 ✔
 XTE A
 EN MA
 METTRE
@@ -177,18 +177,18 @@ JUSCUL
 E
 ```
 
-### Resume a workflow
+### Resume a workflow
 
 Nextflow keeps track of all the processes executed in your pipeline.
-With `-resume` option the execution of the processes that are not changed will
+With `-resume` option the execution of the processes that have not changed will
 be skipped and the cached result used instead.
 ```
 $ nextflow run tutorial.nf --str "mon texte a mettre en majuscule" -resume
 
 N E X T F L O W  ~  version 19.10.0
 Launching `tutorial.nf` [scruffy_mccarthy] - revision: e3b475a61b
-[87/29d13f] process > splitLetters       [100%] 1 of 1, cached: 1 ✔
-[b0/ca75e0] process > convertToUpper (6) [100%] 6 of 6, cached: 6 ✔
+[87/29d13f] process > splitLetters       [100%] 1 of 1, cached: 1 ✔
+[b0/ca75e0] process > convertToUpper (6) [100%] 6 of 6, cached: 6 ✔
 XTE A
 METTRE
 MON TE
@@ -203,9 +203,9 @@ All the processes are retrieved from the cached as shown above.
 >* ** nextflow options ** are prefixed by only one `-`
 >* ** workflow parameters ** are prefixed by `--`
 
-### Run a workflow from a repository
+### Run a workflow from a repository
 
-While Nextflow run a pipeline, if the pipeline is not locally available, it is downloaded from a BitBucket, GitHub, and GitLab repositories, more info [here](https://www.nextflow.io/docs/latest/sharing.html).
+While Nextflow run a pipeline, if the pipeline is not locally available, it is downloaded from a BitBucket, GitHub, or GitLab repository, more info [here](https://www.nextflow.io/docs/latest/sharing.html).
 
 ```
 $ nextflow run nextflow-io/rnaseq
@@ -221,7 +221,7 @@ reads : /home/bleuet/.nextflow/assets/nextflow-io/rnaseq/data/ggal/*_{1,2}.fq
 outdir: results
 executor >  local (1)
 executor >  local (1)
-[c8/2153a4] process > buildIndex (ggal_1_48850000_49020000.Ggal71.500bpflank) [100%] 1 of 1, failed: 1 ✘
+[c8/2153a4] process > buildIndex (ggal_1_48850000_49020000.Ggal71.500bpflank) [100%] 1 of 1, failed: 1 ✘
 [-        ] process > mapping                                                 -
 [-        ] process > makeTranscript                                          -
 Error executing process > 'buildIndex (ggal_1_48850000_49020000.Ggal71.500bpflank)'
@@ -257,10 +257,10 @@ module load system/singularity-3.0.1
 nextflow run nextflow-io/rnaseq
 ```
 
-This configuration activate usage of a singularity image. This is explained in next chapter.
+This configuration activates usage of a singularity image. This is explained in next chapter.
 
 
-### How to use slurm ?
+### How to use slurm ?
 
 Nextflow is designed to work on many executors such as SGE, SLURM, ... or
 even on clouds such as Kubernates, Amazon, ...
@@ -273,7 +273,7 @@ process.queue = 'formationq'
 ```
 > Note that formationq is only available during training session. Do not add this line if you are not in a training session.
 
-Run the workflow and check the running process with slurm command `squeue`
+Run the workflow and check the running processes with slurm command `squeue`
 
 ```
 nextflow run nextflow-io/rnaseq
@@ -284,7 +284,7 @@ In another terminal you can check execution:
 squeue -u <username>
 ```
 
-### Exercice 2 :
+### Exercise 2 :
 * Copy content of [this file](https://genotoul-bioinfo.pages.mia.inra.fr/use-nextflow-nfcore-course/nextflow/tutorial.nf) into tutorial.nf.
 * Run tutorial.nf with the workflow parameter `--str`.
 * List content of curent directory with the command `tree`.
@@ -297,7 +297,7 @@ squeue -u <username>
 ## Nextflow run options
 ---
 
-Nextflow run command has lots of options, here are the main usefull options :
+Nextflow run command has a lot of options, here are the main useful ones :
 
 
 * configuration
@@ -309,7 +309,7 @@ Nextflow run command has lots of options, here are the main usefull options :
 * execution
   * `-resume`
     Execute the script using the cached results, useful to continue
-    executions that was stopped by an error
+    executions that were stopped by an error
   * `-w, -work-dir`
     Directory where intermediate result files are stored
 
@@ -318,7 +318,7 @@ Nextflow run command has lots of options, here are the main usefull options :
 
   * `-with-report`
     Create processes execution html report
-    -> really usefull to get excution report on memory and cpu usage in order to calibrate pipeline parameters
+    -> really useful to get execution report on memory and cpu usage in order to calibrate pipeline parameters
 
   * `-with-timeline`
     Create processes execution timeline file
@@ -353,7 +353,7 @@ Nextflow run command has lots of options, here are the main usefull options :
     number)
 
 
-### Exercice 3 :
+### Exercise 3 :
 * Try the following options and explore the new generated files.
 ```
 $ nextflow run nextflow-io/rnaseq -with-timeline -with-trace -with-report -with-dag
@@ -377,11 +377,11 @@ You can change the working directory with the `-work-dir` option.
 
 ```bash
 $ ls -la
-drwxr-xr-x  3 bleuet BIOINFO  4096 23 déc.  12:11 .nextflow        => internal files (eg img singularity)
--rw-r--r--  1 bleuet BIOINFO   108 23 déc.  12:07 nextflow.config  => config file
--rw-r--r--  1 bleuet BIOINFO 10962 23 déc.  12:11 .nextflow.log    => log file with all intermediate directories
-drwxr-xr-x  2 bleuet BIOINFO  4096 23 déc.  12:11 results          => final results
-drwxr-xr-x  8 bleuet BIOINFO  4096 23 déc.  12:10 work             => working and temporary files
+drwxr-xr-x  3 bleuet BIOINFO  4096 23 déc.  12:11 .nextflow        => internal files (eg img singularity)
+-rw-r--r--  1 bleuet BIOINFO   108 23 déc.  12:07 nextflow.config  => config file
+-rw-r--r--  1 bleuet BIOINFO 10962 23 déc.  12:11 .nextflow.log    => log file with all intermediate directories
+drwxr-xr-x  2 bleuet BIOINFO  4096 23 déc.  12:11 results          => final results
+drwxr-xr-x  8 bleuet BIOINFO  4096 23 déc.  12:10 work             => working and temporary files
 ```
 
 ### `results` directory
@@ -389,22 +389,22 @@ Depending on the executed workflow the results files will be differently organis
 
 ### `work` directory
 Each job execution has a sub-directory. If a job fails, you can go into the
- directory and check the executed command. For example, previously a job failed at
+ directory and check the executed command. For example, a job previously failed
  while running the workflow rnaseq without singularity. We can have a look
- to the directory corresponding to the job failed and have access to the
+ to the directory corresponding to the failed job and have access to the
  log and command file.
 
 ```bash
 $ cd /work/bleuet/nextflow-tutorial/work/fe/d0394d6cc75e7f2eaeeaed74ccddb8
 $ ls -la
--rw-r--r-- 1 bleuet BIOINFO    0 23 déc.  15:31 .command.begin
--rw-r--r-- 1 bleuet BIOINFO  129 23 déc.  15:31 .command.err
--rw-r--r-- 1 bleuet BIOINFO  129 23 déc.  15:31 .command.log
--rw-r--r-- 1 bleuet BIOINFO    0 23 déc.  15:31 .command.out
--rw-r--r-- 1 bleuet BIOINFO 2530 23 déc.  15:31 .command.run
--rw-r--r-- 1 bleuet BIOINFO  101 23 déc.  15:31 .command.sh
--rw-r--r-- 1 bleuet BIOINFO    3 23 déc.  15:31 .exitcode
-lrwxrwxrwx 1 bleuet BIOINFO  105 23 déc.  15:31 ggal_1_48850000_49020000.Ggal71.500bpflank.fa -> /work/bleuet/.nextflow/assets/nextflow-io/rnaseq/data/ggal/ggal_1_48850000_49020000.Ggal71.500bpflank.fa
+-rw-r--r-- 1 bleuet BIOINFO    0 23 déc.  15:31 .command.begin
+-rw-r--r-- 1 bleuet BIOINFO  129 23 déc.  15:31 .command.err
+-rw-r--r-- 1 bleuet BIOINFO  129 23 déc.  15:31 .command.log
+-rw-r--r-- 1 bleuet BIOINFO    0 23 déc.  15:31 .command.out
+-rw-r--r-- 1 bleuet BIOINFO 2530 23 déc.  15:31 .command.run
+-rw-r--r-- 1 bleuet BIOINFO  101 23 déc.  15:31 .command.sh
+-rw-r--r-- 1 bleuet BIOINFO    3 23 déc.  15:31 .exitcode
+lrwxrwxrwx 1 bleuet BIOINFO  105 23 déc.  15:31 ggal_1_48850000_49020000.Ggal71.500bpflank.fa -> /work/bleuet/.nextflow/assets/nextflow-io/rnaseq/data/ggal/ggal_1_48850000_49020000.Ggal71.500bpflank.fa
 ```
 
 See the log file to get the execution error `.command.log`.
@@ -417,7 +417,7 @@ available in [singularity page](../singularity/SINGULARITY.md)
 ## Nextflow config
 ---
 
-There is different way to configure nextflow execution: with configuration file or with profiles (defined in configuration).
+There are different ways to configure nextflow execution : with configuration file or with profiles (defined in configuration).
 
 * **With config file**
 
@@ -427,7 +427,7 @@ ones that may appear in the second one)
 1. in current directory (eg file created previously `nextflow.config`)
 2. in workflow directory (eg `~/.nextflow/assets/nextflow-io/rnaseq/nextflow.config`)
 3. in home directory `$HOME/.nextflow/config`
-4. finally if config file is given with `-c <config file>Ì€ , the settings are considered as the first.
+4. finally if config file is given with `-c <config file>Ì€ , the settings are considered as the first.
 
 > If you want to ignore any default configuration files and use only the custom one use the command line option `-C <config file>`.
 
@@ -464,7 +464,7 @@ profiles {
 ```
 
 ---
-## Others Nextflow commands
+## Other Nextflow commands
 
 List main usage of Nextflow thanks to the help `tldr` and execute example commands, listed below.
 
diff --git a/nextflow/correction.md b/nextflow/correction.md
index 19f2ede8ca8a4316df4a53920b1d61ad42609bea..dd89b0017b073619430f0f417efe4a477aa8bb02 100644
--- a/nextflow/correction.md
+++ b/nextflow/correction.md
@@ -1,6 +1,6 @@
 #Tutorial nextflow / Correction
 
-## Exercice 1 :
+## Exercise 1 :
 * Log into a node (with 4G of memory)
 ```
 ssh -X <username>@genologin.toulouse.inrae.fr
@@ -36,11 +36,11 @@ tldr nextflow
 
 
 
-## Exercice 2 :
+## Exercise 2 :
 * Copy content of [this file](https://genotoul-bioinfo.pages.mia.inra.fr/use-nextflow-nfcore-course/nextflow/tutorial.nf) into tutorial.nf.
 * Run tutorial.nf with the workflow parameter `--str`.
 ```
-nextflow run tutorial.nf --str "ceci est un exercice"
+nextflow run tutorial.nf --str "ceci est un Exercise"
 ```
 * List content of curent directory with the command `tree`.
 ```
@@ -48,7 +48,7 @@ tree .
 ```
 * Re-execute the command with the nextflow option `-resume`.
 ```
-nextflow run tutorial.nf --str "ceci est un exercice" -resume
+nextflow run tutorial.nf --str "ceci est un Exercise" -resume
 ```
 * Copy the content of [this file](https://genotoul-bioinfo.pages.mia.inra.fr/use-nextflow-nfcore-course/nextflow/nextflow.config) into a file called `nextflow.config`
 * Load module Singularity
@@ -66,7 +66,7 @@ workflows are in ~/.nextflow/assets. See lines in file `.nextflow.log`
 ls -altr results
 ```
 
-## Exercice 3 :
+## Exercise 3 :
 * Try the following options and explore the new generated files.
 ```
 nextflow run nextflow-io/rnaseq -with-timeline -with-trace -with-report -with-dag
diff --git a/nfcore/NFCORE.md b/nfcore/NFCORE.md
index 5dd9113034f958249a5c0970695bd4b9f50d9a9a..5b3f7d1bc817a674e037e7a9057ec113be3a8afd 100755
--- a/nfcore/NFCORE.md
+++ b/nfcore/NFCORE.md
@@ -7,14 +7,14 @@
 * a helper [tools](../img/nf-core_tools.png) (oriented developpers)
 
 ## Loading environment
-On genologin server, each time you want to use nf-core workflows, you will have to load the following module:
+On genologin server, each time you want to use nf-core workflows, you will have to load one of the following module:
 ```
 $ search_module nfcore
 bioinfo/nfcore-Nextflow-v19.04.0
 bioinfo/nfcore-Nextflow-v20.01.0
 ```
 
-The nf-core module depends on the Nextflow module, you can choose the nexftlow version you want to use.
+The nf-core module depends on the Nextflow module, you can choose the nextflow version you want to use.
 ```
 module load bioinfo/nfcore-Nextflow-v20.01.0
 ```
@@ -22,10 +22,10 @@ module load bioinfo/nfcore-Nextflow-v20.01.0
 This will load :
 * Nextflow module,
 * singularity module,
-* set the path to access to the local singularity images available in to `/usr/local/bioinfo/src/NextflowWorkflows/singularity-img/`
+* set the path to access to the local singularity images available in `/usr/local/bioinfo/src/NextflowWorkflows/singularity-img/`
 
 ## Listing available nf-core pipelines
-As you saw from the `nf-core --help` output, the tool has a range of subcommands. The most useful is `nf-core list`, which lists all available _nf-core_ pipelines. The output shows the latest version number, when it was released. If the pipeline has been pulled locally using Nextflow, it tells you when that was and whether you have the latest version.
+As you saw from the `nf-core --help` output, the tool has a range of subcommands. The most useful is `nf-core list`, which lists all available _nf-core_ pipelines. The output shows the latest version number and when it was released. If the pipeline has been pulled locally using Nextflow, it tells you when that was and whether you have the latest version.
 
 If you supply additional keywords after the command, the listed pipeline will be filtered. Note that this searches more than just the displayed output, including keywords and description text.
 ```
@@ -65,7 +65,7 @@ nf-core/lncpipe    dev        -              -              -
 
 ## Running nf-core pipelines
 ### Software requirements for nf-core pipelines
-In order to run _nf-core_ pipelines, you will need to have Nextflow installed ([https://www.nextflow.io](https://www.nextflow.io/)). The only other requirement is a software packaging tool: [Conda](https://docs.conda.io/en/latest/miniconda.html), [Docker](https://www.docker.com) or [Singularity](https://sylabs.io/singularity/). **On Genotoul, we use Singularity.**
+In order to run _nf-core_ pipelines, you need to have Nextflow installed ([https://www.nextflow.io](https://www.nextflow.io/)). The only other requirement is a software packaging tool: [Conda](https://docs.conda.io/en/latest/miniconda.html), [Docker](https://www.docker.com) or [Singularity](https://sylabs.io/singularity/). **On Genotoul, we use Singularity.**
 
 ### Fetching pipeline code
 Unless you are actively developing pipeline code, we recommend using the Nextflow [built-in functionality](https://www.nextflow.io/docs/latest/sharing.html) to fetch _nf-core_ pipelines. Nextflow will automatically fetch the pipeline code when you run `nextflow run nf-core/PIPELINE`. For the best reproducibility, it is good to explicitly reference the pipeline version number that you wish to use with the `-revision`/`-r` flag. For example:
@@ -100,9 +100,9 @@ Nextflow can load pipeline configurations from multiple locations. To make it ea
 
 1. Pipeline: Default 'base' config
     * Always loaded. Contains pipeline-specific parameters and "sensible defaults" for things like computational requirements
-    * Does _not_ specify any method for software packaging. If nothing else is specified, Nextflow will expect all softwares to be available on the command line.
+    * Does _not_ specify any method for software packaging. If nothing else is specified, Nextflow will expect all software to be available on the command line.
 2. Pipeline: Core config profiles
-    * All _nf-core_ pipelines come with some generic config profiles. The most commonly used ones are for software packaging: `docker`, `singularity` and `conda`
+    * All _nf-core_ pipelines come with some generic config profiles. The most commonly used ones are for software packaging : `docker`, `singularity` and `conda`
     * Other core profiles are `awsbatch`, `debug` and `test`
 3. [nf-core/configs](https://github.com/nf-core/configs): Server profiles
     * At run time, _nf-core_ pipelines fetch configuration profiles from the [configs](https://github.com/nf-core/configs) remote repository. The profiles here are specific to clusters at different institutions. Genotoul profile is available for nf-core pipelines.
@@ -120,16 +120,16 @@ Note that the order in which config profiles are specified matters. Their priori
 
 ### Genotoul profile
 
-We add a genotoul profile in [nf-core configs](https://github.com/nf-core/configs/blob/master/docs/genotoul.md). So to use a nf-core workflow on genotoul facilities just add `-profile genotoul`. This will activate SLURM executor and use singularity with good bind path.
+We add a genotoul profile in [nf-core configs](https://github.com/nf-core/configs/blob/master/docs/genotoul.md). So to use a nf-core workflow on genotoul facilities just add `-profile genotoul`. This will activate SLURM executor and use singularity with good bind paths.
 
 ### Running pipelines with test data
-The `test` config profile is a bit of a special case. Whereas all other config profiles tell Nextflow how to run on different computational systems, the `test` profile configures each `nf-core` pipeline to run without _any_ other command line flags. It specifies URLs for test data and all required parameters. Because of this, you can test any _nf-core_ pipeline with the following command:
+The `test` config profile is a bit of a special case. Whereas all other config profiles tell Nextflow how to run on different computational systems, the `test` profile configures each `nf-core` pipeline to run without _any_ other command line flags. It specifies URLs for test data and all required parameters. Thanks to this, you can test any _nf-core_ pipeline with the following command:
 
 ```bash
 nextflow run nf-core/PIPELINE -profile test,genotoul
 ```
 
-### Exercice 2:
+### Exercise 2:
 
 * Log into a node (with 4G of memory)
 * Run the nf-core/rnaseq pipeline with profiles `genotoul` and `test`
@@ -143,16 +143,16 @@ nextflow run nf-core/PIPELINE -profile test,genotoul
 * Monitor job execution `squeue -u USERNAME`. On which queue the jobs are launched ?
 * Explore result directory `tree results` and check the [output documentation](https://nf-co.re/rnaseq/docs/output) of the pipeline
 * Copy `html` files from `./results/pipeline_info/` to ~/public_html and visit [http://genoweb.toulouse.inra.fr/~USERNAME/](http://genoweb.toulouse.inra.fr/~USERNAME/)
-* Does the memory was sufficiant ? Which process is the longer ? (see execution_report.html)
-* Visit the [nf-core slack](https://nfcore.slack.com/) and check if a channel of the workflow you are interested in is open, check last discussion.
+* Does the memory was sufficient ? Which process is the longer ? (see execution_report.html)
+* Visit the [nf-core slack](https://nfcore.slack.com/) and check if a channel of the workflow you are interested in is open, check last discussions.
 [View correction](./correction.md)
 
 ## Calibrating ressources
 
-Nextflow submit jobs with ressources defined in configuration `base.config` which can be found in ̀`̀~/.nextflow/assets/nf-core/rnaseq/conf/base.config`. It may be possible that jobs are killed due to Exceded memory limit or time limit or that jobs do not run as their required to much ressources. The default configuration can be overloaded with a configuration file.
+Nextflow submit jobs with resources defined in configuration `base.config` which can be found in ̀`̀~/.nextflow/assets/nf-core/rnaseq/conf/base.config`. It may be possible that jobs are killed due to exceeded memory limit or time limit or that jobs do not run as they required to much ressources. The default configuration can be overloaded with a configuration file.
 
 By default, settings of nf-core workflows are fixed with a "retry strategy" depending on return errors.
-In case of the job is killed because it does not have enougth cpu, time or memory you can tell Nextflow to retry with :
+In case of the job is killed because it does not have enough cpu, time or memory you can tell Nextflow to retry with :
 ```
 process {
   errorStrategy = { task.exitStatus in [143,137,104,134,139] ? 'retry' : 'terminate' }
@@ -210,9 +210,9 @@ params {
 }
 ```
 
-The user can overload thoses parameters by creating a file in current directory called `nextflow.config` or by using `-c file.conf` option.
+The user can overload those parameters by creating a file in current directory called `nextflow.config` or by using `-c file.conf` option.
 
-After running for the fisrt time a pipeline, to calibrate memory, cpu or time, we strongly recommand to check html report available in `results/pipeline_info`.
+After running for the fisrt time a pipeline, to calibrate memory, CPU or time, we strongly recommand to check html report available in `results/pipeline_info`.
 
 To do so,
 1. copy the report in your public html and visit the page http://genoweb.toulouse.inra.fr/~USERNAME/report.html
@@ -247,11 +247,11 @@ Then you will be able to use the pipeline's parameters `--genome YOUR-ID`
 
 
 
-### Exercice 3:
+### Exercise 3:
 * Edit nextflow.config and add a genome with path previously provided.
 * Rerun the pipeline with parameter -genome
 
-* For the execice only, edit `~/.nextflow/assets/nf-core/rnaseq/conf/base.config`, change value of memory set 1Gb for high_memory label as shown here:
+* For the exercise only, edit `~/.nextflow/assets/nf-core/rnaseq/conf/base.config`, change value of memory set 1Gb for high_memory label as shown here:
 ```
 process {
   withLabel: high_memory {
@@ -268,7 +268,7 @@ path for this job is `./work/d0/aa323ac54a4eebb11f81e34aceb154/`, path start wit
 
 * rerun rnaseq workflow with option -resume
 
-* How many time does STAR as retried ?
+* How many times does STAR was retried ?
 
 *  Copy `html` files from `./results/pipeline_info/` to ~/public_html and visit [http://genoweb.toulouse.inra.fr/~USERNAME/](http://genoweb.toulouse.inra.fr/~USERNAME/)
 
@@ -277,12 +277,12 @@ path for this job is `./work/d0/aa323ac54a4eebb11f81e34aceb154/`, path start wit
 
 ## Launching main process with a script
 
-Usually, when you will handle a lot of sample, the main Nextflow proccess has to be launched on unilimitq with a least 4G of memory.
+Usually, when you handle a lot of samples, the main Nextflow proccess has to be launched on unlimitq with a least 4G of memory.
 Here is an example of a script `myscript.sh` to launch with sbatch command.
 ```
 #!/bin/bash
 #SBATCH -J nfcore-rnaseq
-#SBATCH -p unlimiq
+#SBATCH -p unlimitq
 #SBATCH --mem=6G
 #SBATCH --mail-type=BEGIN,END,FAIL
 
@@ -351,4 +351,4 @@ Tip: when you have fixed the problem you can continue the execution adding the o
 ## Conclusion
 I hope that this _nf-core_ tutorial has been helpful! Remember that there is more in-depth documentation on many of these topics available on the [nf-core website](https://nf-co.re). If in doubt, please ask for help on [Slack](https://nfcore.slack.com/).
 
-If you have any suggestions for how to improve this tutorial, or spot any mistakes, please create an issue or pull request on the [genotoul-bioinfo repository](https://forgemia.inra.fr/genotoul-bioinfo/use-nextflow-nfcore-course) or fill the [genotoul support form](http://bioinfo.genotoul.fr/index.php/ask-for/support/).
+If you have any suggestion to improve this tutorial, or spot any mistakes, please create an issue or pull request on the [genotoul-bioinfo repository](https://forgemia.inra.fr/genotoul-bioinfo/use-nextflow-nfcore-course) or fill the [genotoul support form](http://bioinfo.genotoul.fr/index.php/ask-for/support/).
diff --git a/nfcore/correction.md b/nfcore/correction.md
index 2cd3520dae5ae5544fbe9a450e08df7a4deff986..2d2113439be55faa839f70f3a0c812bcdd2bf1d9 100755
--- a/nfcore/correction.md
+++ b/nfcore/correction.md
@@ -1,7 +1,7 @@
 #Tutorial nf-core for Genotoul / Correction
 ---
 
-## Exercice 1 :
+## Exercise 1 :
 * Load latest version of nf-core module
 ```
 search_module nfcore
@@ -41,7 +41,7 @@ nextflow info nf-core/methylseq
 ```
 
 
-### Exercice 2:
+### Exercise 2:
 
 * Log into a node (with 4G of memory)
 ```
@@ -80,7 +80,7 @@ nextflow run nf-core/rnaseq -profile genotoul --help
 
 
 
-### Exercice 3:
+### Exercise 3:
 
 * Edit nextflow.config and add a genome with path previously provided.
 
diff --git a/singularity/SINGULARITY.md b/singularity/SINGULARITY.md
index 466254fd41639bb75adce5890b4d9c0bf8b6a51f..de1916bbc37d96e0ae3bb812e6f660bfc2d72d8e 100644
--- a/singularity/SINGULARITY.md
+++ b/singularity/SINGULARITY.md
@@ -5,7 +5,7 @@
 ![image](../img/logo/singularity.png)
 ## Introduction
 
-Nextflow pipelines can run with softwares locally installed
+Nextflow pipelines can run with software locally installed
 but this is not recommended. Most people find either Docker or Singularity
 the best options.
 
@@ -26,7 +26,7 @@ a simple, portable, and reproducible way.
 
 ## Loading singularity module
 
-To search last version of Singularity available on Genologin/Genotoul :
+To search the last version of Singularity available on Genologin/Genotoul :
 ```
 $ search_module Singularity
 system/singularity-2.5.1
@@ -160,4 +160,4 @@ For Docker, the repository of images is the [docker hub](https://hub.docker.com/
 For singularity, the repository is the [singularity hub](https://singularity-hub.org/).
 
 
-> If you want to create it from a recipe you have to do it as root so on your computer.
+> If you want to create it from a recipe you have to do it as root on your computer.