This brings us closer to having a test of mdlintall that's happy -- but
not 100%: there's still errors about checkboxes that look like links and
confuses mdl

doc/svn-accounts.md

@@ -2,7 +2,13 @@
 title: Getting an SVN account
 ---
 
-We still use SVN in some places. All public SVN repositories are available at [svn.torproject.org](https://svn.torproject.org). We host our presentations, check.torproject.org, website, and an number of older codebases in it.  The most frequently updated directories are the website and presentations. SVN is not tied to LDAP in any way.
+# SVN accounts
+
+We still use SVN in some places. All public SVN repositories are available at
+[svn.torproject.org](https://svn.torproject.org). We host our presentations,
+check.torproject.org, website, and an number of older codebases in it.  The most
+frequently updated directories are the website and presentations. SVN is not
+tied to LDAP in any way.
 
 ## SVN Repositories available
 
@@ -26,7 +32,9 @@ The following SVN repositories are available:
  1. Open a [trac ticket](https://bugs.torproject.org/) per user account desired.
  2. The user needs to pick a username and which repository to access (see list above)
  3. SVN access requires output from the following command:
- > htdigest -c password.tmp "Tor subversion repository" <username>
- 4. The output should be mailed to the subversion service maintainer (See [Infrastructure Page on trac](https://gitlab.torproject.org/legacy/trac/-/wikis/org/operations/Infrastructure)) with Trac ticket reference contained in the email.
+    > htdigest -c password.tmp "Tor subversion repository" <username>
+ 4. The output should be mailed to the subversion service maintainer (See
+    [Infrastructure Page on trac](https://gitlab.torproject.org/legacy/trac/-/wikis/org/operations/Infrastructure))
+    with Trac ticket reference contained in the email.
  5. The user will be added and emailed when access is granted.
  6. The trac ticket is updated and closed.