In at least 3 instances, there is a mismatch between a doc'' path (its location in the file structure) and its order/level in the TOC. Because our content renderer relies on matching a doc's path to the url to decide active states (of the doc's link in the TOC and any parent doc's links) some items receive misleading/incorrect active states.
Thanks for catching this, Blake. I've fixed this by adjusting the docs themselves. We may need to circle back at some point to make this nav behavior more robust, but I think we're good for now.
In at least 3 instances, there is a mismatch between a doc'' path (its location in the file structure) and its order/level in the TOC. Because our content renderer relies on matching a doc's path to the url to decide active states (of the doc's link in the TOC and any parent doc's links) some items receive misleading/incorrect active states.