fix(docs): update locale file path

[Kaseax]

Description

Please provide a clear description of your changes.

While browsing the code, I found that there are some wrong paths in the CONTRIBUTING and TRANSLATION files, which this PR just fixes: nothing special

Type of Change

Please delete options that are not relevant.

• 📝 Documentation update

Areas Affected

Please check all that apply:

• Email Integration (Gmail, IMAP, etc.)
• User Interface/Experience
• Authentication/Authorization
• Data Storage/Management
• API Endpoints
• Documentation
• Testing Infrastructure
• Development Workflow
• Deployment/Infrastructure

Testing Done

Describe the tests you've done:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Security Considerations

For changes involving data or authentication:

• No sensitive data is exposed
• Authentication checks are in place
• Input validation is implemented
• Rate limiting is considered (if applicable)

Checklist

• I have read the CONTRIBUTING document
• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• My changes generate no new warnings
• [] I have added tests that prove my fix/feature works
• All tests pass locally
• Any dependent changes are merged and published

Additional Notes

Add any other context about the pull request here.

Screenshots/Recordings

Add screenshots or recordings here if applicable.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

Summary by CodeRabbit

• Documentation
  • Updated instructions and examples to reflect the new path for English source strings and translation files in the internationalization documentation.
  • Revised configuration examples to use the updated directory for translation JSON files.

[coderabbitai]

Walkthrough

The documentation was updated to correct the file paths for English source strings and translation JSON files in the internationalization and translation configuration sections. The paths now reference the "messages" directory instead of "locales" in both the contributing and translation guide documents.

Changes

File(s)	Change Summary
.github/CONTRIBUTING.md	Updated i18n section to correct the path for English source strings.
.github/TRANSLATION.md	Changed Lingo.dev config example to use new translation file path.

Possibly related PRs

• docs: add @LingoDotDev instructions to translation.md #665: Rewrites the translation guide to introduce the Lingo.dev workflow and references the updated translation file paths.
• chore: translation docs #446: Adds new i18n documentation sections, related to translation docs but not the same content.
• docs #438: Adds the initial translation guide and README references, related to translation documentation.

Suggested reviewers

• MrgSub

Poem

In docs we hop, with careful paws,
Adjusting paths without a pause.
From "locales" to "messages" we leap,
Ensuring translations are tidy and neat.
With every change, our warren grows,
Clearer guides for all—so the story goes!
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d0113d0 and 92fa32e.

📒 Files selected for processing (2)

• .github/CONTRIBUTING.md (1 hunks)
• .github/TRANSLATION.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

.github/CONTRIBUTING.md

[grammar] ~196-~196: There might be a mistake here.
Context: ...gs** - Place all user-facing text in apps/mail/messages/en.json - Organize strings according to the existing struc...

(QB_NEW_EN_OTHER)