docs: clarify role of N and in-place behavior in cumax

[YOGigx]

Resolves #{{TODO: add issue number}}.

Description

What is the purpose of this pull request?

This pull request:

• {{TODO: add description describing what this pull request does}}

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• #{{TODO: add related issue number}}

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.

No.

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

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

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@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!

[YOGigx]

Description

-[x] Read,understood, and followed the contribution guidelines

What is the purpose of this pull request?

This pull request:

This pull request improves the documentation for the cumax function by clarifying the role of the N parameter and explaining its in-place behavior when writing results to the output array y.
-It explains that only the first N elements (as determined by strideX) are processed and that results are written into the output array using strideY, leaving any remaining elements unchanged. This clarification is intended to help new users better understand the function’s behavior and avoid confusion when working with larger output arrays.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

N/A

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.

No.

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

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

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

I used AI assistance to better understand the existing cumax behavior and to help phrase clearer documentation. All changes were authored manually and no code logic was generated by AI.

@stdlib-js/reviewers

[kgryte]

@YOGigx Thank you for your interest in stdlib and for opening this PR. While we appreciate the sentiment behind this PR, we won't be accepting the proposed change, as the content of the note is already covered by existing documentation and examples.

Thanks again, and we look forward to your future contributions! 🚀

[YOGigx]

"Hi @kgryte, Thank you for the reviewing and the clarification! I 'll look for other areas where I can contribute without duplicating existing documentation. Thanks again!