From 845bfc6fe9f52a4df8679f6217c62294c85ce83f Mon Sep 17 00:00:00 2001
From: Victor Lin <13424970+victorlin@users.noreply.github.com>
Date: Thu, 10 Oct 2024 12:41:57 -0700
Subject: [PATCH] Fix broken link to influenza naming conventions

The old link returned 404 with a client-side redirection to the new
link.
---
 .../creating-a-pathogen-repo/creating-an-ingest-workflow.rst    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/tutorials/creating-a-pathogen-repo/creating-an-ingest-workflow.rst b/src/tutorials/creating-a-pathogen-repo/creating-an-ingest-workflow.rst
index 6cad602b..22e7dfce 100644
--- a/src/tutorials/creating-a-pathogen-repo/creating-an-ingest-workflow.rst
+++ b/src/tutorials/creating-a-pathogen-repo/creating-an-ingest-workflow.rst
@@ -414,7 +414,7 @@ If you write a custom script that follows the same pattern, you can add your scr
 curation pipeline before the final ``augur curate apply-record-annotations`` command.
 
 A typical pathogen-specific step for curation is the standardization of strain names since pathogens usually have different naming conventions
-(e.g. `influenza <https://www.cdc.gov/flu/about/viruses/types.htm>`_ vs `measles <https://www.cdc.gov/measles/php/laboratories/genetic-analysis.html#cdc_generic_section_3-guidelines-for-naming-measles-strains-or-sequences>`_).
+(e.g. `influenza <https://www.cdc.gov/flu/about/viruses-types.html>`_ vs `measles <https://www.cdc.gov/measles/php/laboratories/genetic-analysis.html#cdc_generic_section_3-guidelines-for-naming-measles-strains-or-sequences>`_).
 For example, we've added a step in the curation pipeline to normalize the strain names for the `Zika ingest workflow <https://github.com/nextstrain/zika/tree/main/ingest>`_.
 
 1. We added a `custom Python script <https://github.com/nextstrain/zika/blob/a91e575bff38f154390c9eb11a44a89abf95a55b/ingest/bin/fix-zika-strain-names.py>`_