Update documentation for clarity and consistency

Remove emojis and em dash separators
Simplify introductory sentences
Standardize section headings

content/documentation/securité/cadenas_vert/ssl.en.md

@@ -6,7 +6,7 @@ cascade:
   type: docs
 ---
 
-## Introduction: The Padlock, Your Trust Indicator 🕵️‍♂️✨
+## Introduction: the padlock, your trust indicator
 
 You've seen it thousands of times, haven't you? That little **green padlock** (or sometimes gray, depending on your browser and the site) that shows up next to a website's address in your navigation bar. You click on it, you look at it, you think "cool, it's secure," and you move on.
 
@@ -15,15 +15,15 @@ You've seen it thousands of times, haven't you? That little **green padlock** (o
 But... do you really know what it means? 🤔 All the **mechanics that kick in** just so this little symbol appears? It's much more than a simple icon! It's the visible part of an iceberg. \
 **So, what's our mission today? 🚀**
 
-We're going to roll up our sleeves and analyze what happens "under the hood"! Promise: we'll explain **clearly, simply, and without indigestible jargon** what actually happens when this padlock appears. We'll dissect together how it helps us know whether we can trust a site and why it's absolutely **ESSENTIAL** for our "security".
+We're going to roll up our sleeves and analyze what happens "under the hood"! Promise: we'll explain **clearly, simply, and without indigestible jargon** what actually happens when this padlock appears. We'll dissect together how it helps us know whether we can trust a site and why it matters for our "security".
 
 Get ready, because you'll see that behind this little padlock hides a complex dance of certificates, secret keys, and handshakes... And by the end, you'll never look at this little symbol the same way again.
 
-## Part 1: The SSL Certificate 💳
+## Part 1: the SSL certificate
 
 So, this famous SSL certificate, what exactly is it? Hang on tight, because it's the first piece of the puzzle!
 
-### What is it? 🤔
+### What is it?
 
 Imagine the SSL certificate (or TLS, we'll get to that!) as the **official digital ID card of a website**. When you present it to the police 👮, it proves who you are. \
 Well, for a website, it's the same thing!
@@ -37,7 +37,7 @@ It's the first guarantee that you're not being fooled by a well-disguised phishi
 > But since "SSL" remained popular (a bit like calling any tissue a "Kleenex"), it's still widely used. \
 > In this article, we'll juggle between "SSL certificate" and "TLS certificate", but know that we're really talking about the modern, secure technology!
 
-### Who Issues It? The Certificate Authority (CA) 🏛️
+### Who issues it? The certificate authority (CA)
 
 But who makes and distributes these ID cards? These are the **Certificate Authorities (CA)**. \
 Think of them as **"town halls"**.
@@ -54,17 +54,17 @@ And how does your browser (Chrome, Firefox, Safari...) know it can trust a CA? I
 > * **EV (Extended Validation):** The top of the top in verification! The CA conducts a thorough investigation into the company's identity. In the past, this often resulted in the company name being displayed in green next to the padlock. Today, browsers tend to simplify this display, but the rigor of the verification remains.
 > The little padlock will be there for all these types, but additional information about the organization may be visible by clicking on it for OV/EV certificates.
 
-### What Does It Contain? 📜
+### What does it contain?
 
 Concretely, what do we find in this famous digital ID card? The essential information is:
 
-* **The domain name concerned:** For example, `notebook.arnodo.fr`. This is crucial to make sure you're in the right place.
+* **The domain name concerned:** For example, `notebook.arnodo.fr`. This confirms you're in the right place.
 * **The name of the owning organization:** Especially visible and verified for OV and EV certificates. This gives you an idea of who's behind the site.
 * **The server's public key:** 🔑 This is an ultra-important piece of code! We'll see its role in Part 2, but remember it's here, snugly stored in the certificate. It's a bit like the address of our mailbox.
 * **The CA's digital signature:** This is the official stamp of the "town hall" (the CA) that proves the certificate is authentic and hasn't been modified or forged since it was issued.
 * **The validity dates:** Like your driver's license or your passport, a certificate has a start date and an end date. An expired certificate is a big NO 🚩 for your browser!
 
-### How Does Your Browser Verify It? ⏱️💨
+### How does your browser verify it?
 
 All that's great, but how does your browser manage to verify all this in the blink of an eye (often in just a few milliseconds!) when you land on a site? It's a well-oiled little dance, a sort of express "check-up":
 
@@ -73,7 +73,7 @@ All that's great, but how does your browser manage to verify all this in the bli
 3. **Not on the blacklist (revocation):** The browser makes sure the certificate hasn't been revoked. "Revoked?" Yes, that means canceled before its expiration date. This can happen if, for example, the site got hacked and its private key (the server's secret, more on that soon) was compromised. The CA then publishes lists of canceled certificates (called CRL or via OCSP) that browsers consult.
 4. **Right site, right certificate:** It checks that the domain name indicated in the certificate (for example `www.yourfavoritesite.com`) matches EXACTLY the site you're trying to reach. No cheating or identity fraud!
 
-🏁 **The Verdict:**
+**The verdict:**
 
 * **If everything's OK 👍:** The little green padlock (or gray, depending on the browser) proudly displays itself! The connection is deemed safe, and you can browse, buy, or enter your information with a (relatively) peaceful mind.
 * **If something's off 👎:** Your browser will sound the alarm! 🚨 You'll see a very visible warning message (something like "Your connection is not private", "Security alert", etc.).
@@ -83,13 +83,13 @@ All that's great, but how does your browser manage to verify all this in the bli
 
 And that's it for the ID card! But this is only the beginning. Now that we know the site really is what it claims to be, how do we make sure our exchanges with it stay secret? That's where the magic of keys comes in... and that's the topic of our next part!
 
-## Part 2: The Dance of the Keys 💃🔑
+## Part 2: the dance of the keys
 
 Alright, now we know the site really is what it claims to be thanks to its ID card (the SSL/TLS certificate, remember?). That's great, but it's not enough! If our exchanges with this site travel in plain text over the internet, any nosy person (or hacker 🏴‍☠️) could read them. Not great if you're sending your credit card number or your most secret passwords!
 
 That's where the second phase of the magic kicks in: **data encryption**. And for that, we're going to witness a real "dance of the keys"!
 
-### Introduction to the Magic: Asymmetric Cryptography
+### Introduction to the magic: asymmetric cryptography
 
 For our data to become illegible gibberish to others, we use a brilliant concept called **asymmetric cryptography**. What's that? It's the idea of having not one, but **two digital keys** that work together, like an inseparable duo:
 
@@ -98,7 +98,7 @@ For our data to become illegible gibberish to others, we use a brilliant concept
 
 In short: what's encrypted (locked) with the public key can ONLY be decrypted (unlocked) by the corresponding private key. And vice versa (although for our "handshake", it's mostly the first direction that interests us). Clever, isn't it?
 
-### The Simplified SSL/TLS "Handshake"
+### The simplified SSL/TLS "handshake"
 
 Now that we have our keys, how do your browser and the server agree to talk secretly? Thanks to an initial negotiation, a sort of coded "handshake" called the **SSL/TLS Handshake**. Here are the steps, simplified so as not to give you a headache:
 
@@ -117,12 +117,12 @@ From this moment on, **all the data exchanged** between your browser and the ser
 
 The communication is now secure, encrypted end-to-end! 🔒 You can relax, your secrets are (normally) well kept!
 
-## Part 3: Why Is All This Essential For You? 🛡️🌍
+## Part 3: why does this matter to you?
 
 OK, we've seen the site's ID card (the certificate) and the secret dance of keys to encrypt our conversations (the SSL/TLS handshake). \
 But concretely, why go through all this trouble?
 
-### For You, as a User
+### For you, as a user
 
 When you browse a site proudly displaying this padlock (and thus using HTTPS), you benefit from several vital protections:
 
@@ -139,29 +139,29 @@ When you browse a site proudly displaying this padlock (and thus using HTTPS), y
 3. **Authentication 🆔: You're Really Talking to the Right Counter!**
     Thanks to the SSL/TLS certificate, you have much better assurance that you're communicating **with the legitimate site and not with a fraudulent clone**.
 
-### For Website Owners 👑
+### For website owners
 
 If you have a website, setting up HTTPS is no longer a "nice-to-have", it has become a "must-have". Here's why:
 
-1. **Building Trust (and Increasing Conversions!) 😊➡️💰**
-    The padlock immediately reassures your visitors. They see that you take their security seriously. This is absolutely crucial for e-commerce (who would want to enter their bank details on an unsecured site?), online banking services, or any site collecting the slightest bit of personal data. An unsecured site can scare visitors away before they've even explored your content, directly impacting your credibility and, potentially, your sales or your goals.
+1. **Building trust (and increasing conversions)**
+    The padlock immediately reassures your visitors. They see that you take their security seriously. This matters a lot for e-commerce (who would want to enter their bank details on an unsecured site?), online banking services, or any site collecting the slightest bit of personal data. An unsecured site can scare visitors away before they've even explored your content, directly impacting your credibility and, potentially, your sales or your goals.
 
-2. **Improving Search Engine Optimization (SEO) 📈: Google Loves Secure Sites!**
+2. **Improving search engine optimization (SEO): Google loves secure sites**
     For several years now, Google and other search engines have **actively favored HTTPS sites** in their search results. Switching your site to HTTPS can therefore give you a little boost in the rankings. Conversely, not doing so could penalize you.
 
-3. **Protecting Your Users (and Your Reputation!) 🛡️**
+3. **Protecting your users (and your reputation)**
     By securing exchanges, you protect your users against the theft of their personal data. Avoiding a data leak or identity theft that would originate from a security flaw on your site also means protecting your own reputation. Bad press on this subject can be devastating.
 
-4. **Regulatory Compliance ⚖️: Sometimes, It's the Law!**
+4. **Regulatory compliance: sometimes, it's the law**
     For certain activities and in certain regions (think GDPR in Europe, for example), securing the personal data collected and processed is a **legal obligation**. Failing to comply can result in heavy penalties. HTTPS is one of the fundamental building blocks of this compliance.
 
-In short, this little padlock is a sign of respect toward your users, a mark of seriousness for your business, and a protection for everyone. Not bad for such a small icon, right? 😉
+This little padlock is a sign of respect toward your users and a mark of seriousness for your business. Not bad for such a small icon, right?
 
-## Conclusion 🛡️✨
+## Conclusion
 
 So, this little green (or gray) padlock we've dissected from every angle, it's ultimately much more than a simple graphic detail, isn't it? As we've seen, it's the **visible part of an ingenious and complex system** working hard behind the scenes.
 
-To sum up our journey in a few words:
+Quick recap:
 
 * It starts with a **digital ID card** (the SSL/TLS certificate) that assures us the site really is what it claims to be, issued by a trusted "web town hall" (the Certificate Authority).
 * Then, there's a **cryptographic "dance of the keys"** (the public key to encrypt a secret, the private key to decrypt it) that allows your browser and the server to agree on a unique secret code (the session key).
@@ -181,7 +181,7 @@ In short, this padlock is the most visible manifestation of this **personal digi
 
 Get into the habit of **always checking for the presence of this padlock** (and hence "HTTPS" in the address) before entering any sensitive information or downloading anything on a website. Don't hesitate to **click on it for more information** if you have any doubt. And above all, be **extremely vigilant about security warning messages** that your browser might display. They're there for a good reason!
 
-> [!NOTE]Key and Certificate File Formats
+> [!NOTE] Key and certificate file formats
 >
 > You'll often encounter different file formats for keys and certificates. Here are the most common ones:
 >