Fix markdown

[lucacome]

Fixes errors about markdown

Summary by CodeRabbit

• Documentation
  • Improved link clarity in the Docker section of the README by replacing generic “here” with descriptive “examples”; link destination unchanged.
  • Updated Tutorial text to explicitly reference the example source path, enhancing readability without altering navigation.
  • Refined Ubuntu installation note in the example by replacing a vague “here” link with a clearly labeled “instructions” link; target unchanged.
  • Overall: clearer wording and more descriptive links for better usability.

[coderabbitai]

Walkthrough

Documentation-only changes updating hyperlink anchor text in three Markdown files. Link targets remain unchanged. No code, configuration, or behavior modifications.

Changes

Cohort / File(s)	Summary of Changes
Documentation link text updates README.md, doc/Tutorial.md, example/trivial/ubuntu-x86_64/README.md	Updated visible link text/phrasing; retained original URLs. No functional or navigational changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/markdown

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 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/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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 (2)

doc/Tutorial.md (1)

187-187: Nit: make the anchor text mirror the path for quicker scanning

The sentence reads fine; using the directory name in the anchor can improve discoverability.

-The full source code can be viewed in the [example](../example/zoo).
+The full source code is available in [example/zoo](../example/zoo).

example/trivial/ubuntu-x86_64/README.md (1)

6-6: Nit: minor grammar/readability tweak

Optional rewording for clarity and consistency with product naming.

-NGINX-1.14.0 is installed for Ubuntu following the [instructions](https://www.nginx.com/resources/wiki/start/topics/tutorials/install/#official-debian-ubuntu-packages).
+Install NGINX 1.14.0 on Ubuntu by following the official Debian/Ubuntu package [instructions](https://www.nginx.com/resources/wiki/start/topics/tutorials/install/#official-debian-ubuntu-packages).

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ebe8b22 and 779f374.

📒 Files selected for processing (3)

• README.md (1 hunks)
• doc/Tutorial.md (1 hunks)
• example/trivial/ubuntu-x86_64/README.md (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). (4)

• GitHub Check: Build Docker Image (alpine)
• GitHub Check: Build Docker Image (debian)
• GitHub Check: Build Docker Image
• GitHub Check: Analyze (go)

🔇 Additional comments (2)

README.md (2)

113-113: LGTM: clearer anchor text for the Docker examples

Changing "here" to "examples" improves clarity, while keeping the relative link intact.

---

113-113: Quick link check — README examples link resolves

I verified README.md: the link on line 113 ("See examples of how to use it.") points to repo-root example/ (directory exists), and the README also links to example/trivial/ubuntu-x86_64 (exists). No broken relative links found for these locations.

• README.md:26 — See example/trivial/ubuntu-x86_64
• README.md:113 — See examples