Update README.md

[spoorcc]

fix links

Summary by CodeRabbit

• Documentation
  • Updated README navigation links to the new organized URL structure (tutorial, reference, how-to, explanation sections), improving access to guides and references.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1538aae8-3c1f-49c9-be1d-24b83aae008c

📥 Commits

Reviewing files that changed from the base of the PR and between 51758e3 and 6890fcc.

📒 Files selected for processing (1)

• README.md

---

Walkthrough

README.md link targets were updated to use new documentation subpaths: /explanation/..., /tutorial/..., /reference/..., and /howto/..., replacing previous top-level HTML routes.

Changes

Cohort / File(s)	Summary
Documentation Links README.md	Updated navigation and reference links to point to new documentation structure paths (e.g., alternatives and vendoring → /explanation/...; getting_started.html, commands.html, troubleshooting.html, contributing.html → /tutorial/..., /reference/..., /howto/...).

Possibly related PRs

• Cleanup documentation and make it more readable #907: Also updates repository documentation and adjusts documentation reference structures.

Suggested labels

documentation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update README.md' is vague and generic, lacking specificity about what was actually changed in the README.	Consider a more descriptive title such as 'Fix README.md documentation links' or 'Update README.md routing paths' to clearly convey the nature of the changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/readme-links

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 31-37: Update the broken README link for the Getting started
section: change the URL in the "[**Getting
started**](https://dfetch.readthedocs.io/en/latest/tutorial/getting_started.html)"
link to use the correct plural path "/tutorials/getting_started.html" so it
points to the actual documentation file (doc/tutorials/getting_started.rst).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3cf331ab-9995-4e3b-bdc9-64617147c4da

📥 Commits

Reviewing files that changed from the base of the PR and between 44ca965 and 51758e3.

📒 Files selected for processing (1)

• README.md