Appease the linter

Author: alexp-sssup

content/blog/CJ-4-1.mdx

@@ -38,7 +38,7 @@ Around a month ago we announced [CheerpJ 4.0](https://labs.leaningtech.com/blog/
 
 The release of CheerpJ 4.0 was focused on getting the infrastructure right, maintaining our long standing Java 8 support while introducing Java 11, and allowing further versions of Java to be supported.
 
-As stated in our [roadmap](https://cheerpj.com/our-roadmap-for-modern-java-in-the-browser/), our plan was to introduce Java 17 support only later in the year. Thanks to faster than expected progress, we are now releasing this feature today, much earlier than we expected, as part of __CheerpJ 4.1__. This is intended to be a preview of the stable support that is still scheduled for a future CheerpJ 5.0 release, expected before the end of 2025.
+As stated in our [roadmap](https://cheerpj.com/our-roadmap-for-modern-java-in-the-browser/), our plan was to introduce Java 17 support only later in the year. Thanks to faster than expected progress, we are now releasing this feature today, much earlier than we expected, as part of **CheerpJ 4.1**. This is intended to be a preview of the stable support that is still scheduled for a future CheerpJ 5.0 release, expected before the end of 2025.
 
 Moreover, the initial support for Java 11 in the previous release received extensive testing by the developer community on a big variety of applications and libraries. Thanks to the help of our users, several critical bugs in the original release were found and fixed. This new 4.1 release also serves as an opportunity to bring much more stability to Java 11 support.
 
@@ -218,9 +218,9 @@ Development of CheerpJ is moving fast. The CheerpJ 5.0 release is still schedule
 
 There is a long list of improvements that we plan to ship, here are as few highlights:
 
-- __Stable Java 17 support__: With CheerpJ 4.1 we have released a preview of what Java 17 support will look like in the not so distant future, we plan to gather feedback from users to achieve a high level of stability by the time CheerpJ 5.0 is released.
-- __NPM support__: CheerpJ has been historically used primarily to run legacy Java applications, most usually in environments that pre-date the npm ecosystem. Now that CheerpJ can run modern Java we want to provide a npm-native CheerpJ version, to streamline integration into modern projects.
-- __Extend native JNI modules support__: This will allow us to support JavaFX, SWT and eventually allow users to build their own Wasm JNI module for any Java library.
+- **Stable Java 17 support**: With CheerpJ 4.1 we have released a preview of what Java 17 support will look like in the not so distant future, we plan to gather feedback from users to achieve a high level of stability by the time CheerpJ 5.0 is released.
+- **NPM support**: CheerpJ has been historically used primarily to run legacy Java applications, most usually in environments that pre-date the npm ecosystem. Now that CheerpJ can run modern Java we want to provide a npm-native CheerpJ version, to streamline integration into modern projects.
+- **Extend native JNI modules support**: This will allow us to support JavaFX, SWT and eventually allow users to build their own Wasm JNI module for any Java library.
 
 ## Licensing