Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

Fix Typos in What Are DWNs Page #1768

Merged
merged 4 commits into from
Oct 2, 2024
Merged

Fix Typos in What Are DWNs Page #1768

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5f0416e
Fix Typos in What Are DWNs Page
Lymah123 Oct 2, 2024
67d562c
Merge branch 'main' into main
Lymah123 Oct 2, 2024
893ee58
Merge branch 'main' into main
EbonyLouis Oct 2, 2024
4ff015e
Merge branch 'main' into main
EbonyLouis Oct 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions site/docs/web5/decentralized-web-nodes/what-are-dwns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,14 @@ sidebar_position: 1

# Decentralized Web Nodes

A Decentralized Web Node (DWN) is a data storage and message relay mechanism that entities can use to locate public or private permissioned data related to a given [Decentralized Identifier(DID)](/docs/web5/decentralized-identifiers/what-are-dids).
A Decentralized Web Node (DWN) is a data storage and message relay mechanism that entities can use to locate public or private permissioned data related to a given [Decentralized Identifier (DID)](/docs/web5/decentralized-identifiers/what-are-dids).

## Personal Data Store

A DWN is a personal data store. This means you can:

- **Own your data:** You decide where to host your node. You control who has access.
- **Back up your data:** Host multiple nodes in different places, and keep them all [synced](/docs/web5/decentralized-web-nodes/sync) effortlessly. If one goes down, you have your backup.
- **Back up your data:** Host multiple nodes in different places, and keep them all [synced](/docs/web5/decentralized-web-nodes/sync) effortlessly. If one goes down, you have your backup.
- **Send and receive data:** Alice controls her DWN using her DID. Bob controls his DWN with his DID. Alice can send data to Bob just by resolving his DID.

<div role="figure" aria-labelledby="caption-1" class="figure-container">
Expand Down Expand Up @@ -41,7 +41,7 @@ The easiest way to understand this distinction is to think of permissions as act

Data types are bound to known schemas, letting applications agree on data models. This opens the door to applications working together in ways that have been much more difficult with traditional development platforms.

User-defined schemas are not validated on the payload of the record, as this sort of validation is impossible for encrypted payloads since the DWN doesn't have the private keys to decrypt. It is up the application layer if such validation is to be performed on the data.
User-defined schemas are not validated on the payload of the record, as this sort of validation is impossible for encrypted payloads since the DWN doesn't have the private keys to decrypt. It is up to the application layer if such validation is to be performed on the data.

## Messaging

Expand Down
Loading