git.iko.soy/urbit.org
on master help sign in
landscape typos
commit372dc72de4e0df54b47e9ae8504fb854365738fd authordrbeefsupreme <drbeefsupreme@discordja.net> dateMon 8 Mar 2021, 17:20 (6 years ago) parentb929040
2 files changed+2−2
compare with master
unifiedsplit
landscape/_index.md+1−1 landscape/arch.md+1−1
landscape/_index.md+1−1
@@ -8,6 +8,6 @@ template = "sections/docs/chapters.html"
88
99## [Landscape Architecture](@/docs/landscape/arch.md)
1010
11−An overview of how Landscape, our flagsip client, is structured.
11+An overview of how Landscape, our flagship client, is structured.
1212
1313## [API Reference](@/docs/landscape/apiref/_index.md)
landscape/arch.md+1−1
@@ -14,6 +14,6 @@ Stores are the first of the two gall models to form this architecture. A store i
1414
1515Hooks are the second gall application used in this architecture and are not always present. Hooks are used for inter-app communication. This allows a separation of access control concerns and a division between those things which are able to be done by a store itself and those done by another gall application. `graph-store` in particular has two hooks `graph-pull-hook` for outgoing requests, and `graph-push-hook` for incoming requests.
1616
17−## Thread
17+## Threads
1818
1919Threads are used when you want to have a series of transactions on a store where the order of those transactions matters. No guarantees are made about the order in which individual requests to a gall applications are processed; threads were introduced to address this. Threads do not maintain their own state while inactive and are instead run only upon request. A good example is `ted/graph/create`