Apply requested changes. Remove Emojis from headers.

Author: eliaoggian

docs/services/kubernetes/kubernetes-upgrades.md

@@ -3,7 +3,7 @@
 
 To maintain a secure, stable, and supported platform, we regularly upgrade our Kubernetes clusters. We use **[RKE2](https://docs.rke2.io/)** as our Kubernetes distribution.
 
-## 🔄 Upgrade Flow
+## Upgrade Flow
 
 **Phased Rollout**
 
@@ -16,7 +16,7 @@ To maintain a secure, stable, and supported platform, we regularly upgrade our K
   - Timing may depend on compatibility with **other infrastructure components** (e.g., storage, CNI plugins, monitoring tools).
   - However, all clusters will be upgraded **before the current Kubernetes version reaches End of Life (EOL)**.
 
-## ⚠️ Upgrade Impact
+## Upgrade Impact
 
 The **impact of a Kubernetes upgrade can vary**, depending on the nature of the changes involved:
 
@@ -32,7 +32,7 @@ The **impact of a Kubernetes upgrade can vary**, depending on the nature of the
 
 ??? Note "Applications that follow cloud-native best practices (e.g., readiness probes, multiple replicas, graceful shutdown handling) are **less likely to be impacted** by upgrades."
 
-## ✅ What You Can Expect
+## What You Can Expect
 
 - Upgrades are performed using safe, tested procedures with minimal risk to production workloads.
 - TDS clusters serve as a **canary environment**, allowing us to identify issues early.

docs/services/kubernetes/node-updates.md

@@ -3,7 +3,7 @@
 
 To ensure the **security** and **stability** of our infrastructure, CSCS will perform **monthly OS updates** on all nodes of our Kubernetes clusters.
 
-## 🔄 Maintenance Schedule
+## Maintenance Schedule
 
 - **Frequency**: Every **first week of the month**  
 - **Reboot Window**: **Monday to Friday**, between **09:00 and 15:00**  
@@ -13,15 +13,15 @@ These updates include important security patches and system updates for the oper
 
 ??? Note "Nodes will be rebooted only if required by the updates."
 
-## 🚨 Urgent Security Patches
+## Urgent Security Patches
 
 In the event of a **critical zero-day vulnerability**, we will apply patches and perform reboots (if required) **as soon as possible**, outside of the regular update schedule if needed.  
 
 - Affected nodes will be updated **immediately** to protect the platform.
 - Users will be notified ahead of time **when possible**.
 - Standard safety and rolling reboot practices will still be followed.
 
-## 🛠️ Reboot Management with Kured
+## Reboot Management with Kured
 
 We use [**Kured** (KUbernetes REboot Daemon)](https://github.com/kubereboot/kured) to safely automate the reboot process. Kured ensures that:
 
@@ -30,7 +30,7 @@ We use [**Kured** (KUbernetes REboot Daemon)](https://github.com/kubereboot/kure
 - Reboots occur **only during the defined window** 
 - Nodes are **cordoned**, **drained**, and **gracefully reintegrated** after reboot.
 
-## ✅ Application Requirements
+## Application Requirements
 
 To avoid service disruption during node maintenance, applications **must be designed for high availability**. Specifically: