Fix Typos in What Are DWNs Page (#1768)

Co-authored-by: Ebony Louis <55366651+EbonyLouis@users.noreply.github.com>

site/docs/web5/decentralized-web-nodes/what-are-dwns.md

@@ -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">
@@ -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