fix: correct typo 'seperate' to 'separate' in translation files

[mendorshikh]

Summary

Fixed typo: 'seperate' → 'separate' in translation key and usage.

Changes

• InviteForm.tsx: Updated translation key usage
• en/settings.json: Fixed translation key
• mn/settings.json: Fixed translation key

Type

• Typo fix

Review time: < 30 seconds

Summary by Sourcery

Fix a misspelled translation key and its usage in the invite form and locale files.

Bug Fixes:

• Correct the invite form helper text to use the properly spelled 'separate-emails' translation key.

Enhancements:

• Align English and Mongolian settings locale files with the corrected translation key spelling.

Summary by CodeRabbit

• Bug Fixes
  • Corrected spelling error in translation keys from "seperate-emails" to "separate-emails" across language files and team member invitation component.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Fixes a typo in the email helper translation key from 'seperate-emails' to 'separate-emails' and aligns both frontend usage and backend locale definitions across English and Mongolian settings translations.

File-Level Changes

Change	Details	Files
Rename the translation key from 'seperate-emails' to 'separate-emails' and update its usages in the invite form and locale files.	Update the InviteForm component to use the corrected translation key in the helper text. Change the English settings locale entry key to the corrected spelling while preserving the value. Change the Mongolian settings locale entry key to the corrected spelling while preserving the value.	frontend/core-ui/src/modules/settings/team-member/components/invite/InviteForm.tsx backend/gateway/src/locales/en/settings.json backend/gateway/src/locales/mn/settings.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to be17de6 in 9 seconds. Click for details.

• Reviewed 39 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 0 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

Workflow ID: wflow_TsL86cZoZ6gZ74Oh

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

A spelling correction across locale configuration files and a frontend component, changing the translation key "seperate-emails" to "separate-emails" in English and Mongolian language resources and their corresponding reference in the invite form.

Changes

Cohort / File(s)	Summary
Locale Files backend/gateway/src/locales/en/settings.json, backend/gateway/src/locales/mn/settings.json	Renamed translation key from "seperate-emails" to "separate-emails" in team-member section for both English and Mongolian locales.
Component Usage frontend/core-ui/src/modules/settings/team-member/components/invite/InviteForm.tsx	Updated reference to translation key from 'seperate-emails' to 'separate-emails' for helper text display.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A spelling slip, now caught and fixed,
The double 'e' was in a bind!
From "seperate" to "separate" clear,
Three files aligned, the typo's gone—
Hopping forward with proper words!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: correcting a typo from 'seperate' to 'separate' in translation files across multiple locations.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/typo-separate-invite-form

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud