Fix various spelling errors and typos in the documentation and code comments

[RONAK-AI647]

What would you like to be added/modified:
I've noticed several spelling errors and minor typos in the documentation and code comments throughout the repository. While none of them are critical, fixing them will improve the overall quality and readability of the project.

Like:
stARTT: Should be start
documenattionncan: Should be documentation can
abiother: Should be another
firts: Should be first
contributrbute: should be contribute any many more

Why is this needed:
This gives a more formal look to the repo and enhances Professionalism and Credibility ,Clarity and Readability and a better User Experience.

Solution:
I can manually do the changes but number is quite high especially in README.md or docs .
Investigate and propose a Continuous Integration (CI) process to automatically check for spelling errors in future contributions is a good idea I believe. This would help prevent similar issues from being introduced later.

What I propose:
I see the workflow main-doc.yaml which is indeed triggered only by documentation changes and is configured to skip other CI check . If I add a great Python module for this task like pyspelling. It is highly configurable and works well within a CI environment , It will make sure to run when any doc or md files changed.

[RONAK-AI647]

@MooreZheng , If you approve this issue and idea .. I will work on it .

[MooreZheng]

Sounds good to me. Just make sure the CI process will not be too disturbing for contributors. For example, 1) Spell check can be used as a suggestion for merging, but should not be the core barrier to merging. 2) For each commit, the proposed method should make sure that only the submitted material is tested instead of the whole ianvs project. Feel free to let us know if there are further considerations and designs.

[RONAK-AI647]

/assign

[RONAK-AI647]

Hello, I've been investigating the issue, and while working on the spell-check feature, I noticed a potential conflict in the existing CI/CD setup.

The .github/workflows/main-docs.yaml file is configured to trigger on documentation (.md) changes, but its job is named pylint. This seems contradictory, as pylint is for Python code analysis.

To implement a spell check, I propose either replacing this main-docs.yaml file with a dedicated spell-check workflow or updating its logic to perform a spell check instead of a placeholder echo command.

As @MooreZheng told , now to create a barrier , rather a soft warning. So I edited the current workflow to do so and tested in my forks , they do well.

Would you prefer that I create a new, separate workflow file for spell-checking documentation, or should I modify the existing main-docs.yaml file?
Anything to say on this @AryanNanda17 , I see these files had their last commits by you.

[AryanNanda17]

Would you prefer that I create a new, separate workflow file for spell-checking documentation, or should I modify the existing main-docs.yaml file?

You can modify the current main-docs.yaml file only, as it is currently redundant and does not perform any checks.