docs: npm run format

[SteveDala]

Description

It doesn't look like npm run format has been done in some time. This PR fixes that.

Type of change

• Documentation (update or new)

How Has This Been Tested?

No test required, this was simply a run of npm run format

Testing Checklist

• Have run npm run format
• Have run npm run build
• Have run npm run dev and/or npm run preview, using:
  • Chrome
  • Safari
  • Firefox

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have requested a review from the documentation team on the Pull Request

[netlify]

✅ Deploy Preview for thoth-tech ready!

Name	Link
🔨 Latest commit	fb2dd16
🔍 Latest deploy log	https://app.netlify.com/projects/thoth-tech/deploys/6975d0dc1c6c9d00085b9eb5
😎 Deploy Preview	https://deploy-preview-164--thoth-tech.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ishika021]

Upon reviewing the Pull Request, it appears to be mainly a result of formatting (run npm run format) for a large number of markdown documentation pages. In addition, there is one minor change made to the CONTRIBUTING.md documentation file. The changes made to the markdown documentation will likely all relate to automated reformatting and not changes made to the structure or functionality of content.

What I've done and what looks good:

• The formatting has maintained consistency across all affected md/mdx files. Spacing, headings, lists, layout, etc., are standardised throughout.
• Clear scope: there is a single commit related to formatting, making a review and reversion easier if required.

As a suggestion before merging the PR:

• Check that the documentation site builds correctly following the formatting changes (e.g., run npm run build), with no associated errors (MDX parsing).
• Quick check for accidental regressions in markdown: nested lists, tables, code fences, and internal link/anchor references.

Minor suggestion:

Consider mentioning in the PR description that these formatting changes (which were created using a formatter tool) were all created during a single run of the formatter, so people do not look for semantic changes while reviewing.

Overall, I believe this is a safe and clean merge to make.

[SteveDala]

@ishika021 if there's no fixes to be applied, please change your review to an "approving review":