fix: broken link

hanabi · Feb 23, 2024 · 895435b · 895435b
1 parent 54b13db
commit 895435b
Show file tree

Hide file tree

Showing 3 changed files with 1,623 additions and 3,062 deletions.
diff --git a/cspell.jsonc b/cspell.jsonc
@@ -35,6 +35,7 @@
     "BCME",
     "blueviolet",
     "cathys",
+    "clsx",
     "cluable",
     "cluer",
     "cocktailgames",

diff --git a/docs/extras/ejections.mdx b/docs/extras/ejections.mdx
@@ -57,7 +57,7 @@ import RankChoice from "@site/image-generator/yml/extras/ejections/rank-choice.y
 
 ### The Trash Finesse Push Ejection / The Trash Bluff Push Ejection
 
-- First, see the sections on the _[Trash Push Ejection](#trash-push-ejection)_ and on the _[Bad Trash Finesse Ejection](#the-bad-trash-finesse-ejection-the-bad-trash-bluff-ejection)_.
+- First, see the sections on the _[Trash Push Ejection](#trash-push-ejection)_ and on the _[Bad Trash Finesse Ejection](#the-bad-trash-finesse-ejection--the-bad-trash-bluff-ejection)_.
 - If a player performs a _Trash Finesse_ by touching a chop card, this will always result in a _Trash Push_ (since _[Trash Finesses and Trash Bluffs are always unnecessary](../level-25.mdx#trash-finesses-and-trash-bluffs-are-always-unnecessary)_.
 - What if a _Trash Finesse_ is given, but the responding player sees that the resulting pushed card could never be playable by the time it gets to their turn? In other words, what if the pushed card is two-or-more-away-from-playable?
 - In this situation, we agree that the reacting player needs to _Eject_ (instead of playing _First Finesse Position_ like they would in a normal _Trash Finesse_).