Update link to blog

Updated outdated blog link.

Signed-off-by: Justine Geffen <[email protected]>

platform_versioned_docs/version-23.4/launch/advanced.mdx

@@ -44,7 +44,7 @@ reports:
 You can run custom code either before or after the execution of the Nextflow script. These fields allow you to enter shell commands.
 
 Pre-run scripts are executed in the nf-launch script prior to invoking Nextflow processes. Pre-run scripts are useful for:
-- Specifying an alternate Nextflow version to use for the run. For example, use `export NXF_VER=24.04.2` to take advantage of [new Nextflow features](https://nextflow.io/blog/2024/nextflow-2404-highlights.html) before a Platform version is released with 24.04.2 as its baseline. 
+- Specifying an alternate Nextflow version to use for the run. For example, use `export NXF_VER=24.04.2` to take advantage of [new Nextflow features](https://seqera.io/blog/nextflow-24.04-highlights/) before a Platform version is released with 24.04.2 as its baseline. 
 - Executor setup, such as loading a private CA certificate.
 - Troubleshooting. For example, add `sleep 3600` to your pre-run script to instruct Nextflow to wait 3600 seconds (60 minutes) before process execution after the nf-launcher container is started, to create a window in which to test connectivity and other issues before your Nextflow processes execute.