We desperately need linting here.. :(

service/ci.md

@@ -93,7 +93,7 @@ not be fully available.
 ## Design
 
 TODO: expand on GitLab CI's design and architecture, following [this
-checklist](https://bluesock.org/~willkg/blog/dev/auditing_projects.html). See also the [Jenkins section](#Jenkins) below for the same
+checklist](https://bluesock.org/~willkg/blog/dev/auditing_projects.html). See also the [Jenkins section](#jenkins) below for the same
 thing about Jenkins.
 
 ## Issues
@@ -121,7 +121,7 @@ stuff?
 
 This service requires no backups: all configuration should be
 performed by Puppet and/or documented in this wiki page. A lost runner
-should be rebuilt from scratch, as per [disaster recover](#Disaster recovery).
+should be rebuilt from scratch, as per [disaster recover](#disaster-recovery).
 
 ## Other documentation
 
@@ -311,7 +311,7 @@ approach was briefly [discussed in the LDAP audit][LDAP proposed solutions secti
 idea would be to replace the "SSH + role user" approach we currently
 use for service with GitLab CI.
 
-As explained in the [goals](#Goals) section above, this is currently out of
+As explained in the [goals](#goals) section above, this is currently out of
 scope, but could be considered instead of Docker for runners. 
 
 ### Jenkins