Skip to content
This repository was archived by the owner on Jan 31, 2024. It is now read-only.

Commit 6330224

Browse files
hpk42r10s
andcommitted
Apply suggestions from code review
Co-authored-by: bjoern <[email protected]>
1 parent 8c214f4 commit 6330224

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/intro.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Instead of being hosted on a central always-online HTTP server,
88
webxdc apps are stored with the host messenger by attaching a container file to a chat message.
99
Instead of using the HTTP protocol for querying a central server to obtain authoritative application state,
1010
webxdc apps send and receive messages via the messenger's [JavaScript API]
11-
which allows to send and receive "application updates" between devices particpating in a chat.
11+
which allows to send and receive "application updates" between devices participating in a chat.
1212
App developers do not need to implement message transport, user authentication,
1313
discovery or bootstrapping mechanisms, and they do not need to implement end-to-end encryption either.
1414
All Authentication, identity management, social discovery and message transport
@@ -18,10 +18,10 @@ capabilities of the hosting messenger.
1818

1919
Messengers run webxdc container files in network-isolated webviews that can not perform any DNS or HTTP queries.
2020
Webxdc apps can only cause network messages by calling the [`sendUpdate`](./spec/sendUpdate.html)
21-
and [`setUpdateListener`](./spec/setUpdateListener.html) Javasript APIs,
21+
and [`setUpdateListener`](./spec/setUpdateListener.html) JavaScript APIs,
2222
implemented by the hosting messenger.
2323
In ["Bringing E2E privacy to the web"](https://delta.chat/en/2023-05-22-webxdc-security)
24-
Delta Chat developers described the unqiue security-audited privacy guarantees of webxdc
24+
Delta Chat developers described the unique security-audited privacy guarantees of webxdc
2525
not found with any other web container technology or [specification](./spec/index.html).
2626

2727
Waving central registries and app store dependencies "good bye!",
@@ -50,7 +50,7 @@ The [Shared web application state] chapter
5050
provides useful theoretical and practical background for writing robust offline-first web apps
5151
without requiring a central online authority acting as the "source of truth".
5252
Even if you don't study the topic in depth, reading [Shared web application state]
53-
introduces you to the terminology and neccessary considerations
53+
introduces you to the terminology and necessary considerations
5454
for any P2P system, with a particular eye on webxdc.
5555

5656

0 commit comments

Comments
 (0)