docs: update arch view

README.md

@@ -204,20 +204,12 @@ In turn when the `views` are rendered, the `user` can interact with elements by
 clicking on them, triggering `actions` which then flow back into the
 application logic. This is the _unidirectional_ architecture of `choo`.
 ```txt
- ┌───────────────────────────┐     ┌────────┐
+ ┌─────────────────┐
- │    ┌─────────────────┐    │     │  User  │
+ │  Subscriptions ─┤     User ───┐
- ├────│  Subscriptions  │    │     └────────┘
+ └─ Effects  ◀─────┤             ▼
- │    ├─────────────────┤    │          │
+ ┌─ Reducers ◀─────┴──Actions── DOM ◀┐
- └────│     Effects     │◀───┤          ▼
+ │                                   │
-      ├─────────────────┤  Actions ┌────────┐
+ └▶ Router ─────State ───▶ Views ────┘
-      │    Reducers     │◀───┴─────│  DOM   │
-    Models──────────────┘          └────────┘
-               │                        ▲
-             State                   DOM│tree
-               ▼                        │
-          ┌────────┐               ┌────────┐
-          │ Router │─────State ───▶│ Views  │
-          └────────┘               └────────┘
 ```
 - __user:__ 🙆
 - __DOM:__ the [Document Object Model][dom] is what is currently displayed in