service/donate.md

@@ -416,7 +416,7 @@ the tunnel:
     ipsec up civicrm::crm-int-01
 
 If still unsuccessful, check the output from that command, or logs from
-strongSwan. See also the [IPsec documentation](howto/ipsec) for more
+strongSwan. See also the [IPsec documentation](service/ipsec) for more
 troubleshooting tricks.
 
 If the tunnel is up, you can check that you can reach the service from the
@@ -517,7 +517,7 @@ The donation site is built of two main parts:
 [donate-neo]: https://gitlab.torproject.org/tpo/web/donate-neo
 
 Those two are interconnected with a Redis server protected by an
-[IPsec](howto/ipsec) tunnel.
+[IPsec](service/ipsec) tunnel.
 
 The documentation here covers only the frontend, and barely the Redis
 tunnel. 
@@ -571,7 +571,7 @@ are sent to `donate-neo`. In early design discussions between @mathieu and @kez,
 this data was intended to be retrieved via straightforward HTTP requests to
 CiviCRM's API. However, this turned out to be at cross-purposes with the server
 architecture design, in which communication between the Django server and the
-CiviCRM server would only occur via [IPsec](howto/ipsec) tunnel. 
+CiviCRM server would only occur via [IPsec](service/ipsec) tunnel. 
 
 As a result, perk and donation minimum data is exported from CiviCRM and stored
 in the `donate-neo` repository as a JSON file. (Note that as of this writing,
@@ -772,7 +772,7 @@ users or administrators.
 
 The public has access to the `donate` Django app, but not the
 backend CiviCRM server. The app and the CiviCRM server talk to each
-other through a Redis instance, accessible only through an [IPsec](howto/ipsec)
+other through a Redis instance, accessible only through an [IPsec](service/ipsec)
 tunnel (as a 172.16/12 private IP address).
 
 In order to receive contribution data and provide endpoints reachable
@@ -1188,7 +1188,7 @@ The old donate site was built on a server named
      * those sites live in `/srv/donate.torproject.org`
 
 There was also the <https://donate.torproject.org> static site hosted
-in our [static hosting mirror network](howto/static-component). A donation campaign had to
+in our [static hosting mirror network](service/static-component). A donation campaign had to
 be setup both inside the static site and CiviCRM.
 
 #### Authentication
@@ -1204,7 +1204,7 @@ In other words, the `donate-api` PHP app was the component that allows
 communications between the `donate.torproject.org` site and
 CiviCRM. The public has access to the `donate-api` app, but not the
 backend CiviCRM server. The middle and the CiviCRM server talk to each
-other through a Redis instance, accessible only through an [IPsec](howto/ipsec)
+other through a Redis instance, accessible only through an [IPsec](service/ipsec)
 tunnel (as a 172.16/12 private IP address).
 
 In order to receive contribution data and provide endpoints reachable