fix: links

misc/2-player.md

@@ -73,7 +73,7 @@
 
 ### The Delayed Bluff
 
-- In non-2-player games, _Delayed Bluffs_ are explicitly illegal, since they violate _[Lie Principle](https://hanabi.github.io/docs/level-11/#lie-principle)_. However, in 2-player games, they are allowed.
+- In non-2-player games, _Delayed Bluffs_ are explicitly illegal, since they violate _[Lie Principle](https://hanabi.github.io/level-11#lie-principle)_. However, in 2-player games, they are allowed.
 - Note that this convention also applies to _Double Bluffs_. For example, if cluing a 4 at the beginning of the game causes two 1's to blind-play, then the blind-playing player is not promised to have any more playable cards.
 
 ### Scream Discard Modification

misc/BGA.md

@@ -286,4 +286,4 @@ These are conventions that we don't typically turn on for new players, but we do
 
 Reading the stuff on this page will give you the major tools that you will need to play with our group. You can and should stop reading now and play some games with us! There's certainly some other minor things to learn, but you will quickly learn the rest from direct experience and post-game reviews.
 
-Know that you certainly **do not** have to read and memorize [all of our conventions](https://hanabi.github.io/docs/reference/) before playing with us! This is a common misconception that new players have. The website is meant to be used as a reference, and not meant to be read from start to finish.
+Know that you certainly **do not** have to read and memorize [all of our conventions](https://hanabi.github.io/reference) before playing with us! This is a common misconception that new players have. The website is meant to be used as a reference, and not meant to be read from start to finish.

misc/FAQ.md

@@ -158,11 +158,11 @@ Left-most.
 
 ## Should I always _Chop Move_ after receiving a _Tempo Clue_?
 
-No! There are **four** conditions where _Tempo Clues_ are allowed. If [any of these four conditions](https://hanabi.github.io/docs/level-6#the-valuable-tempo-clue) are true, then you should not _Chop Move_.
+No! There are **four** conditions where _Tempo Clues_ are allowed. If [any of these four conditions](https://hanabi.github.io/level-6#the-valuable-tempo-clue) are true, then you should not _Chop Move_.
 
 <br />
 
-## Does _[Schrodinger's Cat Principle](https://hanabi.github.io/docs/level-5/#schr%C3%B6dingers-cat-principle)_ always take priority over _[Occam's Razor](https://hanabi.github.io/docs/level-10/#clue-interpretation--occams-razor)_?
+## Does _[Schrodinger's Cat Principle](https://hanabi.github.io/level-5#schr%C3%B6dingers-cat-principle)_ always take priority over _[Occam's Razor](https://hanabi.github.io/level-10#clue-interpretation--occams-razor)_?
 
 Yes.
 

misc/convention-changes.md

@@ -76,7 +76,7 @@
 
 ## Are there any probationary conventions?
 
-- By default, players generally use the conventions that are specified in the main [website](https://hanabi.github.io/docs/reference/).
+- By default, players generally use the conventions that are specified in the main [website](https://hanabi.github.io/reference).
 - Conventions listed in the [GitHub issues tracker](https://github.com/hanabi/hanabi.github.io/issues) are considered probationary. Players can agree to play with one or more probationary conventions before the game begins, if they want to try something out.
 - When the issue for a proposed convention is closed, it will be integrated into the main website. At that time, it is no longer considered to be probationary.
 

misc/convention-questions.md

@@ -36,7 +36,7 @@ Use notation that the H-Group will be familiar with:
 - For example, the following question will be deleted:
   - /replay 12345 12<br />Level 11 game. Is this a 5 Stall or a 5 Pull?
 - For example, the following question is good:
-  - /replay 12345 12<br />Level 11 game. Here, it is Alice's turn. It is also the Early Game and no 5 Stalls have been given yet. Thus, based on my understanding of the conventions, when Alice clues number 5 to Bob, it would just be a 5 Stall, because there is no other possible clues that Alice can give. Is this correct? (From: https://hanabi.github.io/docs/level-6/#5-stalls-intermediate-section)
+  - /replay 12345 12<br />Level 11 game. Here, it is Alice's turn. It is also the Early Game and no 5 Stalls have been given yet. Thus, based on my understanding of the conventions, when Alice clues number 5 to Bob, it would just be a 5 Stall, because there is no other possible clues that Alice can give. Is this correct? (From: https://hanabi.github.io/level-6#5-stalls-intermediate-section)
 
 ### 5) Put Everything in One Message
 

misc/convention-reasons.md

@@ -6,7 +6,7 @@ The main website lists all of our conventions. But it does not bother listing **
 
 ## Chop-Focus
 
-- In the H-Group convention framework, we play with _[Chop-Focus](https://hanabi.github.io/docs/beginner/single-card-focus/)_, which allows us to "get" playable cards that are on chop. Nearly all other Hanabi groups play with a simpler system (e.g. _Play Clues_ are always focused on the left-most card). Why do we have _Chop-Focus_?
+- In the H-Group convention framework, we play with _[Chop-Focus](https://hanabi.github.io/beginner/single-card-focus)_, which allows us to "get" playable cards that are on chop. Nearly all other Hanabi groups play with a simpler system (e.g. _Play Clues_ are always focused on the left-most card). Why do we have _Chop-Focus_?
 - Most Hanabi groups independently come up with the _Finesse_ and the _Bluff_; they are considered to be the two core tools that allow players to be highly-efficient. In the H-Group, we use these tools as building blocks to compose even more advanced moves, such as the _Layered Finesse_ and the _3 Bluff_. These advanced _Finesses_ and _Bluffs_ allow us to get even more efficient.
 - Separately, notice that the strength of the "play the left-most" convention is that it allows players to easily clue the newest card. Meaning that even if the clue "splashes" other unrelated cards in the hand, it will always work to "get" the newest card.
 - But also notice that in the H-Group (and in any sufficiently advanced group of Hanabi players that does a lot of _Finesses_), we have a lot of good options to "get" a player's _Finesse Position_ card - it is uncommon to have to clue it directly. So this convention isn't helping much.
@@ -17,7 +17,7 @@ The main website lists all of our conventions. But it does not bother listing **
 
 ## Mandatory 5 Stalling
 
-- In the H-Group convention framework, we require that the team collectively performs one _[5 Stall](https://hanabi.github.io/docs/level-2#the-5-stall-cluing-off-chop-5s)_. Why?
+- In the H-Group convention framework, we require that the team collectively performs one _[5 Stall](https://hanabi.github.io/level-2#the-5-stall-cluing-off-chop-5s)_. Why?
 - _5 Stalls_ can be useful because they extend the _Early Game_. Extending the _Early Game_ is good, because it prevents bottom-deck losses.
 - On the other hand, _5 Stalls_ are kind of a waste, as they don't accomplish much in-of-themselves. It is more efficient to only save 5's when they actually get on chop and _need_ to be saved.
 - Thus, requiring one _5 Stall_ is a compromise between extending the _Early Game_ and not doing too many _5 Stalls_.
@@ -26,7 +26,7 @@ The main website lists all of our conventions. But it does not bother listing **
 
 ## Play Order of Multiple 1's
 
-- In the H-Group convention framework, we [play 1's in the opening hand from right-to-left](https://hanabi.github.io/docs/level-3/#part-1---play-order-inversion-in-the-starting-hand). Why?
+- In the H-Group convention framework, we [play 1's in the opening hand from right-to-left](https://hanabi.github.io/level-3#part-1---play-order-inversion-in-the-starting-hand). Why?
 - First, notice that in Hanabi, when multiple cards are clued, players typically feel that playing the left-most (newest) card is "logical".
 - For example, in a 2 player game:
   - It is the first turn of the game and nothing is played on the stacks.
@@ -35,7 +35,7 @@ The main website lists all of our conventions. But it does not bother listing **
   - Bob plays slot 1 as red 1.
 - Why does this seem logical? The reason is that a big part of Hanabi is discarding and waiting patiently for playable cards to be drawn. When a new playable card is drawn, it is usually immediately given a clue. So interpreting _Play Clues_ as being focused on the card that was just drawn makes a lot of sense.
 - This "left-most" logic applies for most of the game. But notice that this logic does not apply to the opening hand. A playable card in the opening hand is **equally likely to be in any slot at all**, since the deck was shuffled randomly. So that explains why it is not necessarily "correct" to play 1's in the starting hand from left-to-right. But is it actually beneficial to play the 1's from right-to-left instead?
-- The H-Group closely follows _[Good Touch Principle](https://hanabi.github.io/docs/beginner/good-touch-principle)_. A common problem with _Good Touch Principle_ is when one player has two copies of the same card in their hand. Even if the card is playable right now (e.g. a red 1), cluing it would be a no-no, since it would be a _Bad Touch_.
+- The H-Group closely follows _[Good Touch Principle](https://hanabi.github.io/beginner/good-touch-principle)_. A common problem with _Good Touch Principle_ is when one player has two copies of the same card in their hand. Even if the card is playable right now (e.g. a red 1), cluing it would be a no-no, since it would be a _Bad Touch_.
 - Instead, the typical strategy is to do nothing and patiently wait for that player to discard. Eventually, the player will discard the first copy of the card, allowing the remaining copy to be clued in a "clean" way.
 - So, what about the inverse? What about when players do **not** patiently wait for a discard and instead clue two or more 1's immediately? The player who receives the clue knows that out of all of the 1s, the most important 1 must be the chop card (or the card closest to chop). Otherwise, if it were a "bad" 1, then the team would do nothing and let it get discarded!
 - It follows that players should always play 1's in the starting hand from right-to-left.
@@ -44,14 +44,14 @@ The main website lists all of our conventions. But it does not bother listing **
 
 ## 3 Bluffs
 
-- In the H-Group convention framework, we extend the _[Bluff](https://hanabi.github.io/docs/level-10#the-bluff)_ convention, allowing players to _Bluff_ with [any 3 that they want](https://hanabi.github.io/docs/level-12#the-3-bluff). Why?
+- In the H-Group convention framework, we extend the _[Bluff](https://hanabi.github.io/level-10#the-bluff)_ convention, allowing players to _Bluff_ with [any 3 that they want](https://hanabi.github.io/level-12#the-3-bluff). Why?
 - Read the [story of 3 Bluffs](3-bluffs.md), which is on a separate page.
 
 <br />
 
 ## Discarding Trash From Left to Right
 
-- In the H-Group convention framework, [we discard known-trash from left-to-right](https://hanabi.github.io/docs/level-6#the-trash-order-chop-move-tocm). Why?
+- In the H-Group convention framework, [we discard known-trash from left-to-right](https://hanabi.github.io/level-6#the-trash-order-chop-move-tocm). Why?
 - Intuitively, you would expect that trash should be discarded from right-to-left, because that is the order that we normally discard cards in.
 - However, this does not work well if you use the _Trash Finesse_ convention and it gets deferred.
 - For example, consider [this replay](https://hanabi.live/replay/16627#32):
@@ -73,7 +73,7 @@ The main website lists all of our conventions. But it does not bother listing **
 
 ## The Elimination Finesse Calling for Oldest Card
 
-- In the H-Group convention framework, we arbitrarily decide that [_Elimination Finesses_ call for the right-most card](https://hanabi.github.io/docs/level-16#the-elimination-finesse) instead of the left-most card. Why?
+- In the H-Group convention framework, we arbitrarily decide that [_Elimination Finesses_ call for the right-most card](https://hanabi.github.io/level-16#the-elimination-finesse) instead of the left-most card. Why?
 - Intuitively, you would expect the left-most card should be called for, since that is how _Finesses_ normally work.
 - However, consider the following 3-player game:
   - No red cards are played on the stacks.
@@ -91,7 +91,7 @@ The main website lists all of our conventions. But it does not bother listing **
 
 ## The 5-Pull
 
-- In the H-Group convention framework, we play with the _[5 Pull](https://hanabi.github.io/docs/level-17/#the-5-pull)_, which is a move that causes a blind-play to the right of the 5. Where did this arbitrary convention come from?
+- In the H-Group convention framework, we play with the _[5 Pull](https://hanabi.github.io/level-17#the-5-pull)_, which is a move that causes a blind-play to the right of the 5. Where did this arbitrary convention come from?
 - Right now, we play with a rule of "you cannot perform a _5 Stall_ if there is something else to do". However, this rule did not always exist. Before this rule was created, we would perform _5 Stalls_ when a 5 was on someone's _Finesse Position_, with the purpose of moving their _Finesse Position_ to the next slot. Then, another player would take advantage of this and perform a _Finesse_ or _Bluff_ to get the card on the next slot.
 - For example, in a 4-player game:
   - It is the first turn and nothing is played on the stacks.