Fixed docs file path and page content

[Omri-Levy]

Summary by CodeRabbit

• Documentation
  • Enhanced the formatting of the system overview document for improved readability and consistency.
  • Updated the header in the child workflow section to indicate a pending update, enhancing clarity on the content's status.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ec33782

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The recent changes involve formatting and header adjustments in Markdown documentation files. These updates enhance consistency and clarity without altering the underlying content or its functionality. Notably, one document's section header was changed to indicate pending content, while others received minor formatting tweaks.

Changes

File Path	Change Summary
.../docs/en/getting_started/system_overview.md	Removed extra spaces for improved formatting; content remains unchanged.
.../docs/en/learn/adding_a_child_workflow_to_your_workflow.md	Section header changed to "## TODO," indicating incomplete content without functional impact.

Poem

In a world of text, so neat and bright,
A rabbit hops in with joy and delight.
With spaces removed, and headers so clear,
Our docs now shine, let’s give a cheer!
🐇✨

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 3

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c4ea42e and ec33782.

Files selected for processing (2)

• websites/docs/src/content/docs/en/getting_started/system_overview.md (3 hunks)
• websites/docs/src/content/docs/en/learn/adding_a_child_workflow_to_your_workflow.md (1 hunks)

Files skipped from review due to trivial changes (1)

• websites/docs/src/content/docs/en/learn/adding_a_child_workflow_to_your_workflow.md

Additional context used

Markdownlint

websites/docs/src/content/docs/en/getting_started/system_overview.md

66-66: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

104-104: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

LanguageTool

websites/docs/src/content/docs/en/getting_started/system_overview.md

[duplication] ~101-~101: Possible typo: you repeated a word
Context: ...Using Plugins ## Webhooks Webhooks in Ballerine allow for real-time commun...

(ENGLISH_WORD_REPEAT_RULE)