Formatting

1 files changed, 10 insertions, 10 deletions

diff --git a/Correct-grammar-for-plural-trainers-like-Twins.md b/Correct-grammar-for-plural-trainers-like-Twins.md
index 2fd15f6..50c93f7 100644
--- a/Correct-grammar-for-plural-trainers-like-Twins.md
+++ b/Correct-grammar-for-plural-trainers-like-Twins.md
@@ -1,17 +1,17 @@
-Battles begin with the phrase "*<ENEMY>* wants to battle!" and end with "*<ENEMY>* was defeated!" This makes sense if "*<ENEMY>*" is something like "YOUNGSTER JOEY", but it's ungrammatical for plural trainers like "TWINS AMY & MAY".
+Battles begin with the phrase "*ENEMY* wants to battle!" and end with "*ENEMY* was defeated!" This makes sense if "*ENEMY*" is something like "YOUNGSTER JOEY", but it's ungrammatical for plural trainers like "TWINS AMY & MAY".
 
-Gen 3 addressed this issue by changing the phrases to "*<ENEMY>* would like to battle!" and "Player defeated *<ENEMY>*!" And then Gen 4 changed the starting phrase to "You are challenged by *<ENEMY>*!" But some people don't like the politeness of Gen 3, or the passive voice of Gen 4. (\*ahem\*) Plus they're both more verbose than the original Gen 2 phrases, which really matters when the textboxes are so small, and the "*<ENEMY>*" name can take up an entire line (like "MYSTICALMAN EUSINE").
+Gen 3 addressed this issue by changing the phrases to "*ENEMY* would like to battle!" and "Player defeated *ENEMY*!" And then Gen 4 changed the starting phrase to "You are challenged by *ENEMY*!" But some people don't like the politeness of Gen 3, or the passive voice of Gen 4. (\*ahem\*) Plus they're both more verbose than the original Gen 2 phrases, which really matters when the textboxes are so small, and the "*ENEMY*" name can take up an entire line (like "MYSTICALMAN EUSINE").
 
-The alternative is to use the correct grammar for plural trainers: "*<ENEMY>* **want** to battle!" and "*<ENEMY>* **were** defeated!" This is fairly simple to implement. If you've worked with event scripts before but not assembly code, this is a good feature to start with.
+The alternative is to use the correct grammar for plural trainers: "*ENEMY* **want** to battle!" and "*ENEMY* **were** defeated!" This is fairly simple to implement. If you've worked with event scripts before but not assembly code, this is a good feature to start with.
 
 
 ## Contents
 
 1. [Define alternative plural phrases](#1-define-alternative-plural-phrases)
 2. [Define plural trainers](#2-define-plural-trainers)
-3. [Use "<ENEMY> want to battle!"](#3-use-enemy-want-to-battle)
-4. [Use "<ENEMY> were defeated!"](#4-use-enemy-were-defeated)
-5. [Use "<ENEMY> are about to use…"](#5-use-enemy-are-about-to-use)
+3. [Use "*ENEMY* want to battle!"](#3-use-enemy-want-to-battle)
+4. [Use "*ENEMY* were defeated!"](#4-use-enemy-were-defeated)
+5. [Use "*ENEMY* are about to use…"](#5-use-enemy-are-about-to-use)
 
 
 ## 1. Define alternative plural phrases
@@ -66,7 +66,7 @@ Edit [data/text/battle.asm](../blob/master/data/text/battle.asm):
 +	done
 ```
 
-(Yes, while looking through the file I found a third phrase using "<ENEMY>" that needed a different plural form. All the rest are okay as-is.)
+(Yes, while looking through the file I found a third phrase using "`<ENEMY>`" that needed a different plural form. All the rest are okay as-is.)
 
 
 ## 2. Define plural trainers
@@ -117,7 +117,7 @@ We're not using the more complicated `IsGymLeaderCommon` method, which calls `Is
 Now we just have to find where those three original phrases are used, and call `IsPluralTrainer` to decide whether to use the new phrases instead.
 
 
-## 3. Use "&lt;ENEMY&gt; want to battle!"
+## 3. Use "*ENEMY* want to battle!"
 
 Edit [engine/battle/core.asm](../blob/master/engine/battle/core.asm) again:
 
@@ -133,7 +133,7 @@ Edit [engine/battle/core.asm](../blob/master/engine/battle/core.asm) again:
 ```
 
 
-## 4. Use "&lt;ENEMY&gt; were defeated!"
+## 4. Use "*ENEMY* were defeated!"
 
 Edit [engine/battle/core.asm](../blob/master/engine/battle/core.asm) again:
 
@@ -149,7 +149,7 @@ Edit [engine/battle/core.asm](../blob/master/engine/battle/core.asm) again:
 ```
 
 
-## 5. Use "&lt;ENEMY&gt; are about to use…"
+## 5. Use "*ENEMY* are about to use…"
 
 Edit [engine/battle/core.asm](../blob/master/engine/battle/core.asm) again: