docs: fix broken Markdown link (issue #9149)

[abhayypancholi]

Resolves #9149

Description

What is the purpose of this pull request?

This pull request:

• This resolved the broken link issue (error 404) by replacing it with the correct link
• gets the user to their concerned path not on a false/damaged link

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Resolves Fix broken Markdown link: https://www.netlib.org/lapack/explore-html-3.6.1/d7/d43/group__aux_o_t_h_e_rauxiliary_ga89e332374c7cd87e5db54bfe21550bc3.html #9149

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Found the working link for dlaset from LAPACK using Wayback Machine.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• [ * ] Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• [ * ] No

@stdlib-js/reviewers

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
lapack/base/dlaset	$\color{green}592/592$ $\color{green}+100.00%$	$\color{green}37/37$ $\color{green}+100.00%$	$\color{green}7/7$ $\color{green}+100.00%$	$\color{green}592/592$ $\color{green}+100.00%$

The above coverage report was generated for the changes in this PR.

[Planeshifter]

Resolved via b0962b9. Thanks for opening a PR; notice that in this case, using current documentation link would be preferable than relying on web archive.