fix: repair broken image URLs

[ccamel]

Self explanatory.

Summary by CodeRabbit

• Documentation
  • Updated image source paths in the "Hierarchy of Norms" and "The Power of Ontologies" documents to reflect a new file organization.
  • Enhanced clarity and readability in the "The Power of Ontologies" document while maintaining core content.
  • Revised image sources in the "What Are Ontologies" document without altering any text or structure.

[coderabbitai]

Walkthrough

This pull request includes updates to several markdown documentation files within the Axone project. The primary focus of the changes is the modification of image source paths, reflecting a reorganization of the file structure. Additionally, the document the-power-of-ontologies.md has been enhanced for clarity, particularly in the introduction and benefits sections, while retaining the core content. No other structural changes or alterations to text content were made across the documents.

Changes

File Path	Change Summary
docs/architecture/governance/hierarchy-of-norms.md	Updated image source path from /img/content/architecture/governance-hierarchy-of-norms.webp to /img/content/technical-documentation/governance-hierarchy-of-norms.webp.
docs/architecture/ontology/the-power-of-ontologies.md	Enhanced clarity in the introduction and benefits sections; updated image source from /img/content/architecture/semantic-stack.webp to /img/content/technical-documentation/semantic-stack.webp.
docs/architecture/ontology/what-are-ontologies.md	Updated image sources for "Ontology equation" and "Ontology construction process" from /img/content/architecture/ontology_equation.webp and /img/content/architecture/ontology-construction-process.webp to /img/content/technical-documentation/ontology_equation.webp and /img/content/technical-documentation/ontology-construction-process.webp, respectively.

Possibly related PRs

• Style/theme rebranding #585: The changes in this PR involve updates to image sources, similar to the main PR's modification of an image source path in documentation, indicating a related focus on visual content organization.

Suggested reviewers

• amimart

Poem

In the garden of norms, where images bloom,
Paths were shifted, making room.
Ontologies dance, clarity in sight,
With every change, the docs feel right.
A hop, a skip, through technical lanes,
Our knowledge grows, as wisdom gains! 🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6c9163a and 5ad0c95.

📒 Files selected for processing (3)

• docs/architecture/governance/hierarchy-of-norms.md (1 hunks)
• docs/architecture/ontology/the-power-of-ontologies.md (1 hunks)
• docs/architecture/ontology/what-are-ontologies.md (2 hunks)

✅ Files skipped from review due to trivial changes (3)

• docs/architecture/governance/hierarchy-of-norms.md
• docs/architecture/ontology/the-power-of-ontologies.md
• docs/architecture/ontology/what-are-ontologies.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>, 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 2:13pm

[bot-anik]

Device	URL
desktop	http://localhost:3000/

Device	URL
mobile	http://localhost:3000/

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

[AnjaMis]

Good catch, thank you!