diff --git a/A-chat-about-saving-data.md b/A-chat-about-saving-data.md
index 829b932..b31d2c6 100644
--- a/A-chat-about-saving-data.md
+++ b/A-chat-about-saving-data.md
@@ -1,7 +1,7 @@
-# **How to Save Data at SwissFEL: A Totally Serious Guide**  
+# **How to Save Data at SwissFEL: A totally serious guide**  
 
 **Hey, look at my nice data!**  
-*What a load of BS!*  
+*What a load of bs!*  
 
 **Oy, no need to be rude!**  
 *I’m not! I mean, what a load of **Beam Synchronous** data!*  
@@ -12,14 +12,14 @@
 **I used this cool command-line script `bs...`**  
 *Ooooh... I’m going to stop you right there.*  
 
-**But my BS command works; there must be a problem with the sources!**  
+**But my bs command works; there must be a problem with the sources!**  
 *Calm down, detective, try saving each source individually with the `bs` command...*  
 
 **OK, hang on... what the?! They *both* save fine on their own!**  
 *Yep, the issue is when you try and save sources from different IOCs/devices with the `bs` command. The data is taken from the **dispatcher**. If the two sources don’t arrive at the dispatcher within a small time window, only the first source is sent in the message. Different sources arrive at the dispatcher at **different times**.*  
 
 **What type of BS is that?! I can't wait and wait...**  
-*Good question. Some BS data comes from **pipelines**, where calculations and moving data around **takes time**. You’re not just saving numbers—you’re saving processed results.*  
+*Good question. Some bs data comes from **pipelines**, where calculations and moving data around **takes time**. You’re not just saving numbers—you’re saving processed results.*  
 
 **Pipelines?! I want data, not plumbing problems!**  
 *Think of pipelines as hardworking elves doing data analysis behind the scenes. No pipelines, more work for you.*  
@@ -48,5 +48,4 @@
 *Pulse IDs rock my world!*
 
 **❌ Don’t Say:** 
-*Beam synchronous PV*  
-
+*Beam synchronous PV*  
\ No newline at end of file