Fix awesome-lint spelling issues in README.md #52
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@palashmon 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: palashmon <[email protected]>
Copilot
AI
changed the title
[WIP] Fix awesome-lint issues
Fix awesome-lint spelling issues in README.md
Sep 21, 2025
palashmon
approved these changes
Sep 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes all 10 spelling and capitalization errors identified by
awesome-lintin the README.md file. The linter was failing due to incorrect capitalization and formatting of technology names that don't follow their official conventions.Changes Made
Fixed the following spelling/capitalization issues:
git→Git- Proper capitalization for Git version control systemPostgresql→PostgreSQL- Correct official capitalization for PostgreSQL databasereact→React- Proper capitalization for React frameworkNextJs→Next.js- Correct formatting with period for Next.js frameworkjest→Jest- Proper capitalization for Jest testing frameworkPOSTMAN→Postman- Corrected from all caps to proper case for Postman API toolTypescript→TypeScript- Correct camelCase capitalization for TypeScriptTypescript→TypeScript- Correct camelCase capitalization for TypeScriptTypescript→TypeScript- Correct camelCase capitalization for TypeScriptvuejs→Vue.js- Correct formatting with period for Vue.js frameworkVerification
After these changes,
npx awesome-lintnow passes successfully with no errors:All changes are minimal and preserve the exact content and structure of the README.md file while ensuring compliance with awesome-lint requirements.
Fixes #51.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com/repos/palashmon/awesome-js-postsawesome-lint(http block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.