Update special-finesses.mdx

docs/extras/special-finesses.mdx

@@ -224,11 +224,12 @@ import InvertedPriorityFinesse from "./special-finesses/inverted-priority-finess
 - In this situation, the player must be trying to communicate something extra. Similar to an _Occupied Finesse_, the player is trying to signal that this seemingly innocent _Save Clue_ is actually a _Play Clue_ instead. Someone on the team must have the cards to make this critical card playable.
 - In some situations, the blind-player may have to defer playing into the _Finesse_ and instead give a _5 Save_ to the player with the (now) unsafe chop. If they do, then this is not a problem - the clue receiver can retroactively determine that a _Declined 5's Finesse_ has occurred and should not _stomp_ on the _Finesse_.
 
-### The Rank Choice Save Finesse
+### The Rank Choice Save Finesse / The Rank Choice Save Bluff
 
 - When saving a card, players have to choose carefully between using a color clue or a rank clue. However, in some rare situations, it makes absolutely no difference which clue is used:
   - Both color and rank would only touch the specific card.
   - Both color and rank would communicate the exact identity of the specific card.
   - Both color and rank would not give any useful negative information to the other cards in the hand.
 - In these situations, the player giving the clue has a completely free choice between rank and color. We agree that by default, players should use color to save the card.
 - If players instead use a rank clue to save the card, this communicates a _Rank Choice Save Finesse_.
+- In the same way, it is also possible to perform a _Rank Choice Save Bluff_.