convert.py, markdown: Fix right single quotation mark.

Some generated markdown have right single quotation marks, and without this fix, it ends up being displayed as '???' in the generated HTML files. As an example with site/new-replicant-test-images-available.html we have: We are please to remind you that, as usual, Replicant is fully free software and doesn???t include any proprietary firmwares. Converting the right single quotation marks to apostrophes fixed it. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
author: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 2024-03-18 02:40:29 +0100
committer: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 2025-06-15 01:30:24 +0200
commit: 659384dc54db02ccdce5648a9418283ee08fc216 (patch)
tree: 79fd51124db101adb2f49f12f4ef55dea5f10e4b /markdown
parent: c577cf167d08c09e4d3409a4971a09cc13daa5b2 (diff)
download: haunt-blog-659384dc54db02ccdce5648a9418283ee08fc216.tar.gz
haunt-blog-659384dc54db02ccdce5648a9418283ee08fc216.tar.bz2
haunt-blog-659384dc54db02ccdce5648a9418283ee08fc216.zip
60 files changed, 369 insertions, 369 deletions
diff --git a/markdown/2011_03_new-replicant-test-images-available.md b/markdown/2011_03_new-replicant-test-images-available.md
index 480c913..7b3acd5 100644
--- a/markdown/2011_03_new-replicant-test-images-available.md
+++ b/markdown/2011_03_new-replicant-test-images-available.md
@@ -14,7 +14,7 @@ installed data and applications** in order to prevent proprietary libraries
 from being used.
 
 We are please to remind you that, as usual, Replicant is fully free software
-and doesn’t include any proprietary firmwares.
+and doesn't include any proprietary firmwares.
 
 The Nexus One mobile phone needs some audio database files (located at
 /system/etc/firmware/*.acdb) to make sound and phone calls work which are not
diff --git a/markdown/2011_04_replicant-2-2-sdk-available.md b/markdown/2011_04_replicant-2-2-sdk-available.md
index 2ec4576..db31843 100644
--- a/markdown/2011_04_replicant-2-2-sdk-available.md
+++ b/markdown/2011_04_replicant-2-2-sdk-available.md
@@ -10,7 +10,7 @@ or any other Android 2.2 device.
 
 As usual the main difference compared to the Android SDK is that Replicant SDK
 should be fully free software. (Android SDK includes proprietary API like
-Google maps but we don’t want proprietary Google maps at all).
+Google maps but we don't want proprietary Google maps at all).
 
 The Replicant SDK also includes an emulator like the Android one to allow
 developers to write their apps even without having a phone.
diff --git a/markdown/2011_04_replicant-lacks-tracking-antifeatures.md b/markdown/2011_04_replicant-lacks-tracking-antifeatures.md
index 5953d58..3b2037a 100644
--- a/markdown/2011_04_replicant-lacks-tracking-antifeatures.md
+++ b/markdown/2011_04_replicant-lacks-tracking-antifeatures.md
@@ -20,11 +20,11 @@ nexus one) those files are missing** , even with `"Settings -> Location &
 Security -> Use wireless networks" enabled.`
 
 The directory that should contain those files(
-/data/data/com.google.android.location/files ) doesn’t even exist in
+/data/data/com.google.android.location/files ) doesn't even exist in
 Replicant.
 
-But beware: even if Replicant itself doesn’t track its users’ position, this
-doesn’t mean that the phone can’t spy on you.
+But beware: even if Replicant itself doesn't track its users' position, this
+doesn't mean that the phone can't spy on you.
 
 A smartphone usually has two components that talk to each other: a cpu and a
 modem. If the modem gets a call, it tells the CPU about it and viceversa for
@@ -34,8 +34,8 @@ work][4]).
 
 The modem and the CPU running Replicant are separated, and while we are trying
 to do our best to ship a fully free mobile os, the code running on the modem
-is proprietary software and **can’t be changed**. Since we don’t know what it
-does, we have no way to be sure that it doesn’t spy.
+is proprietary software and **can't be changed**. Since we don't know what it
+does, we have no way to be sure that it doesn't spy.
 
 Also note that on the HTC Dream and the nexus one mobile phones, GPS and audio
 parts are controlled by the modem.
@@ -44,7 +44,7 @@ parts are controlled by the modem.
 know your location.
 
 This is just to remind you that **every mobile phone is a tracking device**
-and if you don’t want to be spied at all you should not use one.
+and if you don't want to be spied at all you should not use one.
 
 So why do people invest time on Replicant?
 
@@ -57,11 +57,11 @@ Here are some reasons:
 * If mobile phones become the computers of the future we want to run [free
   software][9] on them.
 
-Edit: I learned that the Modem’s CPU has access to the memory(the RAM chips)
-of the CPU running replicant, in other words the modem CPU can spy replicant’s
+Edit: I learned that the Modem's CPU has access to the memory(the RAM chips)
+of the CPU running replicant, in other words the modem CPU can spy replicant's
 CPU.
 
-That will force us to port replicant to some devices that don’t have this
+That will force us to port replicant to some devices that don't have this
 problem, such as the nokia n900 for instance.
 
  [1]: <http://www.guardian.co.uk/technology/2011/apr/20/iphone-tracking-
diff --git a/markdown/2011_05_replicant-2-2-preview-007.md b/markdown/2011_05_replicant-2-2-preview-007.md
index f81c3cc..33fb820 100644
--- a/markdown/2011_05_replicant-2-2-preview-007.md
+++ b/markdown/2011_05_replicant-2-2-preview-007.md
@@ -5,7 +5,7 @@ authors: admin
 ---
 We are pleased to announced [Replicant 2.2 preview 007][1].
 
-**What’s new in this version:**
+**What's new in this version:**
 
 * We are using a new ril (hycs-hardware_xdandroid-ril), which fixes
   telephony in the USA. Data should also work.
diff --git a/markdown/2011_06_replicant-2-2-preview-008-is-out.md b/markdown/2011_06_replicant-2-2-preview-008-is-out.md
index 8b44085..cb35e01 100644
--- a/markdown/2011_06_replicant-2-2-preview-008-is-out.md
+++ b/markdown/2011_06_replicant-2-2-preview-008-is-out.md
@@ -5,7 +5,7 @@ authors: admin
 ---
 We are pleased to announced **Replicant 2.2 preview 008**.
 
-What’s new in this version (since 0007):
+What's new in this version (since 0007):
 
 * Bug #22 (http://trac.osuosl.org/trac/replicant/ticket/22) should
   (hopefully) be fixed
diff --git a/markdown/2011_08_nexus-s-support-in-replicant-being-worked-on.md b/markdown/2011_08_nexus-s-support-in-replicant-being-worked-on.md
index 764ccf9..29ab4e7 100644
--- a/markdown/2011_08_nexus-s-support-in-replicant-being-worked-on.md
+++ b/markdown/2011_08_nexus-s-support-in-replicant-being-worked-on.md
@@ -6,7 +6,7 @@ authors: Paul Kocialkowski
 A few month ago, we (Replicant developers) decided to start the work on the
 new Google Nexus S.
 
-This device seemed an interesting target at first since it doesn’t have any
+This device seemed an interesting target at first since it doesn't have any
 technical restriction to flash a non-official operating system and kernel but
 also as it comes with the latest (free) version of Android, Gingerbread. Of
 course, even if Android Gingerbread is free, the device requires non-free bits
@@ -17,7 +17,7 @@ The work was started at the end of July and the 100% free images of Replicant
 2.3 that run on the device already contain a set of supported features. You
 can get a detailed state of the Nexus S support in Replicant at
 <http://trac.osuosl.org/trac/replicant/wiki/ReplicantStatus#nexuss>. All the
-source code is, as usual, available in Replicant’s [gitorious repos][1].
+source code is, as usual, available in Replicant's [gitorious repos][1].
 Though, we still miss a big part: the RIL, that is necessary for telephony.
 
 We soon discovered that the hardware of the Nexus S was made in a way that
diff --git a/markdown/2011_09_introducing-replicant-on-htc-dream-video.md b/markdown/2011_09_introducing-replicant-on-htc-dream-video.md
index 77a610d..9f62263 100644
--- a/markdown/2011_09_introducing-replicant-on-htc-dream-video.md
+++ b/markdown/2011_09_introducing-replicant-on-htc-dream-video.md
@@ -13,7 +13,7 @@ Networking, FDroid and GPS among other things).
 This video itself is available under the Creative Commons BY-SA license, but
 other licenses may apply to the audio tracks (see on the video).
 
-The audio doesn’t include any voice comment but the video comes along with
+The audio doesn't include any voice comment but the video comes along with
 subtitles that could easily be translated. The video is available in the free
 WebM video format on a 360p resolution, both with subtitles hardcoded (for
 English only) or with subtitles on a separate file.
diff --git a/markdown/2011_11_replicant-2-3-preview-images-for-nexus-one-released.md b/markdown/2011_11_replicant-2-3-preview-images-for-nexus-one-released.md
index e5c9307..ea24302 100644
--- a/markdown/2011_11_replicant-2-3-preview-images-for-nexus-one-released.md
+++ b/markdown/2011_11_replicant-2-3-preview-images-for-nexus-one-released.md
@@ -16,7 +16,7 @@ You can download these new images at
 Nexus One status under Replicant 2.3 should be the same as Replicant 2.2: what
 was working with FroYo should still work in Gingerbread.
 
-Even though Nexus One is supported in Replicant, it doesn’t mean it’s a device
+Even though Nexus One is supported in Replicant, it doesn't mean it's a device
 we can totally recommend for freedom:
 
 * It has a non-free bootloader
diff --git a/markdown/2011_11_replicant-on-nexus-s-preview.md b/markdown/2011_11_replicant-on-nexus-s-preview.md
index 0846fd1..dc8548f 100644
--- a/markdown/2011_11_replicant-on-nexus-s-preview.md
+++ b/markdown/2011_11_replicant-on-nexus-s-preview.md
@@ -12,37 +12,37 @@ This images includes the **ipc-modemctrl** tool (from **libsamsung-ipc** )
 that implements minimal telephony support. Please test this tool and give us
 feedback: <http://trac.osuosl.org/trac/replicant/wiki/libsamsung-ipc>.
 
-Here is a list of what’s not ready yet in this preview image (but may be done
+Here is a list of what's not ready yet in this preview image (but may be done
 in the future):
 
 * RIL: this is the crucial library used to handle telephony and data
   connectivity (3G). This is being worked on very hard and will be there in
   some time
 
-* GPS: we haven’t worked at all on the GPS side: it might be possible to
+* GPS: we haven't worked at all on the GPS side: it might be possible to
   have it working (needs work)
 
-* Compass: it’s the same as in Nexus One (which works) but the kernel driver
+* Compass: it's the same as in Nexus One (which works) but the kernel driver
   is different (needs work)
 
-* Full Camera: Camera works but in Black & White preview mode and isn’t very
+* Full Camera: Camera works but in Black & White preview mode and isn't very
   stable
 
-Here’s a list of what doesn’t work in Replicant and is probably not going to
+Here's a list of what doesn't work in Replicant and is probably not going to
 be achieved:
 
 * 3D acceleration
 
-* Whatever needs the non-free firmwares we don’t include (NFC, MFC, WiFi,
+* Whatever needs the non-free firmwares we don't include (NFC, MFC, WiFi,
   Bluetooth…)
 
 We are indeed not including any non-free firmware (100% free is our goal) and
 are not going to provide any free replacement for these as we are not skilled
-to write such replacement. Though, the kernel we use won’t prevent loading
+to write such replacement. Though, the kernel we use won't prevent loading
 these firmwares if in place.
 
 We also thought of [porting u-boot to the Nexus S][3] in order to have a free
-bootloader replacement but it’s apparently not possible as primary bootloader
+bootloader replacement but it's apparently not possible as primary bootloader
 (perhaps possible chainloaded).
 
 Anyway, we made a video of Replicant 2.3 running on the Nexus S:
diff --git a/markdown/2012_01_nexus-s-status-update-with-new-images.md b/markdown/2012_01_nexus-s-status-update-with-new-images.md
index ae8385b..3ae7b73 100644
--- a/markdown/2012_01_nexus-s-status-update-with-new-images.md
+++ b/markdown/2012_01_nexus-s-status-update-with-new-images.md
@@ -12,20 +12,20 @@ a separate CPU, the RIL runs on the main CPU in Android userspace.
 
 The only free RILs we know of are for the well-documented and widely-used [AT
 command set][2]. Back in July 2011, we were desperate to see that there was no
-free implementation for the Nexus S modem protocol. Fortunately, we weren’t
+free implementation for the Nexus S modem protocol. Fortunately, we weren't
 alone on this one. After asking around on IRC, we met a talented developer who
 owns a Samsung H1 device, which originally runs LiMo, a mobile operating
 system with parts of free software, at least with the [Linux kernel][3]. The
-developer (who’s known on IRC as ius) was part of the effort to [port Android
-to the Samsung H1][4], but he didn’t stop there. He also investigated the
+developer (who's known on IRC as ius) was part of the effort to [port Android
+to the Samsung H1][4], but he didn't stop there. He also investigated the
 modem protocol used in the device. And the most incredible is that he did find
 out most of the protocol messages and data structures. We together
 investigated on Nexus S as well, and, thanks to this incredible luck we had,
 the protocol is the same for nexus s. We managed to boot the modem and
 obtained the first messages quickly. Then, we decided to push Nexus S support
-to ius’ lib, renaming it [libsamsung-ipc][5] for the occasion.
+to ius' lib, renaming it [libsamsung-ipc][5] for the occasion.
 
-But the adventure didn’t stop there. Another talented developer known as
+But the adventure didn't stop there. Another talented developer known as
 morphis, who works on the [SHR][6] project, free [GNU][7]/[Linux][3] system
 for smartphones and who accomplished a huge amount of work to add support for
 the Palm Pre devices modem protocol in [FSO][8] (the middleware used in
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 11eed8f..4f65b59 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
@@ -12,9 +12,9 @@ result, a few weeks ago, Replicant devs agreed and we started the migration
 process.
 
 Bug reports, wiki pages and user accounts were migrated successfully, but it
-wasn’t be the case of the users passwords, which are in a different format
+wasn't be the case of the users passwords, which are in a different format
 from trac to redmine. As a result, if you had an account on trac and want to
-be able to use it on redmine, you’ll have to leave a mail at:
+be able to use it on redmine, you'll have to leave a mail at:
 
 **contact@replicant.us** in order to let us know and reset your password so
 that you can set the password you want.
diff --git a/markdown/2012_03_galaxy-s-support-upcoming.md b/markdown/2012_03_galaxy-s-support-upcoming.md
index 4c24ae4..249fc51 100644
--- a/markdown/2012_03_galaxy-s-support-upcoming.md
+++ b/markdown/2012_03_galaxy-s-support-upcoming.md
@@ -14,20 +14,20 @@ in order to successfully place calls, send text messages and connect to data
 via 3G (among other things we implemented). That was a lot of work and by now,
 many of us are using Nexus S as a stable daily-phone.
 
-So, what’s the good news for Galaxy S owners? Well, most of the work we’ve
+So, what's the good news for Galaxy S owners? Well, most of the work we've
 done for Nexus S works as well on Galaxy S! Of course, there are still low-
-level adjustments to make to have it working as well, but it’s doable. A few
+level adjustments to make to have it working as well, but it's doable. A few
 weeks ago, I bought a Galaxy S device and slowly started the work. I was able
 to get the following features to work: **graphics** (as good as Nexus S),
 
 **sound** , **calls** , **SMS** , **FM radio** and **accelerometers**. The
-main problem I faced is installation: flashing the images via heimdall doesn’t
+main problem I faced is installation: flashing the images via heimdall doesn't
 work but it goes fine with CWM recovery, with all the correct image formats.
 
 I think we will be able to release a new set of images for Nexus S, Galaxy S
-and Nexus One (hopefully with fixed data) and then, it’ll be time to start the
+and Nexus One (hopefully with fixed data) and then, it'll be time to start the
 work on [GTA04][3] the amazing new replacement for the GTA02/Neo Freerunner
-board. Having Replicant running on GTA04 is the goal we’ll try to reach as
+board. Having Replicant running on GTA04 is the goal we'll try to reach as
 hard as possible. We encourage you to help the GTA04 project with
 [donations][4] to fund the effort or by subscribing to the [group tour][5] to
 get your device at a lower price.
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 415d94a..d370c8a 100644
--- a/markdown/2012_09_replicant-2-3-0004-images-release.md
+++ b/markdown/2012_09_replicant-2-3-0004-images-release.md
@@ -3,7 +3,7 @@ date: 2012-09-10T20:17:30+00:00
 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
+Even though we didn't update the homepage for a long time, we are still
 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
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 c2dd50d..12c0573 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
@@ -9,13 +9,13 @@ the vulnerability: intents can basically dial a number and start a call
 without asking confirmation to the user. That could seem harmless at first
 sight, but it turns out it also works with USSD codes, and some of them are
 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.
+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
+What's also problematic about this is that web pages can trigger such intents
 (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
+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
 only new feature of these images (Galaxy S also got a nasty graphic bug
 fixed).
 
diff --git a/markdown/2012_11_replicant-4-0-0001-images-release.md b/markdown/2012_11_replicant-4-0-0001-images-release.md
index 78e1443..0c36c07 100644
--- a/markdown/2012_11_replicant-4-0-0001-images-release.md
+++ b/markdown/2012_11_replicant-4-0-0001-images-release.md
@@ -13,17 +13,17 @@ Aside from the new Ice Cream Sandwich user experience, that we tried to make
 as good as possible without any non-free blob, most devices have better
 hardware support than before, such as Galaxy S which now has working camera,
 or the global improvements that were made to make telephony more stable and
-reliable. Even though it’s not perfect yet, we are proud of the result, that
+reliable. Even though it's not perfect yet, we are proud of the result, that
 many of us use daily. If you encounter a particular problem with our software,
 do not hesitate to report the issue via our tracker, or give feedback when a
 problem was resolved.
 
 We are indeed writing hundreds of lines of code to have more hardware
 supported and with a better state, replacing non-free components, step by
-step. Keep in mind that Replicant has a very small core team, we’re just two
-people doing this on our free time: that means we can’t work on every side of
+step. Keep in mind that Replicant has a very small core team, we're just two
+people doing this on our free time: that means we can't work on every side of
 the project at the same time and have to make choices. This is why we will
-always welcome serious new contributors who’d like to get involved in the
+always welcome serious new contributors who'd like to get involved in the
 project.
 
 You can download the images from the [ReplicantImages][1] page and find
diff --git a/markdown/2013_01_replicant-4-0-sdk-release.md b/markdown/2013_01_replicant-4-0-sdk-release.md
index d73a307..40fa08e 100644
--- a/markdown/2013_01_replicant-4-0-sdk-release.md
+++ b/markdown/2013_01_replicant-4-0-sdk-release.md
@@ -7,7 +7,7 @@ It was brought to our attention that the Android SDK is now being released
 under an overall proprietary software license. In the past, we already had to
 release a free software SDK, back in Replicant 2.2 times, because the Android
 SDK was shipping with the non-free Google APIs. More recent SDK updates made
-these APIs only plug-ins that weren’t shipped with the SDK and it was made
+these APIs only plug-ins that weren't shipped with the SDK and it was made
 clear that these components were non-free while all the license files we could
 find on the Android SDK package were free software licenses.
 
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 af6d25c..460a4b0 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
@@ -26,12 +26,12 @@ group effort, Replicant has better chances to succeed and bring freedom to
 mobile phone users. We are currently a team of two developers with less and
 less time to get involved in the project and bring new features. Becoming a
 developer is not even that hard: we have [developer][4] and [porting
-guides][5] available to make it easier for you to get started and we’ll be
+guides][5] available to make it easier for you to get started and we'll be
 there to guide you all along. Even non-technical people can help to some
 extent, covering tasks such as building up documentation or writing
-announcements for the project if they’re good enough at it.
+announcements for the project if they're good enough at it.
 
-Please get in touch with us if you’re interested. The best way to start is
+Please get in touch with us if you're interested. The best way to start is
 most likely to get a Replicant-supported device and start hacking on it and if
 you prove serious enough, we might even use some of the donations money to
 provide you with a new device to port Replicant to!
diff --git a/markdown/2013_07_replicant-4-0-0004-images-release.md b/markdown/2013_07_replicant-4-0-0004-images-release.md
index 9a62728..05ff353 100644
--- a/markdown/2013_07_replicant-4-0-0004-images-release.md
+++ b/markdown/2013_07_replicant-4-0-0004-images-release.md
@@ -4,12 +4,12 @@ title: Replicant 4.0 0004 images release
 authors: Paul Kocialkowski
 ---
 The last months have been rather calm for Replicant development, no big
-changes or improvements were made. That doesn’t mean the project stalled:
+changes or improvements were made. That doesn't mean the project stalled:
 instead, we added support for some new devices. The previous set of images
 added support for the Galaxy Tab 2 10.1/7.0 in their 3G versions and we were
 requested to provide images for the WiFi-only flavors of these tablets as
 well. Since it only requires very little work, we were able to quickly fulfill
-that request, even though we couldn’t test it ourselves (you’re more than
+that request, even though we couldn't test it ourselves (you're more than
 welcome to spot and report issues about these devices).
 
 However, the biggest part of what motivated us to build and release new images
@@ -20,7 +20,7 @@ features may need non-free firmwares that run on separate chips). A couple of
 other things are also missing due to technical limitations (NFC, FM radio).
 
 We are still trying hard to bring Replicant to the [Goldelico GTA04][1], but
-it couldn’t make it to that release either as we still need help bringing a
+it couldn't make it to that release either as we still need help bringing a
 reliable Android kernel to that platform (DM37x).
 
 A more complete [changelog][2] is also available, highlighting in details what
diff --git a/markdown/2013_08_opening-the-replicant-forums.md b/markdown/2013_08_opening-the-replicant-forums.md
index 6a6a706..e848866 100644
--- a/markdown/2013_08_opening-the-replicant-forums.md
+++ b/markdown/2013_08_opening-the-replicant-forums.md
@@ -15,7 +15,7 @@ blog. The [mailing-list][2] and [IRC][3] are also good places for general-
 purpose questions since they are public, but it appears that many prefer to
 use web-based interfaces.
 
-Registration was also made easier, since new accounts activation doesn’t
+Registration was also made easier, since new accounts activation doesn't
 require a manual confirmation from us anymore.
 
 We hope the [forums][1] will help bring help and support, from and to the
diff --git a/markdown/2013_10_replicant-4-0-0005-images-release.md b/markdown/2013_10_replicant-4-0-0005-images-release.md
index 6bbd6ac..15c96e7 100644
--- a/markdown/2013_10_replicant-4-0-0005-images-release.md
+++ b/markdown/2013_10_replicant-4-0-0005-images-release.md
@@ -5,14 +5,14 @@ authors: Paul Kocialkowski
 ---
 Another couple of months passed by, bringing its share of improvements to
 Replicant 4.0, so we felt it was time to release a new batch of images. First
-thing’s first, let’s talk a bit about the [fundraising program][1] we launched
+thing's first, let's talk a bit about the [fundraising program][1] we launched
 thanks to the [Free Software Foundation][2]: it was a huge success! Over
 $20,000 were collected over the past two months, thanks to your help. We
-really didn’t expect that much money and it will greatly cover for our needs,
+really didn't expect that much money and it will greatly cover for our needs,
 which include buying new devices and covering for travel-related expenses,
 allowing us to attend events such as FOSDEM. On a sad note, we are more and
 more looking for new developers to get involved in the project: both GNUtoo
-and I are very busy and cannot contribute to the project as much as we’d like
+and I are very busy and cannot contribute to the project as much as we'd like
 to, so things will keep moving a bit slowly, compared to what it used to be.
 
 However, this new batch comes with a good share of improvements: the Galaxy
diff --git a/markdown/2013_11_fairphone.md b/markdown/2013_11_fairphone.md
index 9556d32..9416bfe 100644
--- a/markdown/2013_11_fairphone.md
+++ b/markdown/2013_11_fairphone.md
@@ -27,7 +27,7 @@ software, but what we are really interested in is the parts that deal with the
 hardware. First, the Linux kernel source code for the device will be released
 (it is copyleft software so this is an obligation). It will also be possible
 to build the kernel from source and install it on the device without the need
-to sign the kernel with the manufacturer’s key. Actually, there should be no
+to sign the kernel with the manufacturer's key. Actually, there should be no
 signature check on the [Fairphone][1] for the kernel or the bootloaders. Some
 of the bootloaders (maybe all of them; we cannot tell for sure at this point)
 are free software and it should be able to replace them with a free build. We
@@ -40,7 +40,7 @@ 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).  
 [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
+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,
 so it may take some time to arrive or eventually not succeed.
 
diff --git a/markdown/2014_01_replicant-4-2-kicks-out.md b/markdown/2014_01_replicant-4-2-kicks-out.md
index 7fabba2..03d1ac5 100644
--- a/markdown/2014_01_replicant-4-2-kicks-out.md
+++ b/markdown/2014_01_replicant-4-2-kicks-out.md
@@ -3,7 +3,7 @@ date: 2014-01-22T19:15:36+00:00
 title: Replicant 4.2 kicks out!
 authors: Paul Kocialkowski
 ---
-We’ve been working very hard over the past few months to push Replicant to a
+We've been working very hard over the past few months to push Replicant to a
 newer Android version: the work started when CyanogenMod released version
 10.1.3, based on the latest Android 4.2 code, back in September 2013. Bringing
 Replicant to a new Android version is a really big piece of work, especially
diff --git a/markdown/2014_03_unveiling-the-samsung-galaxy-back-door.md b/markdown/2014_03_unveiling-the-samsung-galaxy-back-door.md
index 1543672..9647e08 100644
--- a/markdown/2014_03_unveiling-the-samsung-galaxy-back-door.md
+++ b/markdown/2014_03_unveiling-the-samsung-galaxy-back-door.md
@@ -6,25 +6,25 @@ authors: Paul Kocialkowski
 Yesterday, we disclosed our findings about the [Samsung Galaxy back-door][1],
 an anti-feature found in Samsung Galaxy devices that lets the modem access the
 files stored on the device. For a complete statement about the issue, you can
-refer to [the article we published at the Free Software Foundation’s
+refer to [the article we published at the Free Software Foundation's
 website][1]. A technical description of the issue is available on a [dedicated
 page of the Replicant wiki][2], along with more information regarding the
 back-door.
 
-The information spread out very quickly and we’re glad the press is finding
-interest in such matters as privacy and unjust control over one’s computing.
+The information spread out very quickly and we're glad the press is finding
+interest in such matters as privacy and unjust control over one's computing.
 This demonstrates yet another time why free software is essential and how a
 single piece of proprietary software can compromise a whole device.
 
 We have yet to hear from Samsung about this issue, as we are hoping that the
 reason for the presence of this back-door will be clarified. In that regard,
-we’d be very glad to work with Samsung in order to make things right, for
+we'd be very glad to work with Samsung in order to make things right, for
 instance through releasing free software or documentation that would make it
 easy for community Android versions to get rid of the incriminated blob.
 
 **Update:** Several sources, including Samsung, claim this is a non-issue. A
 complementary statement to address these claims was issued at [Paul
-Kocialkowski’s personal blog][3].
+Kocialkowski's personal blog][3].
 
  [1]: <http://www.fsf.org/blogs/community/replicant-developers-find-and-
 close-samsung-galaxy-backdoor>
diff --git a/markdown/2014_06_replicant-4-2-on-the-goldelico-gta04.md b/markdown/2014_06_replicant-4-2-on-the-goldelico-gta04.md
index bb787ed..e0fc49d 100644
--- a/markdown/2014_06_replicant-4-2-on-the-goldelico-gta04.md
+++ b/markdown/2014_06_replicant-4-2-on-the-goldelico-gta04.md
@@ -11,16 +11,16 @@ finally unlocked thanks to the efforts of Golden Delicious and various members
 of the [OpenPhoenux][2] community, bringing GTA04 support to a newer kernel
 version that holds all the necessary pieces for proper Android support. More
 details on some technical aspects related to this are available at [Paul
-Kocialkowski’s coding blog][3].
+Kocialkowski's coding blog][3].
 
-Work on the device resumed months ago and we’ve been working hard ever since
+Work on the device resumed months ago and we've been working hard ever since
 to improve the status of the Replicant port. While it is not yet usable as a
 daily phone, we have reached numerous milestones over the past months and many
 key parts of the device are already handled correctly, already allowing many
 use cases, such as digital audio player or GPS navigation system. A dedicated
 wiki page holds the [details of the Replicant status on GTA04][4].
 
-As we’re very enthusiastic about the future, we’ve decided to shoot a video
+As we're very enthusiastic about the future, we've decided to shoot a video
 highlighting various aspects of Replicant on the GTA04! Installable images for
 the GTA04 will be released along with the next batch of Replicant 4.2 images,
 including all the features shown in the video:
@@ -33,7 +33,7 @@ The video is also available for download:
 
 To this day, the GTA04 remains the best phone out there regarding software
 freedom: bootloaders are free software and Replicant will eventually be able
-to run with most of the device’s features supported, the only exceptions being
+to run with most of the device's features supported, the only exceptions being
 graphics acceleration, hardware media encoding/decoding and Wi-Fi (due to a
 proprietary firmware). Regarding security and privacy, the [Goldelico
 GTA04][1] is also very good as it can run without proprietary software, but
@@ -42,7 +42,7 @@ also because its modem is clearly separated from the rest of the device.
 You are very much encouraged to get your own device out of the next batch of
 GTA04 production by placing a [preorder on the next revision][7]! As it is
 often the case, devices that are particularly designed to be a good fit with
-free software don’t get much mainstream attention, which makes it especially
+free software don't get much mainstream attention, which makes it especially
 hard for Golden Delicious to run production batches. Unlike in software
 development, having hardware produced costs a lot of money, especially in
 small batches. It is up to you to change that by [showing your interest][7]
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 c6f7268..7df464d 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
@@ -7,17 +7,17 @@ authors: Paul Kocialkowski
 
 Replicant will take part in the 15th edition of the [Libre Software
 Meeting][3] ([Rencontres Mondiales du Logiciel Libre — RMLL][4] in French)
-that takes place from July 5th to 11th 2014 in Montpellier, France. We’ll be
+that takes place from July 5th to 11th 2014 in Montpellier, France. We'll be
 there during the week at the university to present Replicant through a few
-talks as well as a workshop, organized jointly with members of FSFE’s [Free
-Your Android][5] program and the [F-Droid project][6]. You’re welcome to come
+talks as well as a workshop, organized jointly with members of FSFE's [Free
+Your Android][5] program and the [F-Droid project][6]. You're welcome to come
 and say hi, ask for help about freeing your mobile device, see devices
 actually running with Replicant or just have a chat with us!
 
 There will be two conferences about the Replicant project, both delivered in
 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
+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].  
 In addition, Replicant developer Paul Kocialkowski will present a conference
@@ -29,7 +29,7 @@ of the [GNU project][15] and president of the [Free Software Foundation][16]
 will be attending the event and will deliver a speech about a Free digital
 society (in French).
 
-We’re looking forward to seeing you there!
+We're looking forward to seeing you there!
 
  [1]: http://www.replicant.us/wp-content/uploads/2014/06/rmll.png
 
diff --git a/markdown/2014_07_replicant-4-2-0002-images-release.md b/markdown/2014_07_replicant-4-2-0002-images-release.md
index 6781807..ff5cbce 100644
--- a/markdown/2014_07_replicant-4-2-0002-images-release.md
+++ b/markdown/2014_07_replicant-4-2-0002-images-release.md
@@ -3,9 +3,9 @@ date: 2014-07-08T14:02:22+00:00
 title: Replicant 4.2 0002 images release
 authors: Paul Kocialkowski
 ---
-As we announced a few weeks ago, we’ve been working hard on [Goldelico
+As we announced a few weeks ago, we've been working hard on [Goldelico
 GTA04][1] support over the past months, so we thought it was time to make a
-new batch of images. Moreover, the time couldn’t be better as we are
+new batch of images. Moreover, the time couldn't be better as we are
 presenting Replicant at the [LSM/RMLL][2], another reason to have something
 new to show!
 
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 f899766..efdbe34 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
@@ -18,7 +18,7 @@ that we face on mobile devices today, as well as [recommendations][5]
 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
+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.  
 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
@@ -27,7 +27,7 @@ devices we support. This rewrite brings many advantages in terms of stability,
 features support and also provides a sane and clear base to make external
 contributions easier. While this is an important contribution to achieve
 software freedom on mobile devices, these Samsung devices are severely flawed
-as they don’t allow running free bootloaders.
+as they don't allow running free bootloaders.
 
 For some time already, we have decided to focus our development effort on
 better devices, that can run free bootloaders, in addition to a free system
@@ -48,7 +48,7 @@ stay tuned as we will start documenting these devices soon!
 
 In the meantime, we are more than ever willing to make Replicant as
 privacy/security-oriented as we can, especially by targeting devices that
-either don’t have a modem at all (Wi-Fi-only tablets, such as the many Sunxi
+either don't have a modem at all (Wi-Fi-only tablets, such as the many Sunxi
 ones) or are not proven to have bad modem isolation.
 
 As of today, Replicant is still a one-man effort and while all these new
@@ -56,7 +56,7 @@ directions are very exciting, it takes a lot of time to actually turn them
 into reality. Since we prefer to focus on these new directions, Replicant will
 stay based on version 4.2 of Android, even though newer versions are available
 upstream. Porting Replicant to a newer version requires a lot of effort and
-doesn’t bring any significant advantage when it comes to freedom.
+doesn't bring any significant advantage when it comes to freedom.
 
 Regarding the devices we already support that do not match the free
 bootloaders criteria, we are not going to drop development for them, but the
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 c0e6796..98929c7 100644
--- a/markdown/2014_12_replicant-4-2-0003-images-release.md
+++ b/markdown/2014_12_replicant-4-2-0003-images-release.md
@@ -7,20 +7,20 @@ It has been about 6 months since we last released a batch of images. A few
 things of interest were completed in the meantime, so we are rolling out new
 images today.
 
-This release doesn’t bring support for any new device: instead, it mostly
+This release doesn't bring support for any new device: instead, it mostly
 contains stability fixes for the devices we already support. The most
 considerable change in this release is the inclusion of the Samsung-RIL
 rewrite, that was developed this summer. [Samsung-RIL][1] is the component in
 charge of dealing with the modem, the hardware chip that communicates with the
-mobile telephony network. The code that was used since then didn’t have a good
-structure and didn’t meet the code quality standards required to call it
+mobile telephony network. The code that was used since then didn't have a good
+structure and didn't meet the code quality standards required to call it
 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).  
 The new code establishes a sane basis for external contributions, so everyone
-is welcome to dig in and add support for what’s missing.
+is welcome to dig in and add support for what's missing.
 
 Another big achievement in that release is the inclusion of about a dozen
 security fixes, covering issues such as Shellshock, Master key, Fake ID and
@@ -30,17 +30,17 @@ As usual, you can checkout the complete [changelog][2], download the images
 from the [ReplicantImages][3] page and find [installation instructions][4] as
 well as [build guides][5] on the [Replicant wiki][6].
 
-Even though this release doesn’t introduce support for any new device, I have
+Even though this release doesn't introduce support for any new device, I have
 been at work regarding devices that make the best candidates for freedom and
 privacy/security. As mentioned in [an earlier post][7], we are going to focus
 the development effort on a few devices that allow running free bootloaders
-and are either likely to have good modem isolation or don’t have a modem at
+and are either likely to have good modem isolation or don't have a modem at
 all.
 
 Recently, I have been working on adding Replicant support for [Sunxi
 devices][8]. There is a lot of work to do in that area and while nothing was
 released yet, it looks promising. I also spent a considerable amount of time
-working on the LG Optimus Black (P970)’s bootloader. I will be posting [a
+working on the LG Optimus Black (P970)'s bootloader. I will be posting [a
 series of articles][9] about what an incredible journey it has been so far on
 [my personal blog][10] over the next few days. Eventually, the device will be
 properly documented in our wiki and as soon as U-Boot reaches feature
@@ -49,13 +49,13 @@ completeness, it will be time to start porting Replicant to the device!
 **December 20th update:** The full series of articles about freeing the LG
 Optimus Black (P970) is now available:
 
-* [A hacker’s journey: freeing a phone from the ground up, first part][9]
+* [A hacker's journey: freeing a phone from the ground up, first part][9]
 
-* [A hacker’s journey: freeing a phone from the ground up, second part][11]
+* [A hacker's journey: freeing a phone from the ground up, second part][11]
 
-* [A hacker’s journey: freeing a phone from the ground up, third part][12]
+* [A hacker's journey: freeing a phone from the ground up, third part][12]
 
-* [A hacker’s journey: freeing a phone from the ground up, fourth part][13]
+* [A hacker's journey: freeing a phone from the ground up, fourth part][13]
 
  [1]: <http://redmine.replicant.us/projects/replicant/wiki/Samsung-RIL>
 
diff --git a/markdown/2015_01_replicant-at-fosdem-2015.md b/markdown/2015_01_replicant-at-fosdem-2015.md
index 5f80621..0964d87 100644
--- a/markdown/2015_01_replicant-at-fosdem-2015.md
+++ b/markdown/2015_01_replicant-at-fosdem-2015.md
@@ -3,7 +3,7 @@ date: 2015-01-25T09:29:48+00:00
 title: Replicant at FOSDEM 2015
 authors: Paul Kocialkowski
 ---
-This year’s edition of [FOSDEM][1], one of the major free software conferences
+This year's edition of [FOSDEM][1], one of the major free software conferences
 in Europe, is just around the corner! Among the various talks that mention the
 state of free software on [embedded devices][2], I (Paul Kocialkowski) will be
 presenting a talk entitled “[Reached milestones and ongoing development on
@@ -20,7 +20,7 @@ description of the various plans for the work that is left to be done.
 [FOSDEM][1] is also a great opportunity to meet members of the community, so
 do not hesitate to say hi if you bump into me in the [embedded devroom][2] or
 around the place! Remember that face-to-face meetings also allow for verifying
-the [Replicant project’s release key][4]‘s fingerprint and creating a chain of
+the [Replicant project's release key][4]‘s fingerprint and creating a chain of
 trust for verifying the software released by the Replicant project.
 
  [1]: <https://fosdem.org/>
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 f43b5b8..b7e7f17 100644
--- a/markdown/2015_04_whats-happening-or-not-at-replicant.md
+++ b/markdown/2015_04_whats-happening-or-not-at-replicant.md
@@ -21,10 +21,10 @@ Android without random run-time faults. As usual, things are moving very
 slowly due to the lack of time. The next step there will be to submit the
 first batch of LG Optimus Black support for inclusion in upstream U-Boot.
 
-The Replicant code itself hasn’t changed much in the past months, since I am
+The Replicant code itself hasn't changed much in the past months, since I am
 focusing on bootloaders development at this point. In addition, Gitorious is
 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
+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.  
diff --git a/markdown/2015_07_replicant-source-code-hosting-and-rmll-2015.md b/markdown/2015_07_replicant-source-code-hosting-and-rmll-2015.md
index a1e8e67..7dc5001 100644
--- a/markdown/2015_07_replicant-source-code-hosting-and-rmll-2015.md
+++ b/markdown/2015_07_replicant-source-code-hosting-and-rmll-2015.md
@@ -7,8 +7,8 @@ As mentioned a few months ago, Gitorious is closing down and even though the
 Replicant [project page][1] can still be reached there, cloning the
 repositories has been broken for some time. After thoroughly evaluating all
 the hosting possibilities for Replicant (thanks to the many suggestions from
-the community!), we have finally reached a decision. We didn’t want to be
-affiliated with a hosting provider that doesn’t match Replicant’s core values,
+the community!), we have finally reached a decision. We didn't want to be
+affiliated with a hosting provider that doesn't match Replicant's core values,
 that are all about software freedom. In addition, it seemed better not to be
 hosted by a third party, to ensure the security of the source code. These
 criteria left us with very little choice available, but thankfully, we were
@@ -18,7 +18,7 @@ able to comply with them, as the Replicant source code is now hosted by the
 We are very thankful to the FSF for providing us with that solution and the
 hardware required for our needs (the Replicant source code is very large).
 Eventually, we will move all the Replicant source there, as opposed to only
-the parts of CyanogenMod and AOSP that we modified, so that we don’t have to
+the parts of CyanogenMod and AOSP that we modified, so that we don't have to
 rely on any third party at all.
 
 With all those discussions going on, I almost forgot to mention that I will be
@@ -30,9 +30,9 @@ from the ground up][6], in English. In addition, I will be taking part in a
 workshop on free embedded devices in room 219, were I will show a few embedded
 devices running free software.
 
-As usual, everyone is welcome to come, say hi and have a nice chat. It’s also
+As usual, everyone is welcome to come, say hi and have a nice chat. It's also
 possible to verify the [Replicant release GPG key][7] in person to trust the
-verification of our images releases. And of course, I’ll be available to help
+verification of our images releases. And of course, I'll be available to help
 install Replicant on supported devices!
 
  [1]: <https://gitorious.org/replicant>
diff --git a/markdown/2015_07_rmll-feedback-optimus-black-advancement-and-cccamp.md b/markdown/2015_07_rmll-feedback-optimus-black-advancement-and-cccamp.md
index 624f3b7..cd33143 100644
--- a/markdown/2015_07_rmll-feedback-optimus-black-advancement-and-cccamp.md
+++ b/markdown/2015_07_rmll-feedback-optimus-black-advancement-and-cccamp.md
@@ -21,7 +21,7 @@ patches][7] allows booting CyanogenMod without too much trouble, except for
 the occasional random reboot and other oddities that still have to be sorted
 out before it can seriously be used for daily use.
 
-Thus, with basic bootloader support out of the way, it’s time to start the
+Thus, with basic bootloader support out of the way, it's time to start the
 Replicant port to the device. Communication with the modem will require some
 heavy work on [Hayes-RIL][8], our implementation of the AT protocol radio
 interface layer, that is supposed to be more modern and robust than other
@@ -35,7 +35,7 @@ and/or less formal self-organized events. The camp will be a great occasion to
 chat a bit about the current state of the art of software freedom on mobile
 devices, and more! Various other interesting projects will be there as well:
 members of the [Neo900 project][12] will hold the [Neo village][13], where
-I’ll be likely to be found. As usual, I’ll also be available to verify the
+I'll be likely to be found. As usual, I'll also be available to verify the
 Replicant release key fingerprint, help newcomers install Replicant on their
 device and basically anything else that I can help with!
 
diff --git a/markdown/2015_08_replicant-and-friends-at-chaos-communication-camp-2015.md b/markdown/2015_08_replicant-and-friends-at-chaos-communication-camp-2015.md
index 6a61069..0d232ea 100644
--- a/markdown/2015_08_replicant-and-friends-at-chaos-communication-camp-2015.md
+++ b/markdown/2015_08_replicant-and-friends-at-chaos-communication-camp-2015.md
@@ -3,11 +3,11 @@ date: 2015-08-12T18:02:41+00:00
 title: Replicant and friends at Chaos Communication Camp 2015
 authors: Paul Kocialkowski
 ---
-As advertised in the previous blog post, I’ll be at CCCamp 2015 to talk about
-Replicant (as well as other things that I’m working on, like [porting
+As advertised in the previous blog post, I'll be at CCCamp 2015 to talk about
+Replicant (as well as other things that I'm working on, like [porting
 Libreboot to the C201 Chromebook][1]), starting tomorrow.
 
-Formally, I’ll be giving a 45 minute long talk at the [Neo village tent][2] on
+Formally, I'll be giving a 45 minute long talk at the [Neo village tent][2] on
 Sunday, about [Replicant, software freedom and privacy/security on mobile
 devices][3]. In addition, I have asked to give [a lightning talk to highlight
 the necessity to have more developers involved in Replicant][4] on Saturday at
@@ -15,7 +15,7 @@ the necessity to have more developers involved in Replicant][4] on Saturday at
 ensure the growth the project deserves.
 
 People from the [Neo900][5] project will organize the [Neo village][2], where
-I’ll have my tent at, next to Osmocom. As usual, you’re welcome to come and
+I'll have my tent at, next to Osmocom. As usual, you're welcome to come and
 say hi (and possibly verify the [Replicant release public key][6] as well)! I
 may just as well hang around the [Quadrature][7] village, where they have a
 nice tea house set up!
@@ -29,7 +29,7 @@ me a message if you require my presence!
 
 Update: The talks have been added to the [Conferences][11] wiki page.
 Unfortunately, the longer talk on Sunday had to be interrupted because of the
-lightning storm and couldn’t be resumed later. The slides are however
+lightning storm and couldn't be resumed later. The slides are however
 available and hold the main elements of the talk.
 
  [1]: <http://lists.nongnu.org/archive/html/libreboot/2015-08/msg00009.html>
diff --git a/markdown/2015_09_replicant-4-2-0004-images-release.md b/markdown/2015_09_replicant-4-2-0004-images-release.md
index 4d2baa3..1e9aac3 100644
--- a/markdown/2015_09_replicant-4-2-0004-images-release.md
+++ b/markdown/2015_09_replicant-4-2-0004-images-release.md
@@ -4,7 +4,7 @@ title: Replicant 4.2 0004 images release
 authors: Paul Kocialkowski
 ---
 Even though things are moving slowly at Replicant, we figured it was time to
-release another batch of Replicant 4.2 images. [This release][1] doesn’t add
+release another batch of Replicant 4.2 images. [This release][1] doesn't add
 support for any new device, but has a focus on security instead, thanks to an
 active member of the community: Moritz (also known as My Self on the
 [forums][2]). For months, Moritz has been [evaluating whether Replicant is
@@ -16,18 +16,18 @@ Stagefright vulnerability or the Installer Hijacking vulnerability.
 Since the previous release, all the Replicant-specific source code was moved
 over to [git.replicant.us][4], that is gracefully hosted by the FSF. We are
 planning on moving all the Replicant source code over to that new server, so
-that we don’t have to rely on third parties such as CyanogenMod and AOSP to
+that we don't have to rely on third parties such as CyanogenMod and AOSP to
 provide the full source code for Replicant. In the meantime, we have started
 tagging the commits used for each release and signing those tags with the
-[Replicant release key][5], so that it’s possible to reliably retrieve the
+[Replicant release key][5], so that it's possible to reliably retrieve the
 source code for a given Replicant release. Those tags are also combined in the
-release metadata’s [git-tags][6].
+release metadata's [git-tags][6].
 
 For a complete list of changes, you can take a look at the [changelog][7].
 [Installation instructions][8] are available for each device, as well as
 [build guides][9].
 
-You’re welcome to join-in and contribute code to Replicant! [Resources to get
+You're welcome to join-in and contribute code to Replicant! [Resources to get
 started on development][10] are available on the [wiki][11], as well as a list
 of [tasks][12] to improve Replicant.
 
diff --git a/markdown/2015_09_upcoming-events-for-replicant-in-octobernovember-2015.md b/markdown/2015_09_upcoming-events-for-replicant-in-octobernovember-2015.md
index d7e2689..3fdb73a 100644
--- a/markdown/2015_09_upcoming-events-for-replicant-in-octobernovember-2015.md
+++ b/markdown/2015_09_upcoming-events-for-replicant-in-octobernovember-2015.md
@@ -15,11 +15,11 @@ some form of public discussion, such as participation in a round table.
 
 Starting next week-end, Replicant will be at the following events:
 
-* [Brest en Biens Communs][2], October 3, Brest: [Internet aujourd’hui,
+* [Brest en Biens Communs][2], October 3, Brest: [Internet aujourd'hui,
   défendre les libertés][3] round table
 
 * [Brest en Biens Communs][2], October 17, Brest: [Replicant, système
-  d’exploitation libre pour smartphones][4] talk and workshop
+  d'exploitation libre pour smartphones][4] talk and workshop
 
 * [Capitole du Libre][5], November 21-22, Toulouse: Libérer son mobile avec
   Replicant : politique, technique talk
@@ -41,7 +41,7 @@ See you soon!
 
 November update: Due to the recent attacks in Paris, Capitole du Libre was
 canceled and [Bazar du Libre][10] is taking place in Toulouse on November
-21-22. The talk about Replicant was rescheduled in Mix’art Myrys, room 2 at
+21-22. The talk about Replicant was rescheduled in Mix'art Myrys, room 2 at
 3:00 pm.
 
  [1]: <https://www.replicant.us/freedom-privacy-security-issues.php>
diff --git a/markdown/2015_12_shops-selling-devices-pre-installed-with-replicant.md b/markdown/2015_12_shops-selling-devices-pre-installed-with-replicant.md
index 69e50ff..a3452fd 100644
--- a/markdown/2015_12_shops-selling-devices-pre-installed-with-replicant.md
+++ b/markdown/2015_12_shops-selling-devices-pre-installed-with-replicant.md
@@ -5,7 +5,7 @@ authors: Paul Kocialkowski
 ---
 A few months ago, we were contacted to discuss the endorsement of an online
 shop selling mobile devices pre-installed with Replicant: [Qibre Computer
-Hardware][1]. While we’re very happy to see such initiatives being developed,
+Hardware][1]. While we're very happy to see such initiatives being developed,
 we asked for some conditions to be met before endorsing the shop, especially
 conditions that have to do with informing final users:
 
@@ -13,7 +13,7 @@ conditions that have to do with informing final users:
   [freedom][2] and [privacy/security][3]. There are plenty of issues
   remaining, that are explained in general on the [Freedom and
   privacy/security issues page][4] of the website and in greater details on
-  each device’s wiki page (when documented). Those are out of the scope of
+  each device's wiki page (when documented). Those are out of the scope of
   free software support in Replicant, but it is crucial to mention them when
   selling a full device. Linking to these resources is a fine way to ensure
   that customers have access to that information.
@@ -26,8 +26,8 @@ conditions that have to do with informing final users:
 **Qibre has now stopped its activity until further notice.**
 
 A few weeks ago, [Tehnoetic][5] started selling devices pre-installed with
-Replicant and was featured on the FSF’s [Ethical Tech Giving Guide][6] and
-FSFE’s [Free Your Android][7] campaign. At this point, the following devices
+Replicant and was featured on the FSF's [Ethical Tech Giving Guide][6] and
+FSFE's [Free Your Android][7] campaign. At this point, the following devices
 can be bought pre-installed with Replicant from [Tehnoetic][5]:
 
 * [Galaxy S 2 (I9100)][8]: [Tehnoetic S2][9]
diff --git a/markdown/2016_05_coliberator-2016-keynotes-and-workshops.md b/markdown/2016_05_coliberator-2016-keynotes-and-workshops.md
index 87a233a..602a9ff 100644
--- a/markdown/2016_05_coliberator-2016-keynotes-and-workshops.md
+++ b/markdown/2016_05_coliberator-2016-keynotes-and-workshops.md
@@ -10,13 +10,13 @@ Culture, that proposed to host both a keynote and a workshop about Replicant
 at Coliberator this year. The keynote will be a great opportunity to learn
 about freedom and privacy/security in mobile devices. The Replicant workshop
 will showcase devices running Replicant and will be the occasion to get help
-installing Replicant, verify the project’s [release key][3] or just come by
+installing Replicant, verify the project's [release key][3] or just come by
 and have a chat! The [Tehnoetic][4] team will also take part in the workshop,
 with Replicant devices available for sale and more!
 
 Scheduling details are still being worked out by the organization team and
 will be available soon. Either way, note that a [GNU Libreboot][5] keynote and
-workshop will be held as well during Coliberator. This year’s edition of the
+workshop will be held as well during Coliberator. This year's edition of the
 conference will thus highlight freedom at the lower levels in various ways!
 Note that Coliberator is organized by the Ceata team from small individual
 donations, so any [contribution to fund the conference][6] is welcome!
diff --git a/markdown/2016_07_replicant-at-pseshsf-2016.md b/markdown/2016_07_replicant-at-pseshsf-2016.md
index 2200209..fe2ec10 100644
--- a/markdown/2016_07_replicant-at-pseshsf-2016.md
+++ b/markdown/2016_07_replicant-at-pseshsf-2016.md
@@ -11,7 +11,7 @@ possibly other aspects related to freedom at the lower levels).
 The talk will be a great opportunity to learn about freedom and
 privacy/security in mobile devices. The Replicant workshop will showcase
 devices running Replicant and will be the occasion to get help installing
-Replicant, verify the project’s [release key][3] or just come by and have a
+Replicant, verify the project's [release key][3] or just come by and have a
 chat!
 
 As usual, we are looking forward to meeting you there!
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 4bfa94c..2a63e75 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
@@ -69,7 +69,7 @@ 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
+compliant ones. This is also quite confusing since free software isn't
 expected to contain  
 such anti-features in the first place.
 
@@ -93,7 +93,7 @@ be able to work on Android applications, with some time to do so. This is
 exactly the kind of skills required to solve this issue in F-Droid. Getting it
 fixed is crucially important for Replicant.
 
-If you’re interested to jump-in and help resolve this issue, please get in
+If you're interested to jump-in and help resolve this issue, please get in
 touch with us or with F-Droid developers directly to get directions on how to
 get started.
 
diff --git a/markdown/2017_02_replicant-6-0-development-updates.md b/markdown/2017_02_replicant-6-0-development-updates.md
index 8cf3217..d0eee56 100644
--- a/markdown/2017_02_replicant-6-0-development-updates.md
+++ b/markdown/2017_02_replicant-6-0-development-updates.md
@@ -21,13 +21,13 @@ was a great opportunity to discuss and work on various topics related to the
 GTA04. I assisted Lukas Märdian from Goldelico with porting Replicant 6.0 to
 the GTA04 and at the end of the workshop, we were able to boot Replicant 6.0
 and had basic functionality working. Lukas continues to work on the port and
-I’m planning to integrate his changes and get Replicant 6.0 ready for the
+I'm planning to integrate his changes and get Replicant 6.0 ready for the
 GTA04.
 
 ## Support for external WiFi dongles with the AR9271 chipset
 
 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
+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.  
 An alternative is to use an external WiFi dongle with an USB OTG cable. A free
@@ -41,18 +41,18 @@ forum thread][4].
 
 ## Graphics rendering
 
-[ The previous blog post ][5]already metioned that I’m working on the graphics
+[ The previous blog post ][5]already metioned that I'm working on the graphics
 acceleration. Mesa llvmpipe can now be used as an alternative to the Android
 software renderer. Unfortunately, llvmpipe is still too slow and the Android
-software renderer stays the default graphics renderer for now. But it’s
+software renderer stays the default graphics renderer for now. But it's
 possible to use some more apps like Firefox-based browsers with llvmpipe that
-wouldn’t work with the Android software renderer. Llvmpipe also makes it
+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!  
 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
+scanning or in general barcode scanning didn't work with Replicant because the
 software renderer requires a camera preview format that is incompatible with
 barcode scanner apps. I was able to fix it by doing the neccessary conversions
 of preview frames that are requested by barcode scanner apps.
@@ -68,7 +68,7 @@ verifiable and built using only free software.
 
 ## Security/privacy enhancements
 
-Besides fixing various bugs, I’m especially committed to making Replicant more
+Besides fixing various bugs, I'm especially committed to making Replicant more
 secure. Originally, I started contributing to Replicant by submitting patches
 for known security issues in Replicant 4.2. Security updates for the kernel
 and the Android system are included in Replicant 6.0 as quickly as possible,
@@ -81,7 +81,7 @@ Porting Replicant 6.0 to more devices is a priority right now. Besides devices
 that are already supported by Replicant 4.2, some new targets are evaluated.
 An interesting target is the LTE variant of the Galaxy S3 (GT-I9305).
 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 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.  
diff --git a/markdown/2017_04_there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better.md b/markdown/2017_04_there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better.md
index b6a61a6..54db66a 100644
--- a/markdown/2017_04_there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better.md
+++ b/markdown/2017_04_there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better.md
@@ -12,7 +12,7 @@ Replicant 6.0 release. For three previous Replicant versions (2.2, 4.0 and
 Replicant offered its own SDK because the Android SDK released by Google is
 distributed under a non-free license and suggests installing non-free plug-ins
 such as the Google APIs. For a long time, Replicant has provided the only
-Android SDK that is available under a free license and that doesn’t offer to
+Android SDK that is available under a free license and that doesn't offer to
 install non-free software.
 
 **Android SDK in Debian**
diff --git a/markdown/2017_09_a-new-replicant-6-0-release.md b/markdown/2017_09_a-new-replicant-6-0-release.md
index 250cb83..08f4506 100644
--- a/markdown/2017_09_a-new-replicant-6-0-release.md
+++ b/markdown/2017_09_a-new-replicant-6-0-release.md
@@ -3,7 +3,7 @@ date: 2017-09-17T21:45:58+00:00
 title: A new Replicant 6.0 release
 authors: Wolfgang Wiedmeyer
 ---
-A few months have passed since [the initial Replicant 6.0 release][1] and it’s
+A few months have passed since [the initial Replicant 6.0 release][1] and it's
 time for another one. This release more than doubles the number of supported
 devices and contains a few important fixes and improvements. The latest
 changes from LineageOS 13.0 are included. They are mostly security fixes, so
@@ -16,7 +16,7 @@ already supported by Replicant 4.2. These include the [Galaxy Note][2],
 [Galaxy Nexus][3], the [Galaxy Tab 2 7.0][4] and [Galaxy Tab 2 10.1][5]
 models.
 
-There are also two new tablet models that weren’t yet supported by Replicant:
+There are also two new tablet models that weren't yet supported by Replicant:
 the GSM and Wi-Fi-only version of the [Galaxy Note 8.0][6]. The hardware is
 very similar to the Galaxy Note 2 and thus it was quite straightforward to add
 them as new devices. Furthermore, the tablets are not known to have bad modem
@@ -24,7 +24,7 @@ isolation, as the other supported devices. And the working front and back
 camera makes them the currently best supported tablets.
 
 Support for the [GTA04][7] was a goal for this release as well. Some work has
-been done to achieve this goal, but it’s unfortunately not yet ready. It will
+been done to achieve this goal, but it's unfortunately not yet ready. It will
 hopefully be ready when the next release comes around.
 
 ## Improvements and fixes
@@ -34,8 +34,8 @@ hopefully be ready when the next release comes around.
 You can now use USSD messages with Replicant (again). USSD messages are the
 codes you enter to check your available balance, to refill it or to select a
 certain data plan. Depending on your provider, there may be more codes for
-other functionality available. Before Paul’s rewrite of [Samsung-RIL][8] in
-2014, this type of messages could be used, but support for them wasn’t added
+other functionality available. Before Paul's rewrite of [Samsung-RIL][8] in
+2014, this type of messages could be used, but support for them wasn't added
 again after the rewrite, until now. The new implementation features improved
 decoding, most notably for special characters.
 
@@ -51,8 +51,8 @@ to auto-connect to a Wi-Fi network, once the adapter is plugged in.
 Fil also submitted a patch that provides a fix for a very annoying issue with
 the Wi-Fi adapters or with [reverse tethering][9]. So far, network
 connections, that were established using a Wi-Fi adapter or reverse tethering,
-weren’t properly reported to apps. For example, F-Droid wasn’t usable because
-of this. Thanks to Fil’s patch, this issue is now fixed.
+weren't properly reported to apps. For example, F-Droid wasn't usable because
+of this. Thanks to Fil's patch, this issue is now fixed.
 
 It was possible to make all devices that are supported by Replicant 6.0,
 including the newly added ones, usable with certain Wi-Fi adapters. Despite
diff --git a/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md b/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
index 09d8608..b6bce0e 100644
--- a/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
+++ b/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
@@ -14,7 +14,7 @@ terminal devices in achieving an open Internet][2], with a particular focus on
 mobile device. A [first report][3] on this topic was issued at the end of may
 2017, based on consultations with various members of the industry as well as
 non-profits such as [FFDN][4], the federation of non-profit ISPs. This first
-document presents ARCEP’s approach to the application of [EU regulation
+document presents ARCEP's approach to the application of [EU regulation
 2015/2120][5], that gives users specific rights regarding their choice of
 terminal devices. It provides an analysis of the various actors involved with
 terminal devices, making clear distinctions between the hardware, operating
diff --git a/markdown/2017_12_third-replicant-6-0-release.md b/markdown/2017_12_third-replicant-6-0-release.md
index 06e38ef..dac9163 100644
--- a/markdown/2017_12_third-replicant-6-0-release.md
+++ b/markdown/2017_12_third-replicant-6-0-release.md
@@ -22,7 +22,7 @@ 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
+instructions won't work, as they expect you to be able to easily reboot to
 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/2018_01_les-terminaux-sont-ils-le-maillon-faible-de-louverture-dinternet.md b/markdown/2018_01_les-terminaux-sont-ils-le-maillon-faible-de-louverture-dinternet.md
index 937c2c1..5d17926 100644
--- a/markdown/2018_01_les-terminaux-sont-ils-le-maillon-faible-de-louverture-dinternet.md
+++ b/markdown/2018_01_les-terminaux-sont-ils-le-maillon-faible-de-louverture-dinternet.md
@@ -3,97 +3,97 @@ date: 2018-01-10T18:12:47+00:00
 title: Les terminaux sont ils le maillon faible de l’ouverture d’internet ?
 authors: Paul Kocialkowski
 ---
-Les terminaux font aujourd’hui partie de la vie quotidienne de millions
-d’utilisateurs, au travers d’appareils de différents formats et en particulier
-d’appareils mobiles de type smartphone, tablette ou d’ordinateurs portables.
-Ces appareils ont permis de numériser bon nombre d’aspects de la vie, qu’il
-s’agisse des communications entre les individus ou la capture, le stockage et
-l’échange d’informations. Ces appareils disposent en effet de nombreuses
-entrées/sorties permettant de capter et d’interagir avec l’environnement, en
+Les terminaux font aujourd'hui partie de la vie quotidienne de millions
+d'utilisateurs, au travers d'appareils de différents formats et en particulier
+d'appareils mobiles de type smartphone, tablette ou d'ordinateurs portables.
+Ces appareils ont permis de numériser bon nombre d'aspects de la vie, qu'il
+s'agisse des communications entre les individus ou la capture, le stockage et
+l'échange d'informations. Ces appareils disposent en effet de nombreuses
+entrées/sorties permettant de capter et d'interagir avec l'environnement, en
 récoltant et en stockant une très grande quantité de données tout au long de
 chaque journée. Ces données sont très largement stockées au sein
-d’infrastructures de stockage de différentes entreprises, le plus souvent des
+d'infrastructures de stockage de différentes entreprises, le plus souvent des
 multinationales Américaines.
 
 Ces appareils se caractérisent donc par une grande capacité à interagir avec
 les différents aspects du quotidien et une connectivité accrue permettant la
-communication et le partage de données, mais également par l’accès à de
+communication et le partage de données, mais également par l'accès à de
 nombreux contenus et services en ligne. En effet, ces terminaux sont les
-passerelles d’accès pour l’accès rapide au web et à différents types de
+passerelles d'accès pour l'accès rapide au web et à différents types de
 services, qui génèrent un grand nombre de méta-données et forment en cela une
-empreinte numérique de l’utilisateur, qui permettra son identification fine.
-Ces procédés d’identification sont par ailleurs connus pour être mis en œuvre
+empreinte numérique de l'utilisateur, qui permettra son identification fine.
+Ces procédés d'identification sont par ailleurs connus pour être mis en œuvre
 par de nombreuses agences de renseignement.
 
 Les utilisateurs peuvent donc légitimement se poser la question de la
-confiance qu’ils peuvent accorder à ces terminaux, en particulier du point de
-vue de leur fonctionnement et agissements réels vis-à-vis des données qu’ils
-traitent, mais également de leur sécurité, afin de s’assurer que ces données
+confiance qu'ils peuvent accorder à ces terminaux, en particulier du point de
+vue de leur fonctionnement et agissements réels vis-à-vis des données qu'ils
+traitent, mais également de leur sécurité, afin de s'assurer que ces données
 ne sont pas vulnérables et restent effectivement privées. Le contrôle de ces
-appareils apparaît ainsi comme un élément clef, en ce qu’il permet à
-l’utilisateur de s’assurer du bon fonctionnement de l’appareil tout au long de
-son utilisation. Il s’agit pour cela dans un premier temps d’être en mesure
-d’effectuer des audits du code utilisé sur l’appareil et de pouvoir le
-modifier et l’exécuter par la suite. Il devient alors possible pour
-l’utilisateur d’y apporter ses modifications personnelles ou celles de la
+appareils apparaît ainsi comme un élément clef, en ce qu'il permet à
+l'utilisateur de s'assurer du bon fonctionnement de l'appareil tout au long de
+son utilisation. Il s'agit pour cela dans un premier temps d'être en mesure
+d'effectuer des audits du code utilisé sur l'appareil et de pouvoir le
+modifier et l'exécuter par la suite. Il devient alors possible pour
+l'utilisateur d'y apporter ses modifications personnelles ou celles de la
 communauté, de supprimer toute restriction volontaire de fonctionnalité mais
-aussi d’effectuer des audits de sécurité pour identifier les vulnérabilités et
-les portes dérobées et d’apporter des corrections indépendamment des
+aussi d'effectuer des audits de sécurité pour identifier les vulnérabilités et
+les portes dérobées et d'apporter des corrections indépendamment des
 constructeurs des appareils qui prennent rarement en charge les appareils de
-nombreuses années. Il s’agit également par là de garantir l’accès à la
+nombreuses années. Il s'agit également par là de garantir l'accès à la
 connaissance du fonctionnement des appareils, présentant ainsi une opportunité
-pour étudiants, curieux et passionnés d’étudier et de modifier des logiciels
+pour étudiants, curieux et passionnés d'étudier et de modifier des logiciels
 largement utilisés. De plus, la préservation de cette connaissance reste un
 enjeu pour assurer un certain contrôle à long terme de la technologie,
 toujours plus présente, de la part de la société toute entière.
 
 Le règlement Européen 2015/2120 prévoit pour les utilisateurs « le droit
-d’accéder aux informations et aux contenus et de les diffuser, d’utiliser et
-de fournir des applications et des services et d’utiliser les équipements
+d'accéder aux informations et aux contenus et de les diffuser, d'utiliser et
+de fournir des applications et des services et d'utiliser les équipements
 terminaux de leur choix, ». La question du libre choix du terminal ouvre la
-porte à la possibilité pour l’utilisateur de pouvoir choisir des terminaux en
+porte à la possibilité pour l'utilisateur de pouvoir choisir des terminaux en
 lesquels ils peuvent avoir confiance, sur lesquels ils ont le contrôle et dont
 le fonctionnement est connu et largement diffusé. Le projet Replicant
-s’inscrit tout particulièrement dans cette démarche, en développant un système
-d’exploitation entièrement composé de logiciels libres, basé sur le code libre
-d’Android, diffusé par Google. Il s’agit, à partir de cette base libre, de
+s'inscrit tout particulièrement dans cette démarche, en développant un système
+d'exploitation entièrement composé de logiciels libres, basé sur le code libre
+d'Android, diffusé par Google. Il s'agit, à partir de cette base libre, de
 développer les logiciels nécessaires à la prise en charge matérielle de
 différents appareils mobiles, de manière plus ou moins complète mais avec un
-minimum de fonctionnalités disponible. Replicant s’inscrit donc au niveau du
-système d’exploitation, mais les problématiques de la confiance, du contrôle
-et de la connaissance des appareils concernent plus largement l’ensemble des
-composants des appareils mobiles. S’il est en général aujourd’hui possible de
-remplacer le système d’exploitation de ces appareils, la tâche est autrement
-moins aisée pour d’autres composants critiques tels que les logiciels de
-démarrage, qui s’exécutent avant le système d’exploitation, mais également les
-environnements d’exécution de confiance qui s’exécutent pendant toute la durée
-d’utilisation des appareils avec les privilèges les plus élevés sur
-l’appareil. Les appareils qui, en plus de présenter une connectivité TCP/IP à
-l’Internet sont également connectés au réseau GSM disposent d’un composant
+minimum de fonctionnalités disponible. Replicant s'inscrit donc au niveau du
+système d'exploitation, mais les problématiques de la confiance, du contrôle
+et de la connaissance des appareils concernent plus largement l'ensemble des
+composants des appareils mobiles. S'il est en général aujourd'hui possible de
+remplacer le système d'exploitation de ces appareils, la tâche est autrement
+moins aisée pour d'autres composants critiques tels que les logiciels de
+démarrage, qui s'exécutent avant le système d'exploitation, mais également les
+environnements d'exécution de confiance qui s'exécutent pendant toute la durée
+d'utilisation des appareils avec les privilèges les plus élevés sur
+l'appareil. Les appareils qui, en plus de présenter une connectivité TCP/IP à
+l'Internet sont également connectés au réseau GSM disposent d'un composant
 dédié à cette communication mobile, le baseband ou modem. Tout comme les
-logiciels cités précédemment, le logiciel qui s’exécute sur ce modem est bien
+logiciels cités précédemment, le logiciel qui s'exécute sur ce modem est bien
 souvent protégé par une signature numérique qui rend impossible sa
-modification par quiconque ne possède pas la clef privée du fabricant, qu’il
-ne divulgue pas. Il est ainsi impossible d’exécuter du logiciel libre dans ces
-cas de figure, n’offrant ainsi jamais à l’utilisateur une véritable confiance,
+modification par quiconque ne possède pas la clef privée du fabricant, qu'il
+ne divulgue pas. Il est ainsi impossible d'exécuter du logiciel libre dans ces
+cas de figure, n'offrant ainsi jamais à l'utilisateur une véritable confiance,
 ni de véritable contrôle ou une connaissance complète de son fonctionnement.
 
-De cette façon, on retire du pouvoir aux utilisateurs finaux, qu’il s’agisse
-d’individus ou d’entreprises intermédiaires qui utilisent et intègrent ces
-appareils, qui est alors dans les mains du fabricant des appareils. Il s’agit
-ainsi de consacrer l’union entre le matériel d’une part et le logiciel qui
-s’exécute sur celui-ci d’autre part. Pour autant, le logiciel se caractérisant
+De cette façon, on retire du pouvoir aux utilisateurs finaux, qu'il s'agisse
+d'individus ou d'entreprises intermédiaires qui utilisent et intègrent ces
+appareils, qui est alors dans les mains du fabricant des appareils. Il s'agit
+ainsi de consacrer l'union entre le matériel d'une part et le logiciel qui
+s'exécute sur celui-ci d'autre part. Pour autant, le logiciel se caractérisant
 comme des instructions pouvant être modifiées, il est une utilisation tout à
-fait légitime pour l’utilisateur de pouvoir modifier le logiciel s’exécutant
-sur chacun de ses appareils, qui est par nature dissocié de l’aspect matériel
+fait légitime pour l'utilisateur de pouvoir modifier le logiciel s'exécutant
+sur chacun de ses appareils, qui est par nature dissocié de l'aspect matériel
 qui permet son exécution. On souhaite donc particulièrement insister sur cette
-distinction fondamentale, de l’appareil d’une part et du logiciel qu’il
-exécute d’autre part.
+distinction fondamentale, de l'appareil d'une part et du logiciel qu'il
+exécute d'autre part.
 
 Cette capacité de modifier les logiciels présente par sa nature de nombreuses
-opportunités d’innovation par la très grande flexibilité qu’elle offre, qui
-permet l’élaboration d’applications et de services innovants qui sont tout à
-fait de nature à favoriser l’ouverture d’Internet et le développement de
-l’activité qui lui est associée.
+opportunités d'innovation par la très grande flexibilité qu'elle offre, qui
+permet l'élaboration d'applications et de services innovants qui sont tout à
+fait de nature à favoriser l'ouverture d'Internet et le développement de
+l'activité qui lui est associée.
 
 
diff --git a/markdown/2018_03_final-days-for-the-upstream-linux-allwinner-vpu-support-crowdfunding-campaign.md b/markdown/2018_03_final-days-for-the-upstream-linux-allwinner-vpu-support-crowdfunding-campaign.md
index 82036a4..7c09f84 100644
--- a/markdown/2018_03_final-days-for-the-upstream-linux-allwinner-vpu-support-crowdfunding-campaign.md
+++ b/markdown/2018_03_final-days-for-the-upstream-linux-allwinner-vpu-support-crowdfunding-campaign.md
@@ -49,14 +49,14 @@ the Linux kernel][11] for a while.
 
 As the main goal of the campaign was reached within its first week, Maxime
 will be able to work with me on the VPU. His in-depth understanding of the
-[sun4i DRM video driver’s innards][12] will also reveal very useful for
+[sun4i DRM video driver's innards][12] will also reveal very useful for
 accelerating the processing of the frames coming from the VPU (without
 unneeded copies of buffers) and implementing scaling in hardware. In order to
 support the VPU hardware efficiently, a number of changes have to be
 introduced to the Linux kernel. It currently lacks an interface to provide
 coherency between setting specific controls for the media stream and the
 input/output buffers that these controls are related to and should apply to.
-This API has been implemented by Alexandre Courbot (who’s working at Google on
+This API has been implemented by Alexandre Courbot (who's working at Google on
 the Chromium OS project) as the [V4L2 request API][13], that fits the
 requirements for the Allwinner VPU driver. Other VPU drivers, such as the
 [tegra-vde driver][14] that supports the Tegra 20 video decoder engine, also
diff --git a/markdown/2019_01_meeting-point-at-fosdem.md b/markdown/2019_01_meeting-point-at-fosdem.md
index 413b7d2..8f85026 100644
--- a/markdown/2019_01_meeting-point-at-fosdem.md
+++ b/markdown/2019_01_meeting-point-at-fosdem.md
@@ -13,12 +13,12 @@ We encourage everyone to participate and contribute their opinion.
 This meeting will be essential to the future arrangement of Replicant as a
 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.  
+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.  
 
  **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].  
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 3da13a8..980dfec 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
@@ -22,7 +22,7 @@ their devices.
 There were several attempts to add support for devices with free software
 bootloaders in Replicant:
 
-* The LG Optimus black: this smartphone doesn’t prevent users from replacing
+* The LG Optimus black: this smartphone doesn't prevent users from replacing
   the bootloader. Paul Kocialkowsky [did a lot of work][4] to add support
   for this device in upstream u-boot (a free software bootloader) and added
   minimal support for it in the upstream Linux kernel. However support for
@@ -53,15 +53,15 @@ The Replicant project will receive a mobile device, the [NC_1][12] (formerly
 called Necuno Mobile) from its manufacturer (Necuno Solutions), which will
 have a free software bootloader
 
-This device has the size of a smartphone, but doesn’t have a [broadband
+This device has the size of a smartphone, but doesn't have a [broadband
 modem][13]: while users will not be able to use a built-in modem for phone
 calls, SMS or to access the Internet, it is still the best way to be
 completely sure of avoiding any freedom privacy and security issues related to
 broadband modems and the cellular network. It will also require less work to
 add support for this device in Replicant.
 
-Even if it’s possible to disable the modem on some of the mobile devices
-currently supported by Replicant [by not loading the modem’s code][14], some
+Even if it's possible to disable the modem on some of the mobile devices
+currently supported by Replicant [by not loading the modem's code][14], some
 nonfree software still run on these mobile devices. This includes the
 bootloader and potentially any other nonfree software that it may load.
 Because of that we cannot be 100% sure that the modem is completely disabled.
diff --git a/markdown/2019_06_replicant-contributors-meeting-the-2728-july-in-france.md b/markdown/2019_06_replicant-contributors-meeting-the-2728-july-in-france.md
index cde78f5..7d171cf 100644
--- a/markdown/2019_06_replicant-contributors-meeting-the-2728-july-in-france.md
+++ b/markdown/2019_06_replicant-contributors-meeting-the-2728-july-in-france.md
@@ -7,7 +7,7 @@ authors: GNUtoo
 A Replicant contributors meeting will take place in or near Paris in France
 the 27 and 28 July 2019.
 
-As we are still looking for a place to host the meeting, we don’t have a
+As we are still looking for a place to host the meeting, we don't have a
 definitive address yet.
 
 It will be open to anyone who contributes or wants to contribute to the
diff --git a/markdown/2019_07_graphics-support-for-replicant-9.md b/markdown/2019_07_graphics-support-for-replicant-9.md
index 8d2d97e..1d7fcc0 100644
--- a/markdown/2019_07_graphics-support-for-replicant-9.md
+++ b/markdown/2019_07_graphics-support-for-replicant-9.md
@@ -16,7 +16,7 @@ previously on LKML][1]. The devfreq module was also disabled as a workaround
 for graphics corruption issue that happened due to too low clock speeds. Mesa
 on the other hand required us to whitelist Exynos DRM driver to be used with a
 software rendering driver called kms_swrast. After these tiny changes we were
-already able to use the Mesa’s software rendering backend called softpipe!
+already able to use the Mesa's software rendering backend called softpipe!
 Unfortunately, softpipe turned out to be unusably slow even after using HW
 overlay planes to offload some of the buffer compositions to the Exynos 4412
 display controller found on the Samsung Galaxy S3.
diff --git a/markdown/2019_12_replicant-36c3.md b/markdown/2019_12_replicant-36c3.md
index f6b121d..386146b 100644
--- a/markdown/2019_12_replicant-36c3.md
+++ b/markdown/2019_12_replicant-36c3.md
@@ -8,7 +8,7 @@ Starting on December 27th, the [36th Chaos Communication Congress (36C3)][1]
 is taking place in Leipzig. Replicant will be there as part of the [Critical
 Decentralization Cluster][2].
 
-[Replicant’s assembly][3] will feature demos of the current Replicant 6 as
+[Replicant's assembly][3] will feature demos of the current Replicant 6 as
 well as the upcoming Replicant 9. It is the place to come by if you need some
 help installing Replicant or general advice regarding software freedom on
 smartphones and tablets. You can also take the opportunity to verify the
@@ -23,7 +23,7 @@ spots around the congress:
 * [Introduction to Replicant][5] – December 27 19:15, Central
   Decentralization Cluster (CDC) stage
 
-* [Android’s build system is messier than your distro’s][6] – December 28
+* [Android's build system is messier than your distro's][6] – December 28
   20:30, Lecture Room M1
 
 * [Extending the lifetime of smartphones with Replicant][7] – December 28
diff --git a/markdown/2020_01_replicant-at-fosdem-2020.md b/markdown/2020_01_replicant-at-fosdem-2020.md
index ec3799a..def1d6c 100644
--- a/markdown/2020_01_replicant-at-fosdem-2020.md
+++ b/markdown/2020_01_replicant-at-fosdem-2020.md
@@ -8,7 +8,7 @@ As happens every year, [FOSDEM][1] is taking place on the first weekend of
 February. Several Replicant contributors will be at the event, eager to meet
 with other people interested in the project.
 
-During Saturday Replicant will share a little corner on Technoethical’s stand.
+During Saturday Replicant will share a little corner on Technoethical's stand.
 There will be flyers, stickers and some phones running demo versions of
 Replicant 9.
 
@@ -23,7 +23,7 @@ Later that day, Replicant is having a Birds of a Feather (BoF) meeting:
 The meeting is open for everyone interested in the Replicant project (users,
 developers, devices vendors, etc.). Access is public and free as in beer.
 
-Here’s a non-exhaustive list of the topics that will be up for debate:
+Here's a non-exhaustive list of the topics that will be up for debate:
 
 * Replicant 9 status on the i9300/i9305: bootloader, modem, LCD, audio,
   graphics.
@@ -50,10 +50,10 @@ Here’s a non-exhaustive list of the topics that will be up for debate:
 
 * Relationship with LineageOS on supporting the Galaxy SIII.
 
-If there’s any other topic you deem as relevant please let us know in the
-comment section, mailing list or IRC. Everyone’s point of view is welcomed.
+If there's any other topic you deem as relevant please let us know in the
+comment section, mailing list or IRC. Everyone's point of view is welcomed.
 
-On Sunday’s afternoon, there will be a talk at the Hardware Enablement devroom
+On Sunday's afternoon, there will be a talk at the Hardware Enablement devroom
 on the topic of “Extending the lifetime of smartphones with Replicant”:
 
 * Location: room K.4.401, ULB, Brussels, Belgium
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 63ebc6a..4ece681 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
@@ -12,23 +12,23 @@ Edit 3: Added Epilogue
 
 In the summer 2019, in the Replicant contributors conference in Paris, the
 people present were all in favor of not supporting devices with battery that
-can’t easily be replaced, because it would make the use and development of
+can't easily be replaced, because it would make the use and development of
 Replicant for these devices too complicated.
 
 In subsequent conference like the FOSDEM 2020, and in discussions with other
-Replicant users and/or contributors, people didn’t have objections to the
+Replicant users and/or contributors, people didn't have objections to the
 decision.
 
-Even if we don’t want to support such devices in Replicant, we are still open
+Even if we don't want to support such devices in Replicant, we are still open
 to collaborate with people wanting to add support for such devices in other
 projects. For instance we still support the Galaxy S and the Nexus S in
 libsamsung-ipc while the devices are not supported anymore in Replicant, and
-we also do accept patches for devices we don’t want to support in Repliant.
+we also do accept patches for devices we don't want to support in Repliant.
 
 So in practice, some tablets like the Galaxy Tab 2 have battery that are not
 removable in the usual sense as you cannot remove the battery, without any
 tools, while walking, but the battery can still be replaced with the help of
-basic tools like tweezers and screwdrivers. In addition people don’t
+basic tools like tweezers and screwdrivers. In addition people don't
 necessarily expect tablets to last one full day. So we still intend to support
 such devices.
 
@@ -41,7 +41,7 @@ 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
 devices like that.
 
-Given the impact of the decision (most newer phones don’t have non removable
+Given the impact of the decision (most newer phones don't have non removable
 batteries), even if that decision seem sound in theory, we also wanted to test
 it in practice, to be really sure it was the right decision.
 
@@ -50,14 +50,14 @@ when adding support for a smartphone that has a non replaceable battery.
 
 We also wanted to measure how much time was needed to add support for a device
 as fast as possible, because if we supported devices without a replaceable
-battery, we would need to rush to add support for the device while it’s still
+battery, we would need to rush to add support for the device while it's still
 being sold new in order to maximize the lifetime of the device under
 Replicant. Otherwise, people would need to buy the device second hand, where
 the battery would potentially not last a full day anymore.
 
 ## Choosing a device
 
-We didn’t want to spend too much time on that experiment, so we didn’t do much
+We didn't want to spend too much time on that experiment, so we didn't do much
 research and choose the first phone that would match what we were looking for.
 
 We wanted the most recent device device with:
@@ -79,7 +79,7 @@ compatible with Heimdall.
 
 So we choose a Samsung SM-N930F which meets all the requirements above. It
 also has an Exynos 8890, 4GiB of RAM, a stylus and runs Android 6. We wanted
-to have a stylus and a lot of RAM because as we didn’t really intend to add
+to have a stylus and a lot of RAM because as we didn't really intend to add
 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:
@@ -88,14 +88,14 @@ supporting this device or similar devices:
 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.
-  * Having 4GB of RAM should be good enough to run many common applications and desktops. It also means that the phone could be supported for a longer time if there weren’t other factors like the non-removable battery that would prevent that.
+  * Having 4GB of RAM should be good enough to run many common applications and desktops. It also means that the phone could be supported for a longer time if there weren't other factors like the non-removable battery that would prevent that.
 
 As for Replicant, the software support for this device is very similar to the
 Galaxy S7 which is supported by LineageOS.
 
 Unfortunately, the device we chose has shared memory between the modem and the
 system on a chip[1] but as this was just for a quick experiment and that we
-didn’t intend to add support for it in libsamsung-ipc, we just ignored that
+didn't intend to add support for it in libsamsung-ipc, we just ignored that
 issue in order to spend the last amount of time possible.
 
 ## References:
@@ -105,7 +105,7 @@ issue in order to spend the last amount of time possible.
 # Getting the device
 
 The first problem we had was finding the device. We started looking locally,
-including in second hand websites, but we didn’t manage to find any. So after
+including in second hand websites, but we didn't manage to find any. So after
 that we started looking in international second hand websites, and we found
 one.
 
@@ -115,10 +115,10 @@ that this was somewhat related to the non-replaceable battery, though some
 Galaxy S7 could still be found.
 
 However for some reasons, even if the device was shipped, as we have proof
-that it was sent to the post office, we didn’t receive it. We are still
-investigating why, but we didn’t manage to get a conclusive answer yet from
+that it was sent to the post office, we didn't receive it. We are still
+investigating why, but we didn't manage to get a conclusive answer yet from
 the shipping company as we were redirected from service to service and no one
-seem to know why the device didn’t reach its destination. The issue is also
+seem to know why the device didn't reach its destination. The issue is also
 unrelated to COVID-19 as it was shipped by the person many months before it
 was declared a pandemic.
 
@@ -126,14 +126,14 @@ So we started again to look for a device and finally found a second device.
 The offer was really strange. It tell that they disguised the device to look
 like another one to make shipping work.
 
-This didn’t surprise us, as some customs are already actively fighting against
+This didn't surprise us, as some customs are already actively fighting against
 the right to repair devices[1]. So at the time we though it was because they
 decided to fight against the second hand market as well.
 
 In that offer, the person giving the device away also had a strange request:
 she would not charge for the phone but she wanted us to get the data out of
-the phone. The person explained to us that she didn’t trust nor Google nor
-Samsung with her data, which included private pictures but didn’t manage to
+the phone. The person explained to us that she didn't trust nor Google nor
+Samsung with her data, which included private pictures but didn't manage to
 get her data out of the device. As the request seemed legitimate we agreed to
 try but as we are not expert in rooting that it might have failed. The data
 was not encrypted so it also would have made things easier.
@@ -147,7 +147,7 @@ was not encrypted so it also would have made things easier.
 Working with that device was not easy. The first issue we got was that the
 battery would not charge at all, and the battery indication was at 0%.
 
-This explained why the person wasn’t able to extract her data from the device.
+This explained why the person wasn't able to extract her data from the device.
 
 We found on XDA that it was possible to get the battery charge again if we
 managed to downgrade the phone OS. This looked very strange. We also learned
@@ -160,10 +160,10 @@ that is supposed to only affect the the devices fused with the version 2.
 Maybe it was because the battery was already very discharged that it did that,
 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
+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  
+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  
 if the website we downloaded them from had some arrangement with Samsung or
 not.
 
@@ -183,7 +183,7 @@ We have summarized our attempts in the RootingDevices[1] page of the Replicant
 wiki. We still need to update it to add information about our attempts with
 the SM-N930F.
 
-As we didn’t find any rooting application in F-Droid, and that we didn’t want
+As we didn't find any rooting application in F-Droid, and that we didn't want
 to use nonfree applications to root the device, we instead started looking at
 vulnerabilities that enabled us to get root. For each vulnerability we looked
 if the kernel version of the device was affected, and if so we looked for free
@@ -211,15 +211,15 @@ Each time we wanted to flash an image with Heimdall, we had to wait for hours
 for the device to charge a tiny bit.
 
 The stress of the developer working on the device increased a lot because the
-device was potentially always on, and we didn’t know when it had the ability
-to record conversations or not, as we didn’t do a review of its freedom,
+device was potentially always on, and we didn't know when it had the ability
+to record conversations or not, as we didn't do a review of its freedom,
 privacy and security issues.
 
-The developer’s passwords could be revealed as well, by recording the noise of
+The developer's passwords could be revealed as well, by recording the noise of
 his keyboard, and even GPG keys can be reconstructed through noise if they are
 used intensively.
 
-In order to preserve the developer’s sanity and the security of the Replicant
+In order to preserve the developer's sanity and the security of the Replicant
 project, the device was kept in the fridge most of the time.
 
 This was very weird for the people visiting that developer as he had to put
@@ -228,13 +228,13 @@ the device in the fridge each time people came by.
 Sometimes he forgot to put the device in the fridge and started to have
 political and/or intimate conversation and at some point he remembered the
 device and had to go put it in the fridge in the middle of the conversations.
-That was very weird. Especially the “Can you wait a second? I’ve to put the
+That was very weird. Especially the “Can you wait a second? I've to put the
 phone in the fridge.” part.
 
 In addition to all these issues, we also had the device crash during
-development, however we couldn’t wait until the battery was fully depleted as
-the battery didn’t charge. We had to hope that the device wound not go in some
-mode where we were stuck. However it didn’t happen, and we always managed to
+development, however we couldn't wait until the battery was fully depleted as
+the battery didn't charge. We had to hope that the device wound not go in some
+mode where we were stuck. However it didn't happen, and we always managed to
 recover.
 
 Then one day, around when the COVID-19 confinement started, when he was away
@@ -272,8 +272,8 @@ dismissed:
 
 * The “explosive device” was in fact the Samsung SM-N930F, which is best
   known as Galaxy Note 7. As many other people also had one at some point,
-  the court dismissed that charge, especially because this wasn’t done on
-  purpose. The judge also said that they couldn’t condemn people for being
+  the court dismissed that charge, especially because this wasn't done on
+  purpose. The judge also said that they couldn't condemn people for being
   stupid, not remembering about the issue, and relying on the outdated
   offline version of Wikipedia through Kiwix to do research on hardware.
 
@@ -285,7 +285,7 @@ dismissed:
   copyright.
 
 * The violation of trade secrets was also dismissed, even if printed
-  schematics were found on the developer’s table. As the schematics were
+  schematics were found on the developer's table. As the schematics were
   published online in many forums like XDA, they were also considered as
   fair use. Various leaked documents like the Snowden documents, or
   Wikileaks revelations were also used during the case to prove that some
@@ -299,7 +299,7 @@ dismissed:
 
 * Refusing to give encryption key of his hard disks: with a lot of pressure
   from many associations, this was dismissed as it was merely an excuse to
-  get access to the developer’s data and it was not relevant to the case.
+  get access to the developer's data and it was not relevant to the case.
   The same applied with his refusal of handling any of this account data
   (which also includes the passwords giving access to the Replicant
   infrastructure).
@@ -327,8 +327,8 @@ Subpoena and other declarations:
   more constructive things like adding support for phones with a removable
   battery only.” to which the developer agreed.
 
-* He also declared that rushing to add support for a phone wasn’t a good
-  idea either, as because of that, he didn’t realize that the device was a
+* He also declared that rushing to add support for a phone wasn't a good
+  idea either, as because of that, he didn't realize that the device was a
   Galaxy Note 7.
 
 He got a suspended sentence of 3 months for all that.
@@ -342,80 +342,80 @@ turned out to be very fun.
 As the developer had to sign a document with all the hardware on it, to get it
 back, the following conversations occurred when filling the list of hardware:
 
-* Employee: What’s this thing?
+* Employee: What's this thing?
 
-* Developer: It’s a UART adapter for smartphone, you know behind the USB
+* Developer: It's a UART adapter for smartphone, you know behind the USB
   connector there is [very long technical explanations].
 
-* Employee: Let’s write “UART adapter for smartphone”.
+* Employee: Let's write “UART adapter for smartphone”.
 
 * Developer: It also probably works on tablets you know, and it can also do
   many other things other than UART, like power on the phone and switch
   modes [very long technical explanations].
 
-* Employee: Let’s write “complicated computer hardware”.
+* Employee: Let's write “complicated computer hardware”.
 
 Or:
 
-* Employee: What’s this thing?
+* Employee: What's this thing?
 
-* Developer: It’s a hardware to trace the protocol between the SIM card and
+* Developer: It's a hardware to trace the protocol between the SIM card and
   the phone modem, there is a standard called terminal profile which has
   many privacy implications like [very long explanations].
 
-* Employee: Let’s write “SIM card tracker”.
+* Employee: Let's write “SIM card tracker”.
 
-* Developer: It can’t track SIM cards at all, but it can trace the protocol
+* Developer: It can't track SIM cards at all, but it can trace the protocol
   [very long explanation again].
 
-* Employee: Sigh, let’s write “complicated computer hardware” again.
+* Employee: Sigh, let's write “complicated computer hardware” again.
 
 Or:
 
-* Employee: What’s this laptop? It’s a laptop, right?
+* Employee: What's this laptop? It's a laptop, right?
 
-* Developer: It’s a Thinkpad X200, which is a computer capable of running
+* Developer: It's a Thinkpad X200, which is a computer capable of running
   Libreboot, this has many freedom implications like [very long
   explanations].
 
-* Employee: Let’s write “vintage computer”.
+* Employee: Let's write “vintage computer”.
 
 * Developer: But I use that computer you know [very long explanations].
 
-* Employee: Sigh, let’s write “complicated computer hardware” again.
+* Employee: Sigh, let's write “complicated computer hardware” again.
 
 Or:
 
-* Employee: What’s that? Is it a very complicated smartphone?
+* Employee: What's that? Is it a very complicated smartphone?
 
-* Developer: It’s just a usual Galaxy S II (GT-I9100G).
+* Developer: It's just a usual Galaxy S II (GT-I9100G).
 
-* Employee: Let’s write “Galaxy S II”.
+* Employee: Let's write “Galaxy S II”.
 
-* Developer: I’ve also a Galaxy S II (GT-I9100) which has a very different
+* Developer: I've also a Galaxy S II (GT-I9100) which has a very different
   system on a chip [very long explanations].
 
-* Employee: Sigh, let’s write “complicated computer hardware” again.
+* Employee: Sigh, let's write “complicated computer hardware” again.
 
 Or even:
 
-* Employee: What’s that?
+* Employee: What's that?
 
-* Developer: I don’t know
+* Developer: I don't know
 
-* Employee: You don’t know? Is it yours?
+* Employee: You don't know? Is it yours?
 
-* Developer: Yes, but I don’t know how to describe what it is, you can think
+* Developer: Yes, but I don't know how to describe what it is, you can think
   of it like an Arduino running GNU/Linux, back in the days before any of
   the single board computer had systems to automatically detect hardware
   [very long explanations].
 
-* Employee: What’s an Arduino [interrupting the developer]?
+* Employee: What's an Arduino [interrupting the developer]?
 
 * Developer: [very long explanations starting].
 
 * Employee: Sorry [interrupting the developer], bad idea, forget about my
-  question, let’s again write “complicated computer hardware”.
+  question, let's again write “complicated computer hardware”.
 
 At the end the developer got it all back, and the staff said it was the
 strangest set of seized equipment they ever seen.
@@ -424,7 +424,7 @@ He then was unavailable during a full week, as he was reflashing all the
 “complicated computer hardware” for security reasons. That meant that in
 practice he had to reinstall Libreboot[1] or other fully free versions of
 Coreboot that he used, Parabola[2] on all the desktops, laptops, servers,
-single board computers and smartphones that weren’t fully encrypted,
+single board computers and smartphones that weren't fully encrypted,
 reinstalling Replicant on some other smartphones and tablets, reinstalling
 LibreCMC[3] on various devices like WiFi access points, reinstalling various
 microcontroller projects like frser-duino[4] on his flasher, ralim/ts100[5] on
@@ -437,13 +437,13 @@ have been a different story.
 
 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.
+the SM-N930F but we can't know as we didn't try to recover any data.
 
-The only device he didn’t got back was the Samsung SM-N930F, as it was
+The only device he didn't got back was the Samsung SM-N930F, as it was
 probably kept or disposed by the Justice Department.
 
 About the lost of the device, the developer commented: “I lost weeks [of work]
-because of that shitty phone”, “I don’t want that phone anywhere near me.”.
+because of that shitty phone”, “I don't want that phone anywhere near me.”.
 
 It turned out that, in addition to his allergy to nonfree software, freedom
 and privacy violations, that developer now became allergic to non-replaceable
@@ -471,32 +471,32 @@ by several real events.
 * It contains several logic flaws that might have been spotted by attentive
   readers or people used to the [zététique][2] techniques. For instance the
   device was chosen to enable sharing work with GNU/Linux, yet, support for
-  Replicant 6 is added in a way that doesn’t benefit at all code sharing
+  Replicant 6 is added in a way that doesn't benefit at all code sharing
   with GNU/Linux at all as no support for that device is added in
   libsamsung-ipc. The fact that it was not clearly marked as a fiction was
   intended to help people test their critical thinking.
 
-* It’s meant to criticize the systemic causes that resulted in the issue
+* It's meant to criticize the systemic causes that resulted in the issue
   with the Samsung Galaxy Note 7 smartphone. The Wikipedia article on the
   [Samsung Galaxy Note 7][3] has very interesting information on the impacts
   of the issue.
 
-* It’s interesting to see how Samsung used the control it had on such
+* It's interesting to see how Samsung used the control it had on such
   devices, to remotely disable them. That control could be abused. This
   could also be an issue if people have important private data in it, that
-  they weren’t willing to share with companies with huge track record of
+  they weren't willing to share with companies with huge track record of
   users abuse. So instead of having to adapt to every design choice of the
-  smartphone industry, like non-replaceable battery, it’s sometimes better
+  smartphone industry, like non-replaceable battery, it's sometimes better
   to start from limiting as much as possible the damage to users freedom and
   the environment, and try to adapt that to various uses cases instead.
   Here, having user removable batteries would be way more efficient than
   control over users devices for avoiding such issues or dealing with
   batteries that explodes or catch fire. Many manufacturers [had to recall
-  batteries][4] over the years, and the impact weren’t as bad as with the
+  batteries][4] over the years, and the impact weren't as bad as with the
   Galaxy Note 7.
 
-* As far as we know, that event didn’t make smartphone manufacturers switch
-  back to user removable batteries. Samsung didn’t even add back non-
+* As far as we know, that event didn't make smartphone manufacturers switch
+  back to user removable batteries. Samsung didn't even add back non-
   removable batteries to the [Galaxy Note 8][5] , which is the next model in
   the Galaxy Note series. If software or hardware that was threatening some
   economic or political power was the cause of issues that big, the reaction
diff --git a/markdown/2020_07_late-report-from-fosdem-2020.md b/markdown/2020_07_late-report-from-fosdem-2020.md
index 6e43634..cf93c2b 100644
--- a/markdown/2020_07_late-report-from-fosdem-2020.md
+++ b/markdown/2020_07_late-report-from-fosdem-2020.md
@@ -7,7 +7,7 @@ authors: dllud
 On the 1st and 2nd of February 2020, 4 Replicant contributors (FilBerg,
 GNUtoo, GrimKriegor and dllud) attended [FOSDEM 2020][1] in Brussels.
 
-FOSDEM (Free and Open source Software Developers’ European Meeting) is an
+FOSDEM (Free and Open source Software Developers' European Meeting) is an
 annual conference organized by volunteers, to enable users and contributors to
 meet and promote the widespread use of free and open source software. This
 helps communities take decisions and also enables various communities and
@@ -16,13 +16,13 @@ people to collaborate together.
 Part of this comes from FOSDEM allowing projects to book rooms in order to
 have meetings and presentations (dubbed as a BoF, Birds of a Feather).
 Replicant contributors held such a BoF, and also gave a talk at another room
-and wandered around the exhibition’s rooms talking to people at the stands of
+and wandered around the exhibition's rooms talking to people at the stands of
 relevant projects.
 
 As it is a conference, the FOSDEM also features talks by various members and
 contributors of the free software and open source communities which range
 across many different projects and areas. Listening to the talks (which are
-often recorded as well) is a way to get the latest news of what’s happening in
+often recorded as well) is a way to get the latest news of what's happening in
 the free software world.
 
 This is a (late, sorry for that) report with the relevant information that
@@ -37,11 +37,11 @@ both mediums.
 
 Technoethical is a store that sells devices pre-installed withofficial
 versions of Replicant and also Replicant merchandise. It is [featured at
-Replicant’s website][3] and donates a percentage of its sales to Replicant.
+Replicant's website][3] and donates a percentage of its sales to Replicant.
 
 We went to the Technoethical stand to discuss the idea of only requiring a
-percentage of the sales for bigger companies, which wouldn’t include
-Technoethical. According to Tiberiu from Technoethical, Technoethical didn’t
+percentage of the sales for bigger companies, which wouldn't include
+Technoethical. According to Tiberiu from Technoethical, Technoethical didn't
 agree toformally give any percentages of the sales to Replicant, but they
 instead do it voluntarily.
 
@@ -59,7 +59,7 @@ Unfortunately, this property by itself cannot tell precisely which version of
 Replicant is compatible with say the Galaxy Nexus (GT-I9250). We were told to
 look into the qualifier to see if we can find a way to express that.
 
-After looking at it we found that it’s possible to add a platform qualifier
+After looking at it we found that it's possible to add a platform qualifier
 for a given version, for instance to tell that Replicant 6.0 is compatible
 with the Galaxy SII (GT-I9100). However, after this, it is not possible to add
 an extra layer of qualifiers to tell for instance that the Galaxy SIII 4G
@@ -86,7 +86,7 @@ This year we improved the organization of the Replicant BoF:
 * While things were more organized than last year we still need to improve
   on it. For instance we lacked a precise schedule for the BoF in order to
   properly cover all the topics we needed to. The consequence is that we
-  usually try to rush at the end in order to cover some topics we didn’t
+  usually try to rush at the end in order to cover some topics we didn't
   have covered yet.
 
 * We also had the ability to remotely listen to the BoF through Mumble and
@@ -110,7 +110,7 @@ This year we improved the organization of the Replicant BoF:
 
 During the BoF, we did a quick presentation of the issues we were having with
 the Android build system. More details on the issues are available on the
-[“Android’s build system is messier than your distro’s” talk][8] that was
+[“Android's build system is messier than your distro's” talk][8] that was
 presented at 36C3.
 
 ### GeckoView
@@ -178,7 +178,7 @@ reusing the Replicant 9 code.
 
 This means that we would need to work with other upstreams to find the best
 ways to deal with it and share the maintenance of the code. Unfortunately
-there weren’t any contributors from other Android distribution in the room.
+there weren't any contributors from other Android distribution in the room.
 
 ### Galaxy SIII (GT-I9300), Replicant 9 and LineageOS
 
@@ -187,7 +187,7 @@ we collaborated together when it was possible, as we were both trying
 different approaches.
 
 On Replicant 9 we were focusing more on the 2D graphics, and on the modem,
-which doesn’t work yet with LineageOS.
+which doesn't work yet with LineageOS.
 
 Once we have something usable on Replicant 9, it would also be very
 interesting to find time to work on upstreaming the modem driver as well:
@@ -195,7 +195,7 @@ interesting to find time to work on upstreaming the modem driver as well:
 * In several cases the kernel maintainers refused patches for drivers
   lacking free software userspace for using them.
 
-* As Replicant has a free software implementation, it shouldn’t be a
+* As Replicant has a free software implementation, it shouldn't be a
   problem.
 
 * Similar modems are already supported by the Linux kernel, like the N900
@@ -219,12 +219,12 @@ would need to review by themselves each application they are considering to
 install.
 
 So we created the [F-DroidAndApplications wiki page][12] to share the work on
-reviewing F-Droid applications that meet or don’t meet the Free System
+reviewing F-Droid applications that meet or don't meet the Free System
 Distributions Guidelines.
 
 We started reviewing some applications. Unfortunately, even when the source
 code should be fully free, we are not sure if the resulting builds meet the
-guidelines, as we would need to make sure that it’s possible to compile the
+guidelines, as we would need to make sure that it's possible to compile the
 same application with a distribution that meets the FSDG guidelines.
 
 We need to look more into it and/or to write to the licensing team at the FSF.
@@ -251,7 +251,7 @@ enables to get access to the serial port.
 It is therefore relevant to know about that chip in many different contexts.
 
 MediaWiki has ways to avoid the duplication of some information through
-templates, and it’s also possible to interface it with Wikidata in various
+templates, and it's also possible to interface it with Wikidata in various
 ways.
 
 Someone mentioned that Sphinx handles such requirements. However, as not
@@ -266,7 +266,7 @@ tools like Sphinx.
 Someone pointed out that upstream Android continuously gets security updates.
 To keep up with that, we would need to do Replicant 9 releases very often.
 
-While some people pointed issues with rebasing our work, it’s probably still
+While some people pointed issues with rebasing our work, it's probably still
 achievable to do that, as porting our work forward from Android 9 to the next
 Android versions is supposed to be easier.
 
@@ -274,14 +274,14 @@ Someone also pointed out that, for a given Android version, LineageOS was
 backporting security fixes longer than the Android Open Source Project (AOSP).
 
 This information made us reconsider some design choices in Replicant: once
-Replicant 9 has been released, the fact that LineageOS doesn’t have stable
+Replicant 9 has been released, the fact that LineageOS doesn't have stable
 tags for releases becomes less relevant as we will need to find ways to rebase
 and release often, in order to have the latest security fixes.
 
 ### Vulkan
 
 Someone mentioned that the Vulkan graphics API will become mandatory after
-Android 10. This would mean that the graphics stack we’re developing for
+Android 10. This would mean that the graphics stack we're developing for
 Replicant 9 would no longer suffice. Both Lima, the free software driver for
 the Mali GPU present on the Galaxy SIII (GT-I9300), and llvmpipe, the software
 rasterizer planned to be used as fallback on all other devices, only support
@@ -298,19 +298,19 @@ lower-level API than OpenGL][17], with finer-grained control of the GPU memory
 and likes, making it really hard to implement OpenGL on top of it.
 
 A nice tip we got is to keep using a compositor (SurfaceFlinger) that works
-with OpenGL ES. Current SurfaceFlinger still doesn’t have Vulkan support.
+with OpenGL ES. Current SurfaceFlinger still doesn't have Vulkan support.
 Acceleration is still done through OpenGL ES or an hardware composer. As such,
-compositor performance and compatibility won’t bean issue for the time being.
+compositor performance and compatibility won't bean issue for the time being.
 
 ## After the Replicant BoF
 
 ### Replicant contact address
 
 We found that Fil Bergamo, who is part of the Replicant Steering Committee,
-didn’t receive emails from the Replicant contact address.
+didn't receive emails from the Replicant contact address.
 
 We need to setup a new email infrastructure in order to properly address this
-issue. Currently the contact address is hosted at PaulK’s personal email
+issue. Currently the contact address is hosted at PaulK's personal email
 server. Paul no longer has time to maintain it and thus we must transition to
 a new server, hosted in a VM at the FSF servers, that can be administered by
 several Replicant contributors, in order to avoid a single point of failure.
@@ -352,7 +352,7 @@ So the device would have been completely usable with fully free software. They
 also stated in several places on their website that it would have been
 possible to run fully free software on the device.
 
-This was also made possible because the device wasn’t a smartphone and would
+This was also made possible because the device wasn't a smartphone and would
 not have any modem or WiFi chip.
 
 But they are now are planning to add a WiFi chip, and to ourknowledge, all the
@@ -366,7 +366,7 @@ times, with a precision of 10 or 20 meters.
 
 In the long run, for the WiFi firmwares, it would be a good idea to have
 people working to get free WiFi firmwares and really solve the issue for good,
-instead of finding workarounds that don’t solve the problem.
+instead of finding workarounds that don't solve the problem.
 
 In the mean time, the workarounds still have the benefit of making clear what
 is free software and what is not; this clear separation enables us to claim at
@@ -377,7 +377,7 @@ software as well.
 Necunos also told us that they had some underlying issues because their
 devices would be “dual use” devices. This is related to the fact that they are
 also targeting some markets like the Finish defense or secret services, but we
-didn’t understood what it meant practically speaking.
+didn't understood what it meant practically speaking.
 
 ### NLnet and the Android build system
 
@@ -406,7 +406,7 @@ some phones, were still used.
 
 We also saw Maemo Leste on a PinePhone. On this device, the graphics stack was
 using the free software Lima driver and the graphics were fast enough. We
-can’t remember if Lima was stable enough for daily use but it looks really
+can't remember if Lima was stable enough for daily use but it looks really
 promising at least, because the whole graphical interface used it, and we saw
 no rendering artifacts while briefly testing it.
 
@@ -420,7 +420,7 @@ As we had an opportunity to talk with people from the GitLab team, weasked
 them whether they would be open to accept patches that fix this. They
 explained us that such would require to double the UI work for everything, but
 that it might be possible to do server side rendering with the same JavaScript
-that’s used on the client. The issue is that it cannot make requests from
+that's used on the client. The issue is that it cannot make requests from
 buttons like that, so in addition to the page rendering that could happen
 through server-side JavaScript, introspection could be used to rewrite the
 buttons.
@@ -439,7 +439,7 @@ was not the case in similar shops in a smaller city.
 This talk was held at the Hardware Enablement devroom.
 
 It quickly introduced Replicant and the smartphones ecosystem, and then
-proceed to look at what affects smartphones’ and tablets’ lifetime and how to
+proceed to look at what affects smartphones' and tablets' lifetime and how to
 increase it by making Replicant more sustainable.
 
 There was also a small, satirical play in the middle this talk. Its goal was
@@ -447,7 +447,7 @@ to show how the current market trends in smartphone design and construction
 severely impair those that look for privacy, software freedom, and reduction
 of electronic waste.
 
-Video and slides are available at the [talk’s page in FOSDEM’s website][20].
+Video and slides are available at the [talk's page in FOSDEM's website][20].
 
 ## Extra
 
@@ -464,7 +464,7 @@ from previous conferences that were (only) published on the mailing list:
 
 * [XDC 2019][23]
 
-There’s also a [wiki page that lists all talks about Replicant][24] that
+There's also a [wiki page that lists all talks about Replicant][24] that
 happened in several conferences throughout the years.
 
 * * *
diff --git a/markdown/2020_12_call-for-a-community-manager.md b/markdown/2020_12_call-for-a-community-manager.md
index c00fd29..aa640ab 100644
--- a/markdown/2020_12_call-for-a-community-manager.md
+++ b/markdown/2020_12_call-for-a-community-manager.md
@@ -7,7 +7,7 @@ authors: dllud
 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
+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  
@@ -25,7 +25,7 @@ The range of tasks will be very diverse. For instance:
 
 * Help users write proper bug reports.
 
-* Explain the design decisions that were taken during Replicant’s
+* Explain the design decisions that were taken during Replicant's
   development as well as the philosophical stand of the project.
 
 * Improve the wiki documentation, especially the end-user part.
@@ -86,7 +86,7 @@ require much less.
 
 ## How to apply
 
-If you want act as the Replicant project’s community manager please send your
+If you want act as the Replicant project's community manager please send your
 proposal to the public replicant@osuosl.org mailing list and tell us shortly
 (max ~300 words) why you would be the ideal fit for this role.
 
diff --git a/markdown/2021_05_presenting-replicants-community-manager.md b/markdown/2021_05_presenting-replicants-community-manager.md
index 1b6ebf1..e179af5 100644
--- a/markdown/2021_05_presenting-replicants-community-manager.md
+++ b/markdown/2021_05_presenting-replicants-community-manager.md
@@ -15,25 +15,25 @@ the interesting variety of valuable profiles we had the pleasure to evaluate.
 
 The key aspects that have been considered are, in no particular order:
 
-* the candidate having been actively participating in the community’s
+* the candidate having been actively participating in the community's
   activities and discussions, in the forum, the wiki, the mailing list and
   the official IRC channel, as well as in-person meetings
 
-* the candidate’s experience in installing Replicant and in solving problems
+* the candidate's experience in installing Replicant and in solving problems
   related to this activity
 
-* the candidate’s overall confidence with the practical aspects of using
+* the candidate's overall confidence with the practical aspects of using
   Replicant and helping users with related issues, doubts and information
   requests
 
-* the candidate’s involvement with other free-software projects similar to
+* the candidate's involvement with other free-software projects similar to
   Replicant and/or with interesting points of contact with the work being
   done in Replicant
 
-* the candidate’s ability to write useful and comprehensible periodical
-  reports to keep the community informed about the project’s activities
+* the candidate's ability to write useful and comprehensible periodical
+  reports to keep the community informed about the project's activities
 
-* the candidate’s ability to contribute to Replicant’s technical
+* the candidate's ability to contribute to Replicant's technical
   documentation
 
 * the differences with typical free software backgrounds (to be able to
@@ -53,7 +53,7 @@ or remotely, contributing his thoughts, impressions and valuable proposals.
 
 In the next few weeks, we will be coordinating with Kurtis and the FSF to work
 out the applicable funding conditions and to define the contract that will
-regulate the Community Manager’s duties.
+regulate the Community Manager's duties.
 
 Once again, we thank all applicants and the whole community in general.
 
diff --git a/markdown/2021_06_replicant-is-looking-for-volunteers-to-add-support-for-the-gsd4t-gps-chip.md b/markdown/2021_06_replicant-is-looking-for-volunteers-to-add-support-for-the-gsd4t-gps-chip.md
index 2ffa10c..cd89607 100644
--- a/markdown/2021_06_replicant-is-looking-for-volunteers-to-add-support-for-the-gsd4t-gps-chip.md
+++ b/markdown/2021_06_replicant-is-looking-for-volunteers-to-add-support-for-the-gsd4t-gps-chip.md
@@ -17,7 +17,7 @@ There is now some documentation of that protocol in the form of some [Perl
 source that can probably decode the protocol][1], and [there has also been
 some people doing research on it][2].
 
-In addition it’s also easier to do some tests on GNU/Linux: [there is now some
+In addition it's also easier to do some tests on GNU/Linux: [there is now some
 support in upstream Linux for the Galaxy SII (GT-I9100)][3] thanks to the
 postmarketOS contributor(s) who worked on that. [The nonfree bootloader of the
 Galaxy SII (GT-I9100) might requires some patches on top of that][4], but we
diff --git a/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md b/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md
index 037f234..5bc745f 100644
--- a/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md
+++ b/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md
@@ -9,15 +9,15 @@ Replicant 6.0 version 0003 or earlier you need to follow the data migration
 procedure that is documented in the [Release notes][1] page on the Replicant
 wiki.
 
-Even if we released the images back in January 2022, we didn’t announce it
-officially at the time because the data migration procedure wasn’t complete
+Even if we released the images back in January 2022, we didn't announce it
+officially at the time because the data migration procedure wasn't complete
 yet.
 
 ## What is new in this release
 
 Replicant is in the [list of distributions that are recommended by the
 FSF.][2] As such, Replicant needs to follow [strict criteria][3] that ensures
-that the distribution does its best not to violates its users’ freedom.
+that the distribution does its best not to violates its users' freedom.
 
 However fixing the issues and making new releases can sometime take a long
 time. The last Replicant 6.0 release was from December 2017.
@@ -28,13 +28,13 @@ This new release fixes some very serious freedom and privacy issues:
   numbers of both inbound and outbound calls to third parties as part of a
   feature called phone lookup providers. More details are available in the
   [bug report][4]. Even if it was not trivial to reproduce and find the bug
-  it’s now fixed as the feature has been completely disabled with 3 patches
+  it's now fixed as the feature has been completely disabled with 3 patches
   ([5], [6], [7]).
 
 * F-Droid has been removed as many applications shipped in it are not
   compliant with the [guidelines][3] for distributions recommended by the
   FSF. It was kept so long because we expected to get it fixed upstream fast
-  enough, but that didn’t happen for various reasons. We have setup a [wiki
+  enough, but that didn't happen for various reasons. We have setup a [wiki
   page][8] and a [forum section][9] for more information about the issue and
   how to deal with it.
 
@@ -61,27 +61,27 @@ This new release fixes some very serious freedom and privacy issues:
 
 This release may also fix [several bug(s) which made some SIM cards not
 recognizable by Replicant 6.0][19]: we have now merged a fix for one of the
-bug ([#1909][20]) but as we don’t know if all the “SIM card not recognized”
+bug ([#1909][20]) but as we don't know if all the “SIM card not recognized”
 bugs are related. We would highly appreciate if those that opened the original
 bug report could confirm if it also fixes their issues as well.
 
-Several issues still need to be fixed, but we didn’t want to delay even more
+Several issues still need to be fixed, but we didn't want to delay even more
 this release, as that would prevent users from getting the fixes mentioned
 above:
 
-* It’s still not possible to build Replicant 6.0 from a [distribution that
+* It's still not possible to build Replicant 6.0 from a [distribution that
   is recommended by the FSF][21] (bug [#1861][22]).
 
 * While removing the firmware of the Galaxy Note 8.0 touchscreen driver,
   many more firmwares without corresponding source code were found in the
   [driver/touchscreen directory][23] in the kernel used by most of the
-  devices supported by Replicant 6.0. However they weren’t removed yet. Help
+  devices supported by Replicant 6.0. However they weren't removed yet. Help
   is more than welcome to help with that.
 
 * While investigating if it was possible to upgrade WebView, the Android
   builtin web browser component (bug [#1786][24]) we also discovered that,
-  because Android build system doesn’t use a package manager, finding the
-  license of each repository wasn’t trivial (bug [#1973][25]).
+  because Android build system doesn't use a package manager, finding the
+  license of each repository wasn't trivial (bug [#1973][25]).
 
 * More investigations are needed as well to replace WebView with a free
   software and up to date implementation (bug [#1786][24]).
@@ -90,40 +90,40 @@ above:
   (bug [#1773][26]) is not fixed yet, but there is a workaround that works
   for some use cases.
 
-* The [Let’s Encrypt][27] certificates probably stopped working in Replicant
+* The [Let's Encrypt][27] certificates probably stopped working in Replicant
   6.0 the first September 2021. Some browsers like IceCat should normally
   continue to work fine. See the [Standing on Our Own Two Feet][28] blog
   post by letsencrypt for more details.
 
-As the internal WiFi doesn’t work with free software, some new network related
+As the internal WiFi doesn't work with free software, some new network related
 features improving usability were merged :
 
-* RepWiFi has been removed as it’s now possible to use the stock Android
+* RepWiFi has been removed as it's now possible to use the stock Android
   menus to handle the WiFi. This was done by patching Android to also accept
   external dongles. It is less reliable than with RepWiFi because in some
   cases reboots are needed for the WiFi to be recognized, and enabling the
   WiFi most probably also powers on the Internal WiFi chip as well,
   increasing the power consumption. However it should reduce the probability
-  of applications like F-Droid being broken in the future, as it’s better
+  of applications like F-Droid being broken in the future, as it's better
   integrated in Android. In the event that Replicant 6.0 stops being
-  maintained and that Replicant 11 doesn’t get support for all the Replicant
+  maintained and that Replicant 11 doesn't get support for all the Replicant
   6.0 devices, this patch should increase the lifetime of the affected
   devices.
 
-* Ethernet support has been added but it doesn’t work on all the devices.
+* Ethernet support has been added but it doesn't work on all the devices.
 
 * The USB networking scripts were also been added to the devices.
 
-* Support for some rt2500-usb dongles that don’t need the OS to load a
+* Support for some rt2500-usb dongles that don't need the OS to load a
   firmware [has been added to the Galaxy SIII 4G (i9305)][29], which is an
-  uncompleted device. It wasn’t added to the other devices to make the
+  uncompleted device. It wasn't added to the other devices to make the
   release happen a bit faster.
 
 Other improvements were also made:
 
 * llvmpipe is now the default OpenGL renderer. On devices with an Exynos CPU
   / [System on a chip][30], this allows running many applications that
-  weren’t working before. Unfortunately llvmpipe significantly slows down
+  weren't working before. Unfortunately llvmpipe significantly slows down
   some system components used in the graphical interface. This has been
   catered for by patching Android to use the old libagl renderer for those
   system components.
@@ -136,8 +136,8 @@ Other improvements were also made:
   implementation for the system components mentioned above, so there is
   little risk in trying the scripts.
 
-* It’s now easier to build Replicant as there is a new script that wraps
-  part of the building process. It’s also more convenient as it stores build
+* It's now easier to build Replicant as there is a new script that wraps
+  part of the building process. It's also more convenient as it stores build
   logs. The script has been used to build the release, and the build
   instructions also use it now.
 
@@ -148,7 +148,7 @@ Other improvements were also made:
 
 * [Instructions to backup the modem data partition][32] have been added. The
   modem partition can [become corrupted][33] in some conditions. As it can
-  be very difficult or impossible to recreate that partition, and that it’s
+  be very difficult or impossible to recreate that partition, and that it's
   required for the modem to work, we very strongly advise users to do a
   backup.
 
@@ -174,8 +174,8 @@ upstream Linux, it has some implications:
 * The Galaxy SIII 4G (I9305) and Galaxy Note II 4G (N7105) could also be
   added if work is done to add support for their modem in Replicant.
 
-* We don’t know yet how much work is needed to add support for the other
-  devices that are currently supported by Replicant 6.0, so we don’t know
+* We don't know yet how much work is needed to add support for the other
+  devices that are currently supported by Replicant 6.0, so we don't know
   yet if they will be compatible with Replicant 11 or not. We would need to
   find or get more information on the upstream status of theses devices
   before having a rough idea.
@@ -202,10 +202,10 @@ challenges:
   in Linux takes more time than adding devices in Replicant 6:
   * if we start adding support for a device, we want to be able to spend the time required to do it right and to work with upstream projects like Linux to add support for it in theses projects as well. The advantage is that it makes Replicant and the device being added more sustainable. However if the device has a battery that is not replaceable by experienced users, developers, repair shops, or [repair café][36], the device would have a very short lifetime which is incompatible with making Replicant sustainable.
   * Users would need to buy the device new in order to make sure that the battery lasts enough for a daily use. Buying the device second hand would be way more complicated as users would need to make sure that the battery last enough time. Developers would still be able to work on the device for a very long time, assuming that they are not users as well that want to use the device. But their work would not be very useful without usable devices.
-  * In addition, being able to remove the battery of a device increase trust: for devices with a single battery, it’s easy to understand that without a battery, the device is really off. For devices with an additional backup battery, some background information on chip energy consumption is enough to understand what the device cannot do with such backup battery.
+  * In addition, being able to remove the battery of a device increase trust: for devices with a single battery, it's easy to understand that without a battery, the device is really off. For devices with an additional backup battery, some background information on chip energy consumption is enough to understand what the device cannot do with such backup battery.
 
 As for non isolated modems, if Replicant only support devices with isolated
-modems, it’s way easier for users and developers to remember that the devices
+modems, it's way easier for users and developers to remember that the devices
 they are using have a somewhat isolated modem.
 
 However, as Replicant 11 is using a kernel closely based on upstream Linux,
@@ -224,7 +224,7 @@ up to the people that have such devices to test if the code is still working
 over time. The code quality of such contributions may also have to be high as
 we want to keep maintaining that code over time without having the devices.
 The Linux kernel is already using a similar approach to be able to maintain
-support a lot of devices (including devices that the maintainers don’t have)
+support a lot of devices (including devices that the maintainers don't have)
 without removing support for older devices.
 
 We could even provide access to the Replicant infrastructure (for instance by
@@ -236,13 +236,13 @@ need to:
   confuse both projects, else it defeats the point of having some
   separation).
 
-* Stay compatible with the [strict FSF criteria][3] as Replicant doesn’t
+* Stay compatible with the [strict FSF criteria][3] as Replicant doesn't
   want to host projects that are incompatible with such criteria. Though we
-  already collaborate with other projects (which we don’t host) that aren’t
+  already collaborate with other projects (which we don't host) that aren't
   compatible with such criteria.
 
 * Take care of users support (as Replicant developers will probably not have
-  these devices, so they won’t be able to test things to properly support
+  these devices, so they won't be able to test things to properly support
   users).
 
 * Take care of the releases (as Replicant developers will probably not have
diff --git a/markdown/2023_02_replicant-at-fosdem-2023.md b/markdown/2023_02_replicant-at-fosdem-2023.md
index 41eec58..7e4ede7 100644
--- a/markdown/2023_02_replicant-at-fosdem-2023.md
+++ b/markdown/2023_02_replicant-at-fosdem-2023.md
@@ -8,7 +8,7 @@ This year the [FOSDEM][1] will take place in Brussels the 4 and 5 February.
 
 This year there will be a talk about Guix evaluation and usage for/by the
 Replicant project: [How Replicant, a 100% free software Android distribution,
-uses (or doesn’t use) Guix][2], by the current Replicant maintainer.
+uses (or doesn't use) Guix][2], by the current Replicant maintainer.
 
 As not everybody is familiar with Replicant or free software on smartphones,
 it will also have some background information on hardware and software of
diff --git a/markdown/2023_12_replicant-37c3.md b/markdown/2023_12_replicant-37c3.md
index a4b09c8..8870b4c 100644
--- a/markdown/2023_12_replicant-37c3.md
+++ b/markdown/2023_12_replicant-37c3.md
@@ -8,7 +8,7 @@ Since yesterday, December 27th, the [37th Chaos Communication Congress
 (37C3)][1] is taking place in Hamburg. Replicant is present as part of the
 [Critical Decentralization Cluster (CDC)][2].
 
-[Replicant’s assembly][3] is the place to come by if need help installing
+[Replicant's assembly][3] is the place to come by if need 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.
author	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>	2024-03-18 02:40:29 +0100
committer	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>	2025-06-15 01:30:24 +0200
commit	659384dc54db02ccdce5648a9418283ee08fc216 (patch)
tree	79fd51124db101adb2f49f12f4ef55dea5f10e4b /markdown
parent	c577cf167d08c09e4d3409a4971a09cc13daa5b2 (diff)
download	haunt-blog-659384dc54db02ccdce5648a9418283ee08fc216.tar.gz haunt-blog-659384dc54db02ccdce5648a9418283ee08fc216.tar.bz2 haunt-blog-659384dc54db02ccdce5648a9418283ee08fc216.zip