Improvements-to-the-donation-process.md

@@ -217,13 +217,13 @@ Conclusions:
     awareness.
 
   * We should write a newsletter to donors half-way through the year or when we
-    have major improvements. ([[!tails_ticket fundraising#17703]])
+    have major improvements. (fundraising#17703)
 
   * Adding an opt-in mechanism for our newsletter would allow us to be less shy
-    to write them. ([[!tails_ticket fundraising#17702]])
+    to write them. (fundraising#17702)
 
   * LimeSurvey is more convenient to send mass emails to donors.
-    ([[!tails_ticket fundraising#17704]])
+    (fundraising#17704)
 
   * We should communicate more about the impact of donations and how we spend
     the money.
@@ -238,10 +238,10 @@ Conclusions:
     - Protection from oppressive governments and persecution (18)
     - Liberty and freedom of speech (16)
 
-<h1 id="donate">Improve /donate ([[!tails_ticket 17697]])</h1>
+<h1 id="donate">Improve /donate (#17697)</h1>
 
 Since we won't do usability tests and to avoid a situation à la
-[[!tails_ticket 16830]], we will limit our changes to:
+#16830, we will limit our changes to:
 
 * Things we agree on easily
 * Research-based recommendations from experts
@@ -253,7 +253,7 @@ Ideas:
 * Improve "How we spend our money" to tell more about the impact.
 * Improve the headline.
 
-<h1 id="thanks">Rewrite /donate/thanks and /donate/canceled ([[!tails_ticket 17701]])</h1>
+<h1 id="thanks">Rewrite /donate/thanks and /donate/canceled (#17701)</h1>
 
 These pages look crap and we don't spend time on them because we don't
 see them ourselves. But I think that they are critical and low-hanging
@@ -272,11 +272,11 @@ improvements while keeping them cheap.
 
 <h1 id="ab">A/B testing during the campaign (if needed)</h1>
 
-Like I did for [[!tails_ticket 16830]], we could do more such things
+Like I did for #16830, we could do more such things
 during the campaign. For example, we could test different images, text,
 or controversial changes.
 
-<h1 id="buttons">Analyze the results of the A/B testing on frequency buttons ([[!tails_ticket 16830]])</h1>
+<h1 id="buttons">Analyze the results of the A/B testing on frequency buttons (#16830)</h1>
 
 Compare the conversion rates between Tor Browser, Tails, and mobile.
 I'll be analyzing logs when looking at the results of the A/B testing on