Fix directory and filename typos across the codebase

[coder-tejas]

Current Behavior

Over time, a few minor typos have slipped into our directory and file naming conventions in the src/ directory. Examples include CssBaseLine (incorrect MUI spelling), SocialMedial (extra 'l'), and responsive-coulmns.tsx/ (misspelled word plus an incorrect folder extension). While these do not break functionality, they are confusing for developers and violate standard naming conventions.

Expected Behavior

All directories and files should be correctly spelled and follow proper casing conventions (e.g., CssBaseline, SocialMedia, README.md).

Screenshots/Logs

N/A

Environment

N/A (Codebase-level hygiene issue)

📋 Checklist of Required Renames

• Fix MUI spelling: src/base/CssBaseLine/ → src/base/CssBaseline/
• Fix capitalization (I vs l): src/custom/TypingFilter/TypingFIlterInput.tsx → TypingFilterInput.tsx
• Fix capitalization (I vs l): src/custom/TypingFilter/TypingFIlters.tsx → TypingFilters.tsx
• Fix spelling: src/custom/Prompt/promt-component.tsx → prompt-component.tsx
• Fix spelling & remove folder extension: src/custom/Helpers/ResponsiveColumns/responsive-coulmns.tsx/ → responsive-columns/
• Fix spelling: src/icons/SocialMedial/ → src/icons/SocialMedia/
• Standardize casing: src/custom/readme.md → src/custom/README.md
• Standardize casing: src/schemas/readme.md → src/schemas/README.md

⚠️ Important Notes for Contributors

1. Update Imports: Whenever you rename a file or folder, please ensure you update the corresponding imports in their parent index.ts / index.tsx files (and anywhere else they might be imported).
2. Git Case-Sensitivity: If you are on macOS or Windows, Git might not recognize a simple casing change (e.g., readme.md to README.md). You may need to do a two-step rename:

   git mv readme.md readme-temp.md
   git mv readme-temp.md README.md

3. Use git mv: Please use git mv for the renames so Git tracks the file history correctly instead of showing them as deleted/added.

🧪 How to Test

• Run npm run build (or yarn build) to ensure there are no broken imports or missing module errors.
• Optionally run npm run test (or yarn test) to ensure nothing is broken.

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Sistent site in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack