From 594c47af6943651cefa30f2d71a2b9fd5f7fd120 Mon Sep 17 00:00:00 2001 From: Brant Faircloth Date: Fri, 25 Aug 2023 13:26:42 -0500 Subject: [PATCH] update internal links again --- docs/tutorials/tutorial-1.rst | 2 +- docs/tutorials/tutorial-3.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorials/tutorial-1.rst b/docs/tutorials/tutorial-1.rst index dc0aaf0..d514202 100644 --- a/docs/tutorials/tutorial-1.rst +++ b/docs/tutorials/tutorial-1.rst @@ -485,7 +485,7 @@ There are many, many other assembly QC steps you can run other than simply looking at the stats of the assembled contigs. We will not go into those here. -.. _FindingUCELoci: +.. _finding-uce-loci: Finding UCE loci ================ diff --git a/docs/tutorials/tutorial-3.rst b/docs/tutorials/tutorial-3.rst index ab4ca4e..e088849 100644 --- a/docs/tutorials/tutorial-3.rst +++ b/docs/tutorials/tutorial-3.rst @@ -402,8 +402,8 @@ The easiest way for you to use the extracted sequences is to basically pretend like they are "newly assembled contigs" and place the fasta files (`allmis2.fasta` as in the above) into a `contigs` directory. Alternatively, you can symlink them into a new or existing `contigs` folder (that resulted from a PHYLUCE_ assembly -process) and then proceed with the :ref:`FindingUCELoci` procedure. +process) and then proceed with the :ref:`finding-uce-loci` procedure. .. attention:: Although we have already extracted the UCE loci from each genome sequence and even though it seems redundant to go back through the - :ref:`FindingUCELoci` process, this is the best path forward. + :ref:`finding-uce-loci` process, this is the best path forward.