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>

1 files changed, 10 insertions, 10 deletions

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