chore: change naming to general court

[kemuru]

PR-Codex overview

This PR updates the text in the Description.tsx file to change the name of the court mentioned in the complaint process from the Kleros Freelancing Court to the Kleros General Court.

Detailed summary

• Modified text in <StyledP>:
  • Changed "Kleros Freelancing Court" to "Kleros General Court".

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

• Style
  • Updated the dispute resolution clause to reference "Kleros General Court" instead of "Kleros Freelancing Court."

[netlify]

✅ Deploy Preview for kleros-escrow-v2 ready!

Name	Link
🔨 Latest commit	f1c99af
🔍 Latest deploy log	https://app.netlify.com/projects/kleros-escrow-v2/deploys/6893333cc777eb00089bd813
😎 Deploy Preview	https://deploy-preview-123--kleros-escrow-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

The text in the Description component was updated to reference "Kleros General Court" instead of "Kleros Freelancing Court" in a dispute resolution clause. No other changes to logic, control flow, or error handling were made.

Changes

Cohort / File(s)	Change Summary
Dispute Resolution Text Update web/src/components/PreviewCard/Terms/Description.tsx	Changed arbitration court reference from "Kleros Freelancing Court" to "Kleros General Court" in component text.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A nibble here, a nibble there,
The court has changed with utmost care.
General, not Freelancing now,
The clause is clear, the text knows how.
With gentle hops, the change is made—
Another bug-free patch displayed! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/change-court-display

---

🪧 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.
• 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.

Support

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

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 generate unit tests to generate unit tests for 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 or @coderabbitai title 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: 0

🧹 Nitpick comments (1)

web/src/components/PreviewCard/Terms/Description.tsx (1)

145-147: Consider externalising hard-coded court names

Even though this is just a copy tweak, the court name now appears as a hard-coded literal. If the organisation ever rebrands or supports multiple locales, hunting down string literals can be error-prone. Consider moving the court name into a constants file (e.g. consts/courts.ts) or an i18n dictionary so it can be reused (and translated) consistently.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7dd88a4 and f1c99af.

📒 Files selected for processing (1)

• web/src/components/PreviewCard/Terms/Description.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Redirect rules - kleros-escrow-v2
• GitHub Check: Redirect rules - kleros-escrow-v2
• GitHub Check: Header rules - kleros-escrow-v2
• GitHub Check: Header rules - kleros-escrow-v2
• GitHub Check: Pages changed - kleros-escrow-v2
• GitHub Check: Pages changed - kleros-escrow-v2

🔇 Additional comments (1)

web/src/components/PreviewCard/Terms/Description.tsx (1)

145-147: Court name updated correctly – no further action required

The wording change from “Kleros Freelancing Court” to “Kleros General Court” aligns with the desired naming and does not affect runtime behaviour.