docs: fix incorrect example output in csrot dtype declarations

[Atharv1405]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: na
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: na
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed

---

Resolves #8700.

Description

This pull request fixes incorrect example output values in the csrot TypeScript declaration documentation.

Specifically:

• Corrects the last element of the viewX example output to 8.0
• Corrects the last element of the viewY example output to 6.0
• Updates the example arrays to match the expected results of the BLAS csrot operation
• Ensures formatting consistency with other examples in the package (~ for approximate values)

No implementation changes were made. This is a documentation-only update.

Related Issues

None.

Questions

No questions.

Other

No additional information.

Checklist

• Read, understood, and followed the contributing guidelines.

AI Assistance

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

I used ChatGPT to help verify the expected numerical output of the csrot example and to ensure the commit message and PR description follow stdlib contribution guidelines. All changes were manually applied by me.

---

@stdlib-js/reviewers

[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 Gitter channel to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Gitter channel
• 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
blas/base/wasm/csrot	$\color{green}706/706$ $\color{green}+100.00%$	$\color{green}17/17$ $\color{green}+100.00%$	$\color{green}6/6$ $\color{green}+100.00%$	$\color{green}706/706$ $\color{green}+100.00%$

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

[kgryte]

Ref: #8752

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.