In the solution for the pastebin/bitly system design, the write to cache flow is missing in the second diagram which refers to the scaling aspect. The cache has only a read arrow but not a write arrow. The diagram will be more intuitive if a write-through/write-back cache mechanism was indicated.

Environment

• Package version(s): @blueprintjs/core ^3.22.3
• Browser and OS versions: Mac OS X Chrome 79.0.3945.88

If possible, link to a minimal repro (fork this code sandbox):

Steps to reproduce

Spotted this while building a <ControlGroup> that contained buttons, selects, and some dividers.

`

Live CDs/USBs, netbooted PCs and in some cases discardable VMs and containers, usually have a read only base image and an overlayfs/tmpfs/cow filesystem on top of them.

There, we want some services not to run, like package manager upgrades, certain cron-like jobs etc.

It would be awesome if upstream systemd documented what "constitutes a live mode", e.g. the presence of a /run/live directory