broken hooks links in README.md for packages/next

[rexfordessilfie]

New Bug Report

Checklist

• I am not disclosing a vulnerability.
• I have searched through existing issues and the Moralis Forum.
• I can reproduce the issue with the latest SDK release, and my server is updated to the latest version.

Issue Description

When I click on the links for hooks (e.g useEvmWeb3ApiVersion()) in the README for packages/next does not jump to the documentation section for the hook.

Additional: As I and others begin to consult this page more, it would be beneficial to resolve this to make browsing the documentation much easier! Also, I am happy to explore a PR with a fix for this, as I think I spot a solution (lower-casing the fragments for the hooks) that works. Thanks.

Steps + code to reproduce

1. Go to the repo on GitHub in a browser (Chrome or Safari)
2. Access the packages/next section of the repository
3. Scroll to the table of contents section of the README, and click on any hooks under Authentication Api Hooks or EVM Api Hooks (e.g useEvmWeb3ApiVersion())

Actual Outcome

1. The browser does not jump to the appropriate section of the README for the hook (e.g for useEvmWeb3ApiVersion())

Expected Outcome

1. The browser jumps to the appropriate section of the README for the hook (e.g for useEvmWeb3ApiVersion())

Environment

• Browsers: Safari, Chrome

Server

• Moralis server version: N/A

Client

• Moralis SDK version: 2.12.0
• Operating system: Mac OS Ventura
• Browser: Chrome, Safari

Logs

N/A. However, the resulting address when I click on the hook is https://github.com/MoralisWeb3/Moralis-JS-SDK/tree/main/packages/next#%EF%B8%8FuseEvmEndpointWeights, which does not work as expected, compared to https://github.com/MoralisWeb3/Moralis-JS-SDK/tree/main/packages/next#useEvmEndpointWeights, which works as expected.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. for your contributions. If this issue is still affecting you, please leave any comment, and we'll keep it open We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! Thank you.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!