Update copy text

[alecande11]

https://linear.app/initia-labs/issue/PM-319/minor-copy-adjustments-2

Summary by CodeRabbit

• Style
  • Updated various user-facing messages for improved clarity and consistency, including warnings about transaction fees and memos.
  • Changed references from "history" to "activity" in page titles, tab labels, and notification descriptions.
  • Added or adjusted punctuation in warning messages for a more polished user experience.

[coderabbitai]

Walkthrough

This update revises several user-facing messages and labels throughout the application. Text changes include rewording warnings, updating labels from "history" to "activity," and adding punctuation for clarity. No logic, control flow, or error handling is affected; only the displayed text and labels are modified.

Changes

File(s)	Change Summary
.../bridge/BridgeFields.tsx, .../wallet/txs/send/SendFields.tsx	Updated warning messages to clarify leaving enough funds for fees; improved memo message punctuation.
.../bridge/BridgeHistory.tsx, .../wallet/tabs/Home.tsx, .../bridge/data/tx.ts	Changed "history" labels and messages to "activity" in titles, tabs, and notifications.
.../bridge/SlippageControl.tsx	Added a period to the slippage warning message for grammatical correctness.

Poem

A hop, a skip, a message anew,
From "history" to "activity"—a clearer view!
Warnings now with extra care,
Mind your fees and memos there.
Punctuation dots the field,
For clarity, our code’s now sealed.
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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: 0

🧹 Nitpick comments (1)

packages/widget-react/src/pages/wallet/tabs/Home.tsx (1)

41-43: Consider extracting hard-coded tab labels into a common i18n/label map
The literal string "Activity" is now duplicated across multiple components ( Home, BridgeHistory, tx notification, etc.). Centralising user-facing copy (e.g. via src/i18n/en.json or a UI_LABELS constant) avoids drift in future copy updates and simplifies localisation.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e06be4e and a76712b.

📒 Files selected for processing (6)

• packages/widget-react/src/pages/bridge/BridgeFields.tsx (1 hunks)
• packages/widget-react/src/pages/bridge/BridgeHistory.tsx (2 hunks)
• packages/widget-react/src/pages/bridge/SlippageControl.tsx (1 hunks)
• packages/widget-react/src/pages/bridge/data/tx.ts (1 hunks)
• packages/widget-react/src/pages/wallet/tabs/Home.tsx (1 hunks)
• packages/widget-react/src/pages/wallet/txs/send/SendFields.tsx (1 hunks)

🔇 Additional comments (6)

packages/widget-react/src/pages/bridge/SlippageControl.tsx (1)

50-51: Copy tweak looks good – punctuation added for consistency.

packages/widget-react/src/pages/bridge/BridgeFields.tsx (1)

269-270: Message update acknowledged – wording now matches the Send flow.

packages/widget-react/src/pages/wallet/txs/send/SendFields.tsx (1)

96-101: Copy consistency looks good – fee warning and memo info now align with Bridge flow wording & punctuation.

packages/widget-react/src/pages/bridge/data/tx.ts (1)

168-172: No broken link—/bridge/history is the only registered route
A search through your TS/JS files shows that only /bridge/history is defined (in Routes.tsx) and used (in BridgeForm.tsx and tx.ts). There is no /bridge/activity route, so the link to /bridge/history won’t break. The phrase “activity page” is purely a display label.

Optional: For consistency, you may choose to rename the link text to “history page,” but functionally the code is correct.

packages/widget-react/src/pages/bridge/BridgeHistory.tsx (2)

27-27: Copy update is clear and matches the new terminology
Changing the page title to “Bridge/Swap activity” aligns with the global rename effort and involves no functional impact.

---

41-41: Empty-state copy updated consistently
The new message keeps the wording in sync with the title and other pages. No additional concerns.