service/ci.md

 [Continuous Integration](https://en.wikipedia.org/wiki/Continuous_integration) is the system that allows tests to be ran
 and packages to be built, automatically, when new code is pushed to
-the version control system (currently [git](howto/gitolite)).
+the version control system (currently [git](service/gitolite)).
 
-Note that the CI system is implemented with [GitLab](howto/gitlab),
+Note that the CI system is implemented with [GitLab](service/gitlab),
 which has its own documentation. This page, however, documents the
 GitLab CI things specific to TPA.
 
@@ -285,7 +285,7 @@ adjusted to cache less.
 
 Similar to the above, but typically happens on the GitLab
 server. Documented in the GitLab documentation, see [Disk full on
-GitLab server](howto/gitlab#disk-full-on-gitlab-server).
+GitLab server](service/gitlab#disk-full-on-gitlab-server).
 
 ### DNS resolution failures
 
@@ -955,7 +955,7 @@ preferred CI tool.
 
 ## Overview
 
-Ever since the [GitLab migration](howto/gitlab), we have discussed the
+Ever since the [GitLab migration](service/gitlab), we have discussed the
 possibility of replacing Jenkins with GitLab CI, or at least using
 GitLab CI in some way.
 
@@ -1020,7 +1020,7 @@ in the longer term, Jenkins itself.
    deployment, but it is considered out of scope for now. see also the
    [LDAP proposed solutions section][]
 
-[LDAP proposed solutions section]: howto/ldap#Proposed-Solution
+[LDAP proposed solutions section]: service/ldap#Proposed-Solution
 
 ## Approvals required