fix typos

[chrira]

📝 Description

Fixing typos in documentation.

🎯 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🧪 Test improvements
• 🔧 Code refactoring
• 🎨 UI/UX improvements

🧪 Testing

Test Environment

• Tested with Docker deployment
• Tested with direct Python deployment
• Tested on macOS
• Tested on Linux
• Tested on Windows

Test Cases

• All existing tests pass
• New tests added for new functionality
• Manual testing completed
• System health check passes

📋 Checklist

Code Quality

• Code follows the project's coding standards
• Self-review of the code completed
• Code is properly commented
• Type hints added (Python)
• No console.log statements left in production code

Documentation

• Documentation updated (if applicable)
• API documentation updated (if applicable)
• README updated (if applicable)
• CONTRIBUTING.md guidelines followed

Dependencies

• No new dependencies added, or new dependencies are justified
• requirements.txt updated (if applicable)
• package.json updated (if applicable)

🖥️ Screenshots (if applicable)

Add screenshots to help reviewers understand the changes.

📊 Performance Impact

Describe any performance implications:

• No performance impact
• Performance improved
• Performance may be affected (explain below)

🔄 Migration Notes

If this is a breaking change, describe what users need to do:

• No migration needed
• Migration steps documented below

📎 Additional Notes

Any additional information that reviewers should know.