-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed the spelling mistake of Ancillary #187
Conversation
✅ Deploy Preview for vocabulary-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi, @raj, great work. |
@Raja-Abrar-Khan Hi, and thanks for your enthusiasm Yes, please don't open PRs before things have moved to Please see the Contribution Guidelines for more info. Additionally, we try not to do formatting changes grouped with other changes, please revert the additional changes you've made to this PR, so that the changes reflect only what is outlined in the Issue it is addressing. |
@Raja-Abrar-Khan Please remove the extra formatting changes, so this PR only addresses the spelling fixes associated with this Issue. |
Thank you for your feedback! I will ensure that the PR only includes the necessary spelling fixes for "Ancillary." I’ll review the changes and remove any unrelated formatting adjustments. |
replaced by: Closing. |
Fixes
Description
I corrected the spelling of "Ancillary" in all files where the term was misspelled, including the docs/index.html file and all other relevant files in the project folder. This update ensures consistent usage across the project and improves the professionalism of the website's UI.
Technical details
.Updated the spelling of "Ancillary" in:
-docs/index.html (lines 207 and 248)
-src/css/vocabulary.css
-All other files across the project where the incorrect spelling appeared, including HTML, CSS, and any other source files using
the term.
Tests
To verify this PR:
Screenshots
Checklist
Update index.md
).main
ormaster
).visible errors.
Developer Certificate of Origin
For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."
Developer Certificate of Origin