Changed for(... i++) to for .. of

[AnnuJoshi]

Description of Change

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is changed or added
• PR title follows semantic commit guidelines

Release Notes

Notes:

[welcome]

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[codebytere]

hi @AnnuJoshi while we appreciate your contribution this does not qualify as a typo or issue and is therefore not something we feel needs to be changed. In the future, we would also appreciate if you would follow commit guidelines and fill out the provided checklist in order for your PRs to be reviewed.

[ckerr]

@codebytere there is definitely some non-typo / non-bug work that would be accepted in the docs, eg. #14842 to ES6ify the code examples in the documentation.

I agree with turning down this specific PR because it's too minor a change and because of issues with the proposed code (e.g. no const/let before the scope variable, bug in treating for-of like for-in, etc) but I would not want people reading this page to think we only want typo / bugfix changes in our docs.