diff --git a/Iranian APT/Charming Kitten/README.md b/Iranian APT/Charming Kitten/README.md
index 2fc09d6..a7f3dcf 100644
--- a/Iranian APT/Charming Kitten/README.md	
+++ b/Iranian APT/Charming Kitten/README.md	
@@ -104,14 +104,14 @@ This enhancement demonstrates an alternative command and control architecture th
 
 To simulate the communication workflow observed during the analysis, I created a dedicated Telegram bot using **BotFather**, Telegram's official bot management service. Unlike traditional command and control infrastructures that depend on dedicated servers, fixed IP addresses, or custom domains, this simulation communicates exclusively through the Telegram Bot API over encrypted HTTPS connections.
 
-Following the same communication model, I configured the bot with the **Display Name** `Olalampo` and the **Username** `stager_51_bot`. The bot token generated by BotFather serves as the authentication mechanism, allowing BEAR C2 to establish communication with the Telegram Bot API without requiring a dedicated C2 server. This approach demonstrates how cloud messaging platforms can be incorporated into adversary simulations to emulate alternative command and control architectures.
+Following the same communication model, I configured the bot with the **Display Name** `Olalampo` and the **Username** `stager_51_bot`. The bot token generated by BotFather serves as the authentication mechanism, allowing BEAR-C2 to establish communication with the Telegram Bot API without requiring a dedicated C2 server. This approach demonstrates how cloud messaging platforms can be incorporated into adversary simulations to emulate alternative command and control architectures.
 
 <img width="2423" height="1920" alt="image_(1)" src="https://github.com/user-attachments/assets/96e06e84-3208-4b2c-935a-b48ca7dd0620" />
 
 
 `Telegram API Setup`
 
-To enable BEAR C2 to communicate with the Telegram account controlling the bot, I generated a Telegram **API ID** and **API Hash** through Telegram's developer portal. After registering a new application, these credentials were configured inside BEAR C2, allowing the framework to authenticate and interact with the Telegram account used throughout the simulation.
+To enable BEAR-C2 to communicate with the Telegram account controlling the bot, I generated a Telegram **API ID** and **API Hash** through Telegram's developer portal. After registering a new application, these credentials were configured inside BEAR-C2, allowing the framework to authenticate and interact with the Telegram account used throughout the simulation.
 
 
 `CHAR.cpp Configuration`