@@ -8,7 +8,7 @@ Instead of being hosted on a central always-online HTTP server,
8
8
webxdc apps are stored with the host messenger by attaching a container file to a chat message.
9
9
Instead of using the HTTP protocol for querying a central server to obtain authoritative application state,
10
10
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.
12
12
App developers do not need to implement message transport, user authentication,
13
13
discovery or bootstrapping mechanisms, and they do not need to implement end-to-end encryption either.
14
14
All Authentication, identity management, social discovery and message transport
@@ -18,10 +18,10 @@ capabilities of the hosting messenger.
18
18
19
19
Messengers run webxdc container files in network-isolated webviews that can not perform any DNS or HTTP queries.
20
20
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,
22
22
implemented by the hosting messenger.
23
23
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
25
25
not found with any other web container technology or [ specification] ( ./spec/index.html ) .
26
26
27
27
Waving central registries and app store dependencies "good bye!",
@@ -50,7 +50,7 @@ The [Shared web application state] chapter
50
50
provides useful theoretical and practical background for writing robust offline-first web apps
51
51
without requiring a central online authority acting as the "source of truth".
52
52
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
54
54
for any P2P system, with a particular eye on webxdc.
55
55
56
56
0 commit comments