From 181039afdf80abb1ebc808908e2cf07935b85992 Mon Sep 17 00:00:00 2001
From: Anabella Trigila <18577080+atrigila@users.noreply.github.com>
Date: Tue, 12 Nov 2024 14:43:08 -0300
Subject: [PATCH] Update docs/usage.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Nicolás Schcolnicov <90359308+nschcolnicov@users.noreply.github.com>
---
 docs/usage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/usage.md b/docs/usage.md
index 3549542a..c525e7b4 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -47,7 +47,7 @@ If MirGeneDB should be used instead it needs to be specified using `--mirgenedb`
 
 See examples in: [the test-datasets repository of nf-core](https://github.com/nf-core/test-datasets/tree/smrnaseq/MirGeneDB).
 
-> [!NOTE] > `mirtop` is hard-coded to use the `pre` sequences rather than `pri`. Users must provide `pre` files from the start to ensure consistency between the FASTA and GFF files, as the coordinates in the GFF file are referenced to `pre` sequences. This also ensures that names in the BAM file will match those in the GFF.
+> [!NOTE] > `mirtop` is hard-coded to use the `pre` sequences, which originate from the hairpin FASTA, rather than the `pri` sequences, which come from the mature FASTA. Users must provide `pre` files from the start to ensure consistency between the FASTA and GFF files, as the coordinates in the GFF file are referenced to `pre` sequences. This also ensures that names in the BAM file will match those in the GFF.
 
 ### Genome