1 files changed, 8 insertions, 8 deletions

diff --git a/search/readme.md b/search/readme.md
index 400c8ce..164dc9f 100644
--- a/search/readme.md
+++ b/search/readme.md
@@ -23,11 +23,11 @@ to Yomikun's tags for compatibility. Other tags include:
 
 ### Behavior-altering tags
 
-Some tag classes impact the parser's behavior. For example, the input text
+A word's class can impact the parser's behavior. For example, the input text
 「完了しました」 will be parsed as just 「完了」, but with the
-`class:verb:suru-included` tag added by the parser. This is because the word
+inflection `infl:suru` tag added by the parser. This is because the word
 「完了」 has the tag `class:verb:suru` in the database, which allows the parser
-to deconjugate a noun with the verb 「する」 back into the stem.
+to deconjugate a noun with the verb 「する」 attached back into the stem.
 
 Other uses of this behavior include more accurate automatic kanji reading
 generation, for example 「城」 being read as 「じょう」 in 「ハイラル城」
@@ -35,11 +35,11 @@ because 「ハイラル」 has the tag `name:place` in the database, and
 「城(じょう)」 has `class:suffix`, while 「城(しろ)」 has `class:noun`.
 
 Yomikun encourages homebrew dictionary sharing, and encourages using
-behavior-altering tags for fixing readings for cases like the above examples.
-As another example of this, it is encouraged that a dictionary for (for
-example) Zelda add 「トト」 as a term with tags `class:noun` and `name:place`,
-instead of 「トト湖(こ)」 as an expression to fix the reading of the kanji
-「湖(みずうみ)」.
+behavior-altering tags instead of expressions for fixing readings for cases
+like the above examples. As another example of this, it is encouraged that a
+dictionary for (for example) Zelda add 「トト」 as a term with tags
+`class:noun` and `name:place`, instead of 「トト湖(こ)」 as an expression to
+fix the reading of the kanji 「湖(みずうみ)」.
 
 If Yomikun doesn't generate the correct reading, and the reading isn't based on
 natural language context (=a computer *could* accurately decide which reading