From 3907181b6fe9f70bb82ffcec08b7bdf9cda972c9 Mon Sep 17 00:00:00 2001
From: Laurent Modolo <laurent.modolo@ens-lyon.fr>
Date: Fri, 16 Apr 2021 09:44:26 +0200
Subject: [PATCH] CONTRIBUTING.md: fix typo

---
 CONTRIBUTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index eb2c2500..3d74be83 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -205,10 +205,10 @@ You can the use tests on `read.size()` to define conditional `script` block:
 
 ### Complex processes
 
-Sometime you want to do write complexe processes, for example for `fastp` we want to have predefine `fastp` process for different protocols, order of adapter trimming and reads clipping.
+Sometime you want to do write complex processes, for example for `fastp` we want to have predefine `fastp` process for different protocols, order of adapter trimming and reads clipping.
 We can then use the fact that `process` or named `workflow` can be interchangeably imported with th [DSL2](https://www.nextflow.io/docs/latest/dsl2.html#workflow-composition).
 
-With the following example, the user can simply include the `fastp` step without knowing that it's a named `workflow`instead of a `process`.
+With the following example, the user can simply include the `fastp` step without knowing that it's a named `workflow` instead of a `process`.
 By specifying the `params.fastp_protocol`, the `fastp` step will transparently switch betwen the different `fastp` `process`es.
 Here `fastp_default` or `fastp_accel_1splus`, and other protocols can be added later, pipeline will be able to handle these new protocols by simply updating from the `upstream` repository without changing their codes.
 
-- 
GitLab