Skip to content

Commit e40f9dd

Browse files
committed
docs: clarify event engine screenshot and behaviour description
1 parent 619fbba commit e40f9dd

File tree

1 file changed

+3
-3
lines changed
  • src/content/posts/event-driven-golang

1 file changed

+3
-3
lines changed

src/content/posts/event-driven-golang/index.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,18 +63,18 @@ Then open the UI:
6363
open http://localhost:8080
6464
```
6565

66-
You will see a small web page that lists events, their current state, and how they change over time.
66+
You will see a small web page that lists events and their current state. It looks like this:
6767

6868
![Event engine UI](./meta.jpg)
6969

70-
The UI connects to the server with server-sent events and WebSocket. It shows you:
70+
When the engine is running against a real database and broker, the UI connects over server-sent events and WebSocket and shows you:
7171

7272
- when a new event is created
7373
- when it is picked up for work
7474
- when it succeeds or fails
7575
- when it is retried or expires
7676

77-
This turns “event-driven architecture” from a diagram into something you can watch.
77+
That turns “event-driven architecture” from a diagram into something you can watch.
7878

7979
## The main pieces in plain language
8080

0 commit comments

Comments
 (0)