Good finding, thank you. I think that was a typo while creating the directory structure. Instead of adjusting the link, we should rename the uses-cases directory to use-cases.

@polarathene @wernerfred Whats your take on this?

@polarathene @wernerfred Whats your take on this?

This:

Instead of adjusting the link, we should rename the uses-cases directory to use-cases.

@wernerfred Do you know of an easy way to check for dead internal links in our documentation?

@wernerfred Do you know of an easy way to check for dead internal links in our documentation?

sadly not, i think @polarathene mentioned that he wanted to build something like this for CI last year but had no time to implement it yet IIRC

Do you know of an easy way to check for dead internal links in our documentation?

Yes it's on my backlog, my broken PC disk should have notes regarding it once I restore it later this week.

I think I was going to use a rust project lychee with the CI. We need to test markdown local links are valid (building docs with --strict mostly does that at least for file paths, but fails against validating anchor tags #), and also testing links on built docs.

Anyway, it'll get addressed eventually unless someone beats me to it 😅

Also agree on changing the docs file name instead.

It won't affect previous docs which are versioned (which also retain typos/bugs). We may at a later point want to consider rebuilding old tags with newer version of the docs generator, but it may not be worth it either (there was some deprecations a while back, one with admonition support I think and recently the mermaid one).

I will merge this after #2420

Documentation preview for this PR is ready! 🎉

Built with commit: cca0f77