convert.py, markdown: Fix trailing whitespaces.

Many lines have 2 spaces at the end.

An example is the 'Location: [G5, Hall 3, Level 0][4] ' line inside
the markdown/2023_12_replicant-37c3.md file.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

23 files changed, 62 insertions, 62 deletions

diff --git a/markdown/2011_03_new-replicant-test-images-available.md b/markdown/2011_03_new-replicant-test-images-available.md
index 7b3acd5..0694abb 100644
--- a/markdown/2011_03_new-replicant-test-images-available.md
+++ b/markdown/2011_03_new-replicant-test-images-available.md
@@ -5,7 +5,7 @@ authors: admin
 ---
 Hello Replicants!
 
-We have [new Replicant test images][1].  
+We have [new Replicant test images][1].
 We would like to know if phone calls work in the USA on the Nexus One and the
 HTC Dream. Help us testing!
 
diff --git a/markdown/2011_04_replicant-2-2-sdk-available.md b/markdown/2011_04_replicant-2-2-sdk-available.md
index db31843..10cd06b 100644
--- a/markdown/2011_04_replicant-2-2-sdk-available.md
+++ b/markdown/2011_04_replicant-2-2-sdk-available.md
@@ -4,7 +4,7 @@ title: Replicant 2.2 SDK available
 authors: admin
 ---
 Thanks to the huge amount of work by paulk (Paul Kocialkowski) we now have an
-SDK.  
+SDK.
 It should be functional enough to write android applications for Replicant 2.2
 or any other Android 2.2 device.
 
diff --git a/markdown/2012_02_wiki-and-tracker-are-now-powered-by-redmine.md b/markdown/2012_02_wiki-and-tracker-are-now-powered-by-redmine.md
index 4f65b59..4fe740e 100644
--- a/markdown/2012_02_wiki-and-tracker-are-now-powered-by-redmine.md
+++ b/markdown/2012_02_wiki-and-tracker-are-now-powered-by-redmine.md
@@ -4,7 +4,7 @@ title: Wiki and tracker are now powered by Redmine
 authors: Paul Kocialkowski
 ---
 Replicant web services are kindly hosted by the Oregon State University Open
-Source Lab.  
+Source Lab.
 Recently, they asked us to consider switching from trac, which was powering
 our wiki and tracker, to redmine, another engine providing the same services.
 The reason is that redmine is easier to manage for them than trac. As a
diff --git a/markdown/2012_04_nexus-sgalaxy-s-privacy-issues.md b/markdown/2012_04_nexus-sgalaxy-s-privacy-issues.md
index 979ed6c..8fc5f4c 100644
--- a/markdown/2012_04_nexus-sgalaxy-s-privacy-issues.md
+++ b/markdown/2012_04_nexus-sgalaxy-s-privacy-issues.md
@@ -5,7 +5,7 @@ title: Nexus S/Galaxy S privacy issues
 authors: GNUtoo
 ---
 We found out that on the Nexus S and the Galaxy S the modem could possibly spy
-the main CPU(where Replicant runs).  
+the main CPU(where Replicant runs).
 We are currently trying to see if that can be fixed(by loosing about 80M of
 ram) or not.
 
diff --git a/markdown/2012_09_replicant-2-3-0004-images-release.md b/markdown/2012_09_replicant-2-3-0004-images-release.md
index d370c8a..ffa5606 100644
--- a/markdown/2012_09_replicant-2-3-0004-images-release.md
+++ b/markdown/2012_09_replicant-2-3-0004-images-release.md
@@ -4,7 +4,7 @@ title: Replicant 2.3 0004 images release
 authors: Paul Kocialkowski
 ---
 Even though we didn't update the homepage for a long time, we are still
-actively working!  
+actively working!
 Lately, a big part of the work was focused on adding support for the upcoming
 [Goldelico GTA04][1]. We strongly encourage the use of the [GTA04][1] since it
 features nearly-zero known freedom issues (the only exception being that the
diff --git a/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md b/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
index 12c0573..532bf26 100644
--- a/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
+++ b/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
@@ -12,7 +12,7 @@ very powerful. This is mostly the case of vendor-specific USSD codes (that are
 not included in Replicant), which could erase the phone's user data.
 
 What's also problematic about this is that web pages can trigger such intents
-(through an iframe with the `tel:` prefix for instance).  
+(through an iframe with the `tel:` prefix for instance).
 Since this vulnerability was present in our Replicant images (although the
 damage was reduced as we don't include vendor-specific USSD codes), we decided
 to include the fix in our code base and release new images. That's nearly the
diff --git a/markdown/2013_07_announcing-the-free-software-foundation-fundraising-program-for-replicant.md b/markdown/2013_07_announcing-the-free-software-foundation-fundraising-program-for-replicant.md
index 460a4b0..aea51cc 100644
--- a/markdown/2013_07_announcing-the-free-software-foundation-fundraising-program-for-replicant.md
+++ b/markdown/2013_07_announcing-the-free-software-foundation-fundraising-program-for-replicant.md
@@ -16,7 +16,7 @@ to work on, based on how much they respect freedom, so we might decline some
 offers.
 
 You might want to consider making a donation to our project, any amount will
-help, from the [FSF directed donations page for Replicant][3].  
+help, from the [FSF directed donations page for Replicant][3].
 Bitcoin donations are also accepted, at the following address:
 `13tgjejUJ6NtQVX9HvKz8svdcuWPNwgr5T`
 
diff --git a/markdown/2013_11_fairphone.md b/markdown/2013_11_fairphone.md
index 9416bfe..cb8524c 100644
--- a/markdown/2013_11_fairphone.md
+++ b/markdown/2013_11_fairphone.md
@@ -10,7 +10,7 @@ aspects that the [Fairphone][1] company took care of: such topics as using
 fair and conflict-free resources, ensuring that all workers along the supply
 chain get a fair wage, improving the handling of electronic waste, being
 transparent about the cost of each part of the device, its technical
-specifications and encouraging open and flexible designs.  
+specifications and encouraging open and flexible designs.
 We are really glad to see a company producing electronic devices taking care
 of such many important aspects as social conditions of workers, ecology and
 handling of e-waste as well as transparency and being “technically open”.
@@ -38,7 +38,7 @@ side, some of the libraries that deal with the hardware have been released as
 free software for devices that use the same platform (Mediatek 6589), so the
 basic required features such as audio will likely work. We are also confident
 we will be able to handle the modem with free software (that means telephony
-and such will work).  
+and such will work).
 [Fairphone][1] is really trying hard to get Mediatek to release as many
 components as free software as possible, but they don't have the source in
 their own hands and nor can they decide to make it free software themselves,
@@ -56,7 +56,7 @@ for the phone to be converted to a remote spying device.
 In conclusion, we think it will be possible to have Replicant working on the
 [Fairphone][1] and the bootloaders (that are not part of the operating system)
 may even be free software, but we believe it is seriously compromised
-security-wise because of the poor modem isolation.  
+security-wise because of the poor modem isolation.
 However, [Fairphone][1] seems definitely interested in doing things right on
 the software freedom side and helping us get Replicant running on the device!
 
diff --git a/markdown/2014_06_replicant-at-the-15th-libre-software-meeting-in-montpellier-france-this-july.md b/markdown/2014_06_replicant-at-the-15th-libre-software-meeting-in-montpellier-france-this-july.md
index 7df464d..a9f9648 100644
--- a/markdown/2014_06_replicant-at-the-15th-libre-software-meeting-in-montpellier-france-this-july.md
+++ b/markdown/2014_06_replicant-at-the-15th-libre-software-meeting-in-montpellier-france-this-july.md
@@ -19,7 +19,7 @@ English: [Replicant: software freedom on mobile devices][7] and [An overview
 of Replicant development][8]. But there are plenty more talks dedicated to
 software freedom and Android: FSFE's member [Erik Albers][9] will present a
 conference about [Freedom on Android devices][10] while F-Droid developer
-[Daniel Martí][11] will talk about [Free Software on Android via F-Droid][12].  
+[Daniel Martí][11] will talk about [Free Software on Android via F-Droid][12].
 In addition, Replicant developer Paul Kocialkowski will present a conference
 about various freedom issues on ARM devices: [ARM devices and your
 freedom][13].
diff --git a/markdown/2014_09_replicant-homepage-and-roadmap-for-the-future.md b/markdown/2014_09_replicant-homepage-and-roadmap-for-the-future.md
index efdbe34..687699a 100644
--- a/markdown/2014_09_replicant-homepage-and-roadmap-for-the-future.md
+++ b/markdown/2014_09_replicant-homepage-and-roadmap-for-the-future.md
@@ -8,7 +8,7 @@ holds status reports and news about the project. However, it did not fit well
 for providing easy access to relevant material about the project, nor did it
 give our (growing) community the attention it deserves. This is why we decided
 to launch a new [homepage][1] for the project, highlighting what really
-matters, in style.  
+matters, in style.
 We believe it is a good thing to have, in order to clearly spread the word
 about Replicant and ease the understanding of our message. The new homepage
 provides a clear explanation of [what Replicant is about][2], provides
@@ -19,7 +19,7 @@ regarding these topics.
 
 Regarding progress in development, a few things happened recently and a lot
 more is on the way: time to take a step back, look at what's in the works and
-what is next on our roadmap.  
+what is next on our roadmap.
 After attending [RMLL/LSM ][6]in Montpellier, France, most of the development
 time was spent on completing a full rewrite of [Samsung-RIL][7], the software
 in charge of the various aspects of telephony and mobile data on the Samsung
diff --git a/markdown/2014_12_replicant-4-2-0003-images-release.md b/markdown/2014_12_replicant-4-2-0003-images-release.md
index 98929c7..ef4c0bc 100644
--- a/markdown/2014_12_replicant-4-2-0003-images-release.md
+++ b/markdown/2014_12_replicant-4-2-0003-images-release.md
@@ -18,7 +18,7 @@ stable or reliable. The rewrite should be more robust and fail-proof: it has
 been tested daily on a couple of devices for the past few months, with no
 major incident to report. The Samsung-RIL rewrite has about as many features
 supported as the previous version, with the exception of a few ones that were
-broken anyway (mainly, USSD and STK).  
+broken anyway (mainly, USSD and STK).
 The new code establishes a sane basis for external contributions, so everyone
 is welcome to dig in and add support for what's missing.
 
diff --git a/markdown/2015_04_whats-happening-or-not-at-replicant.md b/markdown/2015_04_whats-happening-or-not-at-replicant.md
index b7e7f17..eaa90ff 100644
--- a/markdown/2015_04_whats-happening-or-not-at-replicant.md
+++ b/markdown/2015_04_whats-happening-or-not-at-replicant.md
@@ -27,7 +27,7 @@ now closing down and while we have all the source code uploaded there backed
 up, we're looking for an alternative solution that doesn't compromise on the
 core values behind Replicant and offers significant guarantees. Because of
 this situation, nothing is to be committed to the repositories before they are
-moved to a new location, that we are yet to find.  
+moved to a new location, that we are yet to find.
 However, some security updates were kindly submitted by the community and
 those will be reviewed and integrated as soon as everything is back up and
 running.
diff --git a/markdown/2016_08_replicant-6-early-work-upstream-work-and-f-droid-issue.md b/markdown/2016_08_replicant-6-early-work-upstream-work-and-f-droid-issue.md
index 2a63e75..854f3bc 100644
--- a/markdown/2016_08_replicant-6-early-work-upstream-work-and-f-droid-issue.md
+++ b/markdown/2016_08_replicant-6-early-work-upstream-work-and-f-droid-issue.md
@@ -54,7 +54,7 @@ devices, such as Allwinner tablets, that will benefit Replicant eventually.
 recommended by the FSF and [listed as a fully free software distribution][2]
 that respects the [GNU Free System Distribution Guidelines][3], along with
 other GNU/Linux distributions such as [Trisquel][4] or [Parabola][5].
-Replicant  
+Replicant
 ships the F-Droid package manager in its images.
 
 F-droid is committed to distributing only free software, and it does. However
@@ -70,14 +70,14 @@ Practically speaking some of the applications F-Droid distributes:
 While the list of such anti-features is displayed in red when selecting an
 application in F-Droid, applications with anti-features are still listed aside
 compliant ones. This is also quite confusing since free software isn't
-expected to contain  
+expected to contain
 such anti-features in the first place.
 
-It took Replicant a long time to realize the issue, this is due  
-to its developers being very busy, to the fact that the anti-feature  
+It took Replicant a long time to realize the issue, this is due
+to its developers being very busy, to the fact that the anti-feature
 display is confusing and that there was no clear smoking gun.
 
-After an investigation, that was delayed due to the lack of time, a  
+After an investigation, that was delayed due to the lack of time, a
 smoking gun was finally found, and [a bug report][8] was opened on the
 Replicant side.
 
diff --git a/markdown/2017_02_replicant-6-0-development-updates.md b/markdown/2017_02_replicant-6-0-development-updates.md
index d0eee56..ff605bf 100644
--- a/markdown/2017_02_replicant-6-0-development-updates.md
+++ b/markdown/2017_02_replicant-6-0-development-updates.md
@@ -29,7 +29,7 @@ GTA04.
 After you have installed Replicant on one of the supported devices, you will
 notice that WiFi doesn't work. The reason is that the WiFi chips on all
 supported devices need a proprietary firmware to be loaded onto the chip. As
-Replicant only ships free software, this firmware is not included in an image.  
+Replicant only ships free software, this firmware is not included in an image.
 An alternative is to use an external WiFi dongle with an USB OTG cable. A free
 firmware exists for the AR9271 chipset and various WiFi adapters use this
 chipset. [Tehnoetic provided patches][3] for initial support in Replicant 4.2.
@@ -50,7 +50,7 @@ wouldn't work with the Android software renderer. Llvmpipe also makes it
 possible to use a recent webview. For now, Replicant 6.0 is stuck with the
 last webview version that worked with the Android software renderer.
 Optimizing llvmpipe for ARM likely would make it fast enough. Any help in this
-regard would be greatly appreciated!  
+regard would be greatly appreciated!
 Another long-standing issue is related to the software rendering: QR code
 scanning or in general barcode scanning didn't work with Replicant because the
 software renderer requires a camera preview format that is incompatible with
@@ -84,11 +84,11 @@ Currently, only the non-LTE variant (GT-I9300) is supported by Replicant and
 Replicant doesn't support any 4G-enabled phone yet. It's possible to build a
 Replicant 6.0 image for the LTE variant, but it lacks support for the modem.
 The main task of the port will be to write a free implementation of the modem
-interface for telephony, SMS and mobile data.  
+interface for telephony, SMS and mobile data.
 I also played with the mainline kernel on the Galaxy S3 and I was able to boot
 Replicant 6.0 on top of the Linux 4.8 kernel with a few patches so that it was
 usable with very limited functionality. I will share more results from this
-endeavor in the future.  
+endeavor in the future.
 Replicant is based on CyanogenMod 13.0. As the CyanogenMod project was
 discontinued, future Replicant 6.0 versions will be based on its successor,
 LineageOS 13.0.
diff --git a/markdown/2017_12_third-replicant-6-0-release.md b/markdown/2017_12_third-replicant-6-0-release.md
index dac9163..1c33f2f 100644
--- a/markdown/2017_12_third-replicant-6-0-release.md
+++ b/markdown/2017_12_third-replicant-6-0-release.md
@@ -11,19 +11,19 @@ devices were crashing during boot, endlessly) when installing certain
 applications.
 
 It also fixes a [security issue][1] that enables attackers to decrypt and/or
-modify WiFi traffic.  
+modify WiFi traffic.
 This can be problematic if your security is relying on the WiFi encryption.
 This can be the case if you are using WiFi to connect to your device to use
 applications like [Remote Keyboard][2] over telnet. This can also be
 problematic if you share your Internet connection through WiFi and some
 services of the phone operator you use are available without authentication.
 
-Because of the above, updating to this new version is strongly recommended.  
+Because of the above, updating to this new version is strongly recommended.
 See the update instructions [on the wiki][3] for that.
 
 If your device is affected by the boot loop issue mentioned above, the update
 instructions won't work, as they expect you to be able to easily reboot to
-recovery.  
+recovery.
 In that case, to reboot to the recovery you have to first boot in [safe
 mode][4], and then to follow the update instructions to reboot to recovery.
 
diff --git a/markdown/2019_01_meeting-point-at-fosdem.md b/markdown/2019_01_meeting-point-at-fosdem.md
index 8f85026..f392101 100644
--- a/markdown/2019_01_meeting-point-at-fosdem.md
+++ b/markdown/2019_01_meeting-point-at-fosdem.md
@@ -4,24 +4,24 @@ title: Meeting Point at FOSDEM
 authors: Fil
 ---
 The [**Replicant Community Meeting**][1] will take place on Sunday, the 3rd of
-February at 11:00 AM in room J.1.106 at ULB, Brussels Belgium.  
+February at 11:00 AM in room J.1.106 at ULB, Brussels Belgium.
 We have successfully booked a [BoF room at FOSDEM][2], so we will have a
-quiet, heated and comfortable place where we can all sit together.  
+quiet, heated and comfortable place where we can all sit together.
 
-Access is public and free as in beer.  
-We encourage everyone to participate and contribute their opinion.  
+Access is public and free as in beer.
+We encourage everyone to participate and contribute their opinion.
 This meeting will be essential to the future arrangement of Replicant as a
-structured Project.  
+structured Project.
 
 Any schedule update or other info can be tracked on [the event's dedicated
-page on FOSDEM's website][2].  
-Replicant's blog will also be updated accordingly.  
+page on FOSDEM's website][2].
+Replicant's blog will also be updated accordingly.
 
  **IMPORTANT NOTICE** : This announcement is about the **community meeting.**
-The time schedule for the **workshop** **hasn't been decided yet**.  
+The time schedule for the **workshop** **hasn't been decided yet**.
 Interested people are encouraged to write to the [mailing list][3] to help
-organize it.  
-Also, the related [poll is still open][4].  
+organize it.
+Also, the related [poll is still open][4].
 
 
 
diff --git a/markdown/2019_01_replicant-meeting-at-fosdem-2019.md b/markdown/2019_01_replicant-meeting-at-fosdem-2019.md
index 0a53657..f989988 100644
--- a/markdown/2019_01_replicant-meeting-at-fosdem-2019.md
+++ b/markdown/2019_01_replicant-meeting-at-fosdem-2019.md
@@ -9,13 +9,13 @@ Like every year, [FOSDEM][1] will take place the first weekend of february in
 Brussels, Belgium.
 
 Replicant is organizing a **community meeting and a workshop** that will take
-place alongside FOSDEM events.  
+place alongside FOSDEM events.
 The main intention behind this is to **gather Replicant enthusiasts and
 contributors together** in order to share ideas and discuss Replicant-related
-key topics.  
+key topics.
 This is **a call for the community** to participate and propose arguments to
-discuss.  
-A [wiki page][2] has been prepared, to collect proposals and schedules.  
+discuss.
+A [wiki page][2] has been prepared, to collect proposals and schedules.
 Proposals and questions can be presented to [the mailing list][3].
 
 **Examples topics** that have been proposed are:
@@ -43,16 +43,16 @@ best day and time** :
 * [One for the workshop][5]
 
 We invite whoever might be interested, to **indicate their preferred
-schedule** for the events, in order to help us set up a sensible timetable.  
+schedule** for the events, in order to help us set up a sensible timetable.
 
 The official meeting point and timetables will be published on this blog and
-on the mailing list.  
+on the mailing list.
 
 Stay tuned!
 
-**EDIT** :  
+**EDIT** :
 The meeting report is available:
-<https://redmine.replicant.us/attachments/download/1597/formatted-report.pdf>  
+<https://redmine.replicant.us/attachments/download/1597/formatted-report.pdf>
 
  [1]: <https://fosdem.org/2019/>
 
diff --git a/markdown/2019_01_replicant-will-receive-a-device-from-necuno-solutions.md b/markdown/2019_01_replicant-will-receive-a-device-from-necuno-solutions.md
index 980dfec..bc973e2 100644
--- a/markdown/2019_01_replicant-will-receive-a-device-from-necuno-solutions.md
+++ b/markdown/2019_01_replicant-will-receive-a-device-from-necuno-solutions.md
@@ -75,7 +75,7 @@ more details on freedom issues affecting various system on a chip and by
 extension the single board computers that use such components.
 
 A Replicant developer (Joonas Kylmälä) will receive a Necuno Mobile to work on
-it.  
+it.
 
 The Necuno Mobile should have a Linux kernel that is very close to upstream:
 this is a good opportunity for a new attempt to enable Replicant to use
diff --git a/markdown/2019_12_replicant-36c3.md b/markdown/2019_12_replicant-36c3.md
index 386146b..45206ae 100644
--- a/markdown/2019_12_replicant-36c3.md
+++ b/markdown/2019_12_replicant-36c3.md
@@ -14,7 +14,7 @@ help installing Replicant or general advice regarding software freedom on
 smartphones and tablets. You can also take the opportunity to verify the
 release signing PGP key.
 
-Location: [L4, Exhibition Hall 2, Level 0][4]  
+Location: [L4, Exhibition Hall 2, Level 0][4]
 DECT: 6506
 
 There will also be a few talks about Replicant and related topics in several
diff --git a/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md b/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md
index 4ece681..aa64632 100644
--- a/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md
+++ b/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md
@@ -35,7 +35,7 @@ such devices.
 However some smartphones, which are typically used during a full day without
 necessarily having the ability to recharge, cannot be opened with regular
 tools. For such smartphones you need a heat gun, and using that also damage
-the device along  
+the device along
 the way. When the battery is glued with very strong glue, it makes it even
 more complicated and even more dangerous to change the battery as you need to
 use very dangerous chemicals to remove the glue. So we decided to not support
@@ -84,7 +84,7 @@ official support for it in Replicant, we still wanted the work to also be
 potentially useful for GNU/Linux distributions that might be interested in
 supporting this device or similar devices:
 
-* The amount of RAM and the stylus makes it more easy to run GNU/Linux  
+* The amount of RAM and the stylus makes it more easy to run GNU/Linux
 on the device:
 
   * As the stylus is more precise than big fingers, you can more easily use software that is less well adapted to the very small display, the very high pixel density, and big fingers.
@@ -163,7 +163,7 @@ and that the bootloader and OS refused to charge it.
 As we didn't have a lot of time to spent on all that, we didn't want to
 investigate more and proceeded to download OS images for older versions of the
 devices. We are also not sure if this was legal or not as the images weren't
-hosted by Samsung, and so we don't know  
+hosted by Samsung, and so we don't know
 if the website we downloaded them from had some arrangement with Samsung or
 not.
 
@@ -435,7 +435,7 @@ At least he could still trust his hardware and continue to use it after
 reinstalling everything. If the hardware had to run nonfree software, it would
 have been a different story.
 
-Besides about 1 month of Apache logs, and the phone number of his contacts,  
+Besides about 1 month of Apache logs, and the phone number of his contacts,
 not much was exposed. We also hope that Android “Factory erase” worked fine on
 the SM-N930F but we can't know as we didn't try to recover any data.
 
@@ -453,12 +453,12 @@ there.” that developer commented.
 
 ## References:
 
-[1]https://libreboot.org  
-[2]https://parabola.nu/  
-[3]https://librecmc.org/  
-[4]https://github.com/urjaman/frser-duino  
-[5]https://github.com/Ralim/ts100  
-[6]https://git.osmocom.org/simtrace/  
+[1]https://libreboot.org
+[2]https://parabola.nu/
+[3]https://librecmc.org/
+[4]https://github.com/urjaman/frser-duino
+[5]https://github.com/Ralim/ts100
+[6]https://git.osmocom.org/simtrace/
 [7]https://osmocom.org/projects/simtrace/wiki/SIMtrace
 
 ## Epilogue
diff --git a/markdown/2020_12_call-for-a-community-manager.md b/markdown/2020_12_call-for-a-community-manager.md
index aa640ab..10b1ee1 100644
--- a/markdown/2020_12_call-for-a-community-manager.md
+++ b/markdown/2020_12_call-for-a-community-manager.md
@@ -9,8 +9,8 @@ The Replicant project is looking for a community manager.
 The role of the community manager is to fill the gap between Replicant
 developers and users, making sure that users' concerns are properly addressed
 while at the same time freeing the developers from the burden of running the
-community.  
-The community manager should also foster collaborations between  
+community.
+The community manager should also foster collaborations between
 Replicant and other free software projects.
 
 ## Tasks
diff --git a/markdown/2021_05_presenting-replicants-community-manager.md b/markdown/2021_05_presenting-replicants-community-manager.md
index e179af5..da93321 100644
--- a/markdown/2021_05_presenting-replicants-community-manager.md
+++ b/markdown/2021_05_presenting-replicants-community-manager.md
@@ -44,9 +44,9 @@ candidate for the role.
 
 Kurtis has been a very active community member since at least 2016,
 successfully helping users in various occasions with different issues and
-enquiries.  
+enquiries.
 He is well informed about various free-software projects and has often acted
-as a link between some of those projects and Replicant.  
+as a link between some of those projects and Replicant.
 He participated in and/or helped organise many of the gatherings that have
 been held by Replicant members throughout the last 4 years, either in person
 or remotely, contributing his thoughts, impressions and valuable proposals.
diff --git a/markdown/2023_12_replicant-37c3.md b/markdown/2023_12_replicant-37c3.md
index 8870b4c..7ffcc7f 100644
--- a/markdown/2023_12_replicant-37c3.md
+++ b/markdown/2023_12_replicant-37c3.md
@@ -12,7 +12,7 @@ Since yesterday, December 27th, the [37th Chaos Communication Congress
 Replicant or general advice regarding software freedom on smartphones and
 tablets. You can also take the opportunity to verify the release signing PGP.
 
-Location: [G5, Hall 3, Level 0][4]  
+Location: [G5, Hall 3, Level 0][4]
 DECT: 8652
 
 As Replicant is struggling with structural problems, first and foremost lack