English user guide: add temporary string to cause xliff regeneration.

[michaelDCurran]

First of two janitorial PRs for xliff support:
After merging the Crowdin stuff, I realise I need to make two more commits to beta. One to add a temporary string to the user guide, and one then to remove it. This will cause userguide.xliff to be re-built.

1. I should have merged beta into xliff one more time before I merged the pr, to catch the poedit change to the user guide. But also
2. userGuide.xliff currently lists a commit in its file header that no longer exists as the pr was a squash merge (as we always do).
   Bumping userGuide.md with an added line, and then a removed line will fix this.
   Any future changes to userGuide.md in beta will be handled as expected by the Github action.

[coderabbitai]

Walkthrough

The change involves the addition of a new line of text, "Crowdin Test string 1," under the Introduction section of the user guide. This update serves to enhance the documentation without affecting existing functionality or logic.

Changes

Files	Change Summary
user_docs/en/userGuide.md	Added "Crowdin Test string 1" under Introduction section.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation

    User->>Documentation: Request for user guide
    Documentation-->>User: Provide user guide with updated content
    User->>Documentation: Read Introduction section
    Documentation-->>User: Show "Crowdin Test string 1"

Loading

---

Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6fbbc10 and 42d1d72.

Files selected for processing (1)

• user_docs/en/userGuide.md (1 hunks)

Files skipped from review due to trivial changes (1)

• user_docs/en/userGuide.md

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

Tip

Early access features: enabled

We are currently testing the following features in early access:

• Anthropic claude-3-5-sonnet for code reviews: Anthropic claims that the new Claude model has stronger code understanding and code generation capabilities than their previous models. Note: Our default code review model was also updated late last week. Please compare the quality of the reviews between the two models by toggling the early access feature.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues on the discussion post.