update dead links

[taikoonwang]

Description

this PR fix issue's part 1. for part 2, I think the proper way to do this is to add a readme, so it's outside the scope of the dead link.

Related issue

#2035

Tests

• Yes
• No, because they aren't needed
• No, because I need help

Added to documentation?

• README.md
• Dojo Book
• No documentation needed

Checklist

• I've formatted my code (scripts/prettier.sh, scripts/rust_fmt.sh, scripts/cairo_fmt.sh)
• I've linted my code (scripts/clippy.sh, scripts/docs.sh)
• I've commented my code
• I've requested a review after addressing the comments

[glihm]

Hey @taikoonwang good catch.

| for part 2, I think the proper way to do this is to add a readme, so it's outside the scope of the dead link.

Could you detail that?

Also, would you mind fixing the dojoup README link?

[taikoonwang]

Hey @taikoonwang good catch.

| for part 2, I think the proper way to do this is to add a readme, so it's outside the scope of the dead link.

Could you detail that?

Also, would you mind fixing the dojoup README link?

I mean I have no idea how to fix https://book.dojoengine.org/toolchain/dojoup (which is borken),If we just change it to https://book.dojoengine.org/toolchain (which is also borken), Because the whole toolchain missing an overview readme.

source:

[glihm]

@taikoonwang got you, thanks for the explanation.
You're right before we had a dedicated section for dojoup. But asdf is simplifying the management of several versions and different installation sources.

[glihm]

Thanks for those fixes @taikoonwang. 🙏