diff --git a/NewbieDeveloperSetup.md b/NewbieDeveloperSetup.md
index a909ee7..38ba9fb 100644
--- a/NewbieDeveloperSetup.md
+++ b/NewbieDeveloperSetup.md
@@ -23,12 +23,12 @@ The easiest workflow you can use is by working using Github's [Pull Requests](ht
 
 6. ...
 
-m. Learn to use the [logging system](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/logging.rst)
+m. Learn to use the [logging system]source:trunk/docs/logging.rst
 
 n. Help [reviewing patches](PatchReviewProcess). It is a good way to familiarize yourself with Tahoe-LAFS code and a lot can be learnt from the reviews before writting a single line of code.
 
 o. Learn [how to submit patches](Patches)
 
-p. Dive into the code! See some [tips for diving into Tahoe's source code](https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007337.html) and follow the [coding standards](CodingStandards) when you're ready to code.
+p. Dive into the code! See some [/pipermail/tahoe-dev/2012-May/007337.html tips for diving into Tahoe's source code] and follow the [coding standards](CodingStandards) when you're ready to code.
 
-q. Learn [how to write tests](HowToWriteTests). Patches and new code should pass the automated testing before being eligible to be merged (see [this comment](/tahoe-lafs/trac-2024-07-25/issues/7573)#comment:88). There is a [list of patches needing tests](https://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~test-needed) if you want to get your feet wet.
\ No newline at end of file
+q. Learn [how to write tests](HowToWriteTests). Patches and new code should pass the automated testing before being eligible to be merged (see [this comment](/tahoe-lafs/trac-2024-07-25/issues/7573)#comment:88). There is a [list of patches needing tests]query:status=!closed&keywords=~test-needed if you want to get your feet wet.
\ No newline at end of file