{bp-15922} arch/arm, risc-v: Fix typos in Code Comments

[jerpelea]

Summary

This PR fixes the typos in the Code Comments of chip.h, allocateheap.c and start.c. The typos were discovered here:

• arch/risc-v/eic7700x: Add support for ESWIN EIC7700X SoC #15921

Impact

RELEASE

Testing

CI

[nuttxpr]

[Experimental Bot, please feedback here]

No. The provided PR information is insufficient. While it mentions what files changed and links a related PR, it lacks critical details required by the NuttX PR template.

Here's why it's insufficient and what's missing:

• Summary: While it mentions fixing typos, it doesn't explain what functional part of the code these comments relate to. This helps reviewers understand the context and potential impact of even seemingly minor changes. The link to the other PR is helpful but shouldn't replace a concise summary within this PR itself.

• Impact: Simply stating "RELEASE" is not enough. While the impact might be minimal for typo fixes, the template requires explicit "YES/NO" answers for each category, along with descriptions for any "YES" responses. Even if all answers are "NO," stating so explicitly is important.

• Testing: "CI" is insufficient. The template requires:

  • Specifics about the build host (OS, CPU, compiler).
  • Specifics about the target (architecture, board, configuration).
  • Actual testing logs before and after the change, demonstrating the correction. Relying solely on CI isn't enough, especially for seemingly minor changes that CI might not explicitly catch or log in a visible way.

In short, the PR needs to be significantly more detailed to meet the NuttX requirements. While the changes themselves may be small, the required information is essential for proper review and integration.

[cederom]

Thank you @jerpelea and @lupyuen :-)