Remove hackmd links

Co-authored-by: Eric Herman  <eric@publiccode.net>

Author: Ainali

activities/communication/community-call-invite-template.md

@@ -24,7 +24,9 @@ If participants can benefit of preparing, mention it as well.]
 
 If you have something else you would like to discuss please let us know, we are happy to make modifications to the agenda.
 
-[Read the full agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?view).
+```
+[Read the full agenda](INSERT LINK).
+```
 
 We look forward to seeing you on the call!
 
@@ -34,6 +36,4 @@ Our next Foundation for Public Code community call will take place at hh.mm on W
 
 If you have something specific you would like to discuss please let us know, we are happy to add items to the agenda.
 
-[Read the full agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?view).
-
 We look forward to seeing you on the call!

activities/communication/running-community-call.md

@@ -17,10 +17,10 @@ The roles on the community call are:
 
 The chair and the notetaker:
 
-* create a notes HackMD.io document for this call
+* create a notes document for this call
 * add "updates since the last community call" to the notes - keep this to three items or fewer (we want the community call to be a dialogue, not a broadcast). If possible, focus on community related updates
 * put these in the call notes doc
-* update the [agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?edit)
+* update the agenda and link it
 * send out invitations ([template](community-call-invite-template.md))
 
 Ask the [communications coordinator](../../organization/staff.md#communications) if you need help with Foundation updates.
@@ -40,8 +40,6 @@ Have each person join the call on a separate connection aligned with our [confer
 
 Call-in link: <https://meet.publiccode.net/FoundationCommunityCall>
 
-Agenda link: <https://hackmd.io/9THmWbpQTLi8L9UIzczSyw>
-
 ### No show
 
 If nobody joins at the call starting time, wait at least 15 minutes before closing the call.

activities/trainings/index.md

@@ -15,7 +15,6 @@ Here is a list of trainings developed or used by the Foundation for Public Code:
 * Rewriting Git History - Amend, Reword, Delete, Reorder, Squash and Split ([video](https://www.youtube.com/watch?v=ElRzTuYln0M), [article](https://www.themoderncoder.com/rewriting-git-history/)) - for making the git history as clear and understandable as possible
 * [Git Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf) - for a list of the most common used git commands
 * [Reviewing contributions](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/)
-* [HackMD.io](https://hackmd.io/) - for collaborating on draft documents in Markdown with people outside the organization (especially helpful for content we plan to publish)
 * [Markdown Here](https://markdown-here.com/) - for formatting emails written using Markdown
 * [Jekyll tutorial](https://jekyllrb.com/docs/step-by-step/01-setup/) - for understanding the templates which underpin our website