remove non-functioning links

app.py

@@ -47,7 +47,7 @@ with gr.Blocks(title="RFD3 Test") as demo:
                 There are three steps to setting up a job.
                 - First, create an input specification for your generation job. This is a yaml or json file with details on targeted motifs, scaffolds and generation parameters that gets passed to RFD3's CLI as `inputs`. Check out <a href="https://rosettacommons.github.io/foundry/models/rfd3/input.html" target="_blank">RFD3's documentation and tutorials</a> to learn how to compose this file!
                 - Second, upload a PDB file containing your target/scaffold structure to condition the generation or leave empty for unconditional generation.
-                - Third, Select the number of batches and designs per batch for your job. These are passed as CLI arguments to RFD3. Advanced CLI arguments can be added in the "Advanced Options" section. While most of these arguments can be kept at their default value, some  related to the inference sampler can provide improvements for <a href="https://rosettacommons.github.io/foundry/models/rfd3/ppi_design_tutorial.html" target="_blank">protein-protein interaction (PPI) workflows</a>. Here is a list of other <a href="https://rosettacommons.github.io/foundry/models/rfd3/input.html#cli-arguments" target="_blank">CLI arguments</a>.
+                - Third, Select the number of batches and designs per batch for your job. These are passed as CLI arguments to RFD3. Advanced CLI arguments can be added in the "Advanced Options" section. While most of these arguments can be kept at their default value, some  related to the inference sampler can provide improvements for protein-protein interaction (PPI) workflows. Here is a list of other <a href="https://rosettacommons.github.io/foundry/models/rfd3/input.html#cli-arguments" target="_blank">CLI arguments</a>.
 
                 
                 Individual jobs On ZeroGPU spaces are limited to 240 seconds for PRO users or members of an organization. Hence, make sure that you are logged in before launching a job to avoid errors and keep the number of designs per run manageable.