diff --git a/content/03.results.md b/content/03.results.md
index 4a083fa0..ebcc3539 100644
--- a/content/03.results.md
+++ b/content/03.results.md
@@ -14,7 +14,7 @@ The contributor formally requested to include their analytical code and results
 All PRs underwent peer review to ensure scientific accuracy, maintainability, and readability of code and documentation (**Figure {@fig:Fig1}C-D**).
 
 Beyond peer review, we implemented additional checks to ensure consistent results for all collaborators over time (**Figure {@fig:Fig1}D**).
-To provide a consistent software development environment, we created a monolithic image with all OpenPBTA dependencies using Docker® [@https://dl.acm.org/doi/10.5555/2600239.2600241] and the Rocker project [@https://doi.org/10.48550/arXiv.1710.03675].
+To provide a consistent software development environment, we created a monolithic image with all OpenPBTA dependencies using Docker® [@https://dl.acm.org/doi/10.5555/2600239.2600241] and the Rocker project [@arxiv:1710.03675].
 We used the continuous integration (CI) service CircleCI® to run analytical code in PRs on a test dataset before formal code review, allowing us to detect code bugs or sensitivity to data release changes.
 
 We followed a similar process in our Manubot-powered [@doi:10.1371/journal.pcbi.1007128] repository for proposed manuscript additions (**Figure {@fig:Fig1}C**); peer reviewers ensured clarity and scientific accuracy, and Manubot performed spell-checking.