diff --git a/Improve-Partner-Battle-Code.md b/Improve-Partner-Battle-Code.md
index 2197d55..50a22a0 100644
--- a/Improve-Partner-Battle-Code.md
+++ b/Improve-Partner-Battle-Code.md
@@ -122,6 +122,8 @@ In `src\battle_script_commands.c`, edit `Cmd_checkteamslost`:
 ```
 This change allows the battle to continue even if all of the player’s Pokémon faint, aligning with the mechanic introduced in the generation 4 games. After all, the partner NPC still has a chance to win the battle. The player will still need to press A whenever a Pokémon faints. Other than that, the battle will play out automatically.
 
-Be aware that if the partner wins and the player has no alive Pokémon in their party, the user will need to heal the player's party immediately afterwards (preferably via a `special`). If both the player and the partner's Pokémon faint, you might want to customize the whiteout string for extra clarity.
+Be aware that if the partner wins and the player has no alive Pokémon in their party, the user will need to heal the player's party immediately afterwards (preferably via a `special`). Not doing so would leave the player with a fully fainted party, which can cause all sorts of major bugs and glitches.
+
+If both the player and the partner's Pokémon faint, you might want to customize the ''out of usable Pokémon'' string for extra clarity. By default it'll say the player is out of usable Pokémon. While not exactly wrong, it's a bit odd to display this string directly after the _partner_ is out of Pokémon. Ideally, the message should say both the player and partner are out of Pokémon, followed by the typical player whiteout message.
 
 And that's it!
\ No newline at end of file