docs(examples): avoid low-level workout wording
Keep the workout exemplar docs aligned with canonical example guidance by describing persisted truth without teaching low-level update payload terminology. req: examples/003 req: examples/005 req: local/001
This commit is contained in:
@@ -3,7 +3,7 @@
|
||||
This is the phone-first local-first product exemplar for hemx. It shows a
|
||||
single useful loop: next action shown, user input accepted, a local command
|
||||
recorded, a domain event projected, hemx UI updated, and the result exported or
|
||||
replayed without storing DOM patches or `EffectBatch` as truth. req: examples/001
|
||||
replayed without storing DOM patches or UI update payloads as truth. req: examples/001
|
||||
req: local/001 req: local/003 req: local/004
|
||||
|
||||
## Run
|
||||
|
||||
Reference in New Issue
Block a user