diff --git a/README.md b/README.md
index 473fe56c974fad8f568f9adbcb6b0a0968e5c0ec..1445b36145c6506910f2e40d81d2ec9fcae0d624 100644
--- a/README.md
+++ b/README.md
@@ -3,8 +3,6 @@
 [![pipeline status](https://gitlab.pasteur.fr/hub/cc-qtl-db/badges/dev/pipeline.svg)](https://gitlab.pasteur.fr/hub/cc-qtl-db/commits/dev)
 [![coverage report](https://gitlab.pasteur.fr/hub/cc-qtl-db/badges/dev/coverage.svg)](https://gitlab.pasteur.fr/hub/cc-qtl-db/commits/dev)
 
-<!-- Take a look at its [wiki](https://gitlab.pasteur.fr/hub/cc-qtl-db/wikis/home) -->
-
 [[_TOC_]]
 
 ## Introduction
@@ -336,7 +334,7 @@ The analysis parameters, however, are not compatible with two-way RIL (namely, a
 
 One key feature of CC-QTL is that given its database structure, it is thought in such a way that phenotypic data can be acquired for multiple traits, over different experiments performed by different users, with the objective in the long run to assess traits correlations. That requires the mouse genotypes to be reproducible, which is the case for CC lines, but not for DO lines, another mouse multiparental mapping population deriving from the same 8 founder lines than the CC, in which by design each line has a unique genetic makeup which cannot be reproduced.
 
-Ongoing work on CC-QTL (medium term objective) is to extend it to so-called CC-RIX, which are intercrosses between CC lines. CC-RIX are genetically reproducible like CCs, yet benefit from the buffering effect of heterozygosity and allow to assess parental effects.
+Ongoing work on CC-QTL is to extend it to so-called CC-RIX, which are intercrosses between CC lines. CC-RIX are genetically reproducible like CCs, yet benefit from the buffering effect of heterozygosity and allow to assess parental effects.
 
 ### How can I install the analysis workflow on Galaxy ?
 
@@ -344,7 +342,7 @@ We made the analysis workflow Galaxy-powered to both guarantee reproducibility a
 
 In case you are solely interested in deploying and running CC-QTL locally on your computer, eg for test purposes, nothing is required from your side else than following the installation instructions, as the Docker will deploy a local Galaxy along with all the interface components.
 
-If you want, however, to install it on a pre-existing Galaxy instance (eg, Galaxy instance from your institute): you can do so using the [wrappers](path to wrappers) we use on the Galaxy@Pasteur instance. The current version of CC-QTL is indeed not yet compatible for an installation using the Galaxy Toolshed (this will be the case from the next release onwards).
+If you want, however, to install it on a pre-existing Galaxy instance (eg, Galaxy instance from your institute): you can do so using the [wrappers](https://gitlab.pasteur.fr/galaxy-team/galaxy-tools/-/tree/master/tools/cc_qtl) we use on the Galaxy@Pasteur instance. The current version of CC-QTL is indeed not yet compatible for an installation using the Galaxy Toolshed, this will be the case from the next release onwards.
 
 Keep in mind, though, that by using CC-QTL directly through Galaxy, you will get the analysis workflow yet not the database, nor the interface ; thus not benefiting from all the functionalities of CC-QTL (eg plots).