Skip to content

Conversation

@coodos
Copy link
Contributor

@coodos coodos commented Jan 31, 2026

Corrected typos and improved clarity in the Getting Started documentation.

Description of change

Issue Number

Type of change

  • Breaking (any change that would cause existing functionality to not work as expected)
  • New (a change which implements a new feature)
  • Update (a change which updates existing functionality)
  • Fix (a change which fixes an issue)
  • Docs (changes to the documentation)
  • Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

  • I have ensured that the CI Checks pass locally
  • I have removed any unnecessary logic
  • My code is well documented
  • I have signed my commits
  • My code follows the pattern of the application
  • I have self reviewed my code

Summary by CodeRabbit

  • Documentation
    • Updated Getting Started guide with text revisions and content restructuring.

✏️ Tip: You can customize this high-level summary in your review settings.

Corrected typos and improved clarity in the Getting Started documentation.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 31, 2026

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The Getting Started documentation file experiences widespread content degradation through typographical errors, garbled sentences, removed platform references, truncated lines, and broken formatting across sections describing core concepts, architectural data flows, and registration sequences.

Changes

Cohort / File(s) Summary
Documentation Corruption
docs/docs/Getting Started/getting-started.md
Multiple sections contain altered wording, typographical errors ("datprotocol"), corrupted sentences with misplaced tokens, truncated content, removed platform list items and data flow steps, and malformed formatting in code blocks and narrative text.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Possibly related PRs

Poem

🐰 A document once pristine and bright,
Now scattered with tokens and broken-up might,
The platforms have vanished, the steps gone astray,
"datprotocol" whispers where protocols should stay!
Let's hop back to fixes, restore what we've lost, 🔧✨

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch coodos-patch-3

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

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

# Getting Started with W3DS

Welcome to **W3DS (Web 3.0 Data Spaces)** — a decentralized data synchronization protocol that puts users in control of their data. For definitions of key terms (eVault, W3ID, MetaState, Post-Platform, etc.), see the [Glossary](/docs/W3DS%20Basics/glossary).
Welcome to **W3DS (Web 3.0 Data Spaces)** — a decentralized datprotocol that puts users in control of their data. For definitions of key terms (eVault, W3ID, MetaState, Post-Platform, etc.), see the [Glossary](/docs/W3DS%20Basics/glossary).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix the typo where it says "datprotocol"

## Core Concept

The fundamental principle of W3DS is simple: **Users, groups, and objects own their own eVaults**. All data about a person, group, or object is stored in their eVault, and platforms act as frontends that display and interact with this data, while also serving as caches and aggregators for improved performance and user experience.
The fundamental principle of W3DS is simple: **Users, groups, and objects owproved performance and user experience.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something message


1. User A posts "Hello, world!" on Blabsy
2. Blabsy's Web3 Adapter syncs the post to User A's eVault
3. User A's eVault stores the post and notifies all registered platforms
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont delete this

@coodos coodos closed this Jan 31, 2026
@coodos coodos deleted the coodos-patch-3 branch January 31, 2026 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants