Translations to clarify which documents can be uploaded

[larssondenise]

Describe the background of your pull request

What does your pull request do? Does it solve a bug (which one?), add a feature?

Additional context

Add any other context

Governance

• Documentation is added
• Test cases are added or updated

By submitting this pull request I confirm that:

• I've read the contributing document https://github.com/alkem-io/.github/blob/master/CONTRIBUTING.md.
• I've read and understand the Code of Conduct https://github.com/alkem-io/.github/blob/master/CODE_OF_CONDUCT.md.
• I understand that any contributions or suggestions I made may make it into the actual code. I've read the License
  https://github.com/alkem-io/Coordination/blob/master/LICENSE.
• I understand that submitting the pull request requires agreeing to and signing the contributor license agreement.

Summary by CodeRabbit

• New Features
  • Enhanced clarity in user interface text strings, improving instructions and descriptions.
  • Updated file upload helper text to specify supported file types (Word, PDF, Excel, images) and size limit (15 MB).
  • Simplified description for creating a Virtual Contributor.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the translation.en.json file, which contains text strings for the user interface. Modifications include clarifying phrases, enhancing the helper text for file uploads, and refining descriptions related to the creation of a Virtual Contributor. The overall goal is to improve clarity and consistency in the language used throughout the application, making it more intuitive for users.

Changes

File	Change Summary
src/core/i18n/en/translation.en.json	- Updated "Add link to {{title}}" to "Add links or documents to {{title}}".
	- Revised helper text to specify upload options: "You can upload Word, PDF, Excel, or images up to 15 MB".
	- Changed "Written knowledge in text and documents" to "Written knowledge in text".
	- Minor adjustments to tooltips and confirmation dialogs for improved clarity.

Possibly related PRs

• Update translation.en.json Welcome at should be Welcome to #6918: This PR also modifies the translation.en.json file, focusing on improving the clarity of user greetings, which aligns with the main PR's goal of enhancing user interface text clarity.
• Change text to make more clear, issue 7030 #7040: This PR makes extensive changes to the translation.en.json file, updating various user interface texts for clarity, which is directly related to the main PR's focus on improving text strings.
• Adjust VC campaign text #7182: This PR updates text strings in the translation.en.json file to enhance clarity and consistency, similar to the changes made in the main PR.
• Update translation.en.json Subsp template: Enter Subspace URL instead… #7206: This PR modifies the translation.en.json file to improve user prompts regarding Subspace URLs, which is in line with the main PR's objective of refining user interface text for better understanding.

Suggested labels

client, translations

Suggested reviewers

• SimoneZaza

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cb513c7 and c4491b5.

📒 Files selected for processing (1)

• src/core/i18n/en/translation.en.json (3 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/core/i18n/en/translation.en.json (1)

Pattern src/**/*.json: Review the JSON files for correct syntax and structure.
Ensure that the configuration and data are accurate and follow the project's standards.
Check for sensitive data exposure and ensure that the data is properly validated.

🔇 Additional comments (2)

src/core/i18n/en/translation.en.json (2)

708-708: LGTM! The text change improves clarity.

The updated text better reflects the functionality by explicitly mentioning both links and documents.

---

1448-1448: LGTM! The helper text now provides clear upload guidelines.

The updated text improves user experience by explicitly stating supported file types and size limits upfront.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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

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.