fix: prettier

docs/level-22.mdx

@@ -90,7 +90,7 @@ import ChopMoveIgnitionInteraction from "@site/image-generator/yml/level-22/chop
 - If a playable card is on chop, the natural thing to do is to give it a _Chop-Focus Play Clue_. If a player _Chop Moves_ the playable card instead, this is very strange. If there is not a good reason to do so, then the cluer is trying to communicate something extra.
 - In this situation, they intend for an _Ignition_ on the next player. Since a _Chop Move_ causes a blind-play, the _Chop Moved_ player will know that the _Chop Moved_ card is playable.
 - If multiple cards are _Chop Moved_, the (possible) target of a _Chop Move Ignition_ is the left-most, the same as the target would have been for a _Trash Pull_.
-- If a _Chop Move Ignition_ is successful, the clue receiver does *not* _Chop Move_ because 2 plays meets _Minimum Clue Value Principle_.
+- If a _Chop Move Ignition_ is successful, the clue receiver does _not_ _Chop Move_ because 2 plays meets _Minimum Clue Value Principle_.
 - For example, in a 4-player game:
   - It is the first turn and nothing is played on the stacks.
   - Cathy's hand is, from newest to oldest: blue 4, blue 4, blue 5, red 1