From 2b4a4cb536edcbb03af9ac2277a8db53eae19a4c Mon Sep 17 00:00:00 2001
From: Krystine Sherwin <93062060+KrystalDelusion@users.noreply.github.com>
Date: Mon, 27 May 2024 15:48:00 +1200
Subject: [PATCH] Docs: Fix fsm.rst

`$mux-tree` should be `$mux`-tree.
---
 docs/source/using_yosys/synthesis/fsm.rst | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/docs/source/using_yosys/synthesis/fsm.rst b/docs/source/using_yosys/synthesis/fsm.rst
index cc3d0879d..9a0e045cc 100644
--- a/docs/source/using_yosys/synthesis/fsm.rst
+++ b/docs/source/using_yosys/synthesis/fsm.rst
@@ -63,12 +63,10 @@ information is determined:
 The state registers (and asynchronous reset state, if applicable) is simply
 determined by identifying the driver for the state signal.
 
-.. todo:: Figure out what `$mux-tree` should actually be.
-
-From there the `$mux-tree` driving the state register inputs is recursively
-traversed. All select inputs are control signals and the leaves of the
-`$mux-tree` are the states. The algorithm fails if a non-constant leaf that is
-not the state signal itself is found.
+From there the `$mux`\ -tree driving the state register inputs is recursively
+traversed. All select inputs are control signals and the leaves of the `$mux`\
+-tree are the states. The algorithm fails if a non-constant leaf that is not the
+state signal itself is found.
 
 The list of control outputs is initialized with the bits from the state signal.
 It is then extended by adding all values that are calculated by cells that