Skip to content

docs: fix misspellings in JSDoc and the generated API reference - #3131

Open
vaibhav8a wants to merge 1 commit into
phcode-dev:mainfrom
vaibhav8a:fix-jsdoc-typos
Open

docs: fix misspellings in JSDoc and the generated API reference#3131
vaibhav8a wants to merge 1 commit into
phcode-dev:mainfrom
vaibhav8a:fix-jsdoc-typos

Conversation

@vaibhav8a

Copy link
Copy Markdown

Fixes five misspellings that appear in both the JSDoc comments and the API reference generated from them.

Typo Source files
overriden overridden src/command/KeyBindingManager.js, src/preferences/PreferencesManager.js, src/editor/CodeHintList.js
fucntion function src/features/QuickViewManager.js, src/preferences/StateManager.js
seperated separated src/utils/EventManager.js, src/view/ThemeManager.js
specifed specified src/view/Pane.js (×2)
persistant persistent src/widgets/PopUpManager.js

docs/API-Reference/** is generated from these JSDoc blocks, so fixing only the markdown would be undone on the next docs build. Each correction is therefore applied to the source comment and to the corresponding generated page (KeyBindingManager.md, QuickViewManager.md, StateManager.md, EventManager.md, Pane.md, PopUpManager.md) so the committed tree matches what the generator would now emit.

Comments and documentation only — no identifiers, APIs, or behaviour touched. I skipped the same spelling in src/styles/bootstrap/, which is vendored third-party code.

If you'd rather regenerate the docs yourselves, I can drop those six files and leave just the source comments.

overriden -> overridden, fucntion -> function, seperated -> separated,
specifed -> specified, persistant -> persistent.

docs/API-Reference/ is generated from JSDoc, so each fix is applied to the
source comment and to the generated page, keeping the two in sync.
@sonarqubecloud

Copy link
Copy Markdown

@abose

abose commented Aug 26, 2026

Copy link
Copy Markdown
Member

Thanks for the contributing @vaibhav8a . The changes looks good.

Can you just comment, "I grant permission to distribute my contributions in this pull request under MIT License Terms." for me to be able to merge this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants