ui: one way to open the events page, and stale wording after the pane's removal

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

src/ui.cpp

@@ -4187,7 +4187,7 @@ gboolean tick(gpointer user) {
     next_channels = now_c + G_TIME_SPAN_SECOND;
     app->last_channels_meas = now_c;
     // The cache's own question, on the same cadence as the channel dump: a directory read per second,
-    // and the button's availability re-decided only when the answer changed.
+    // and the dock block's and the events page's availability re-decided only when the answer changed.
     if (app->event_store != nullptr) {
       const bool cached = !app->event_store->list().empty();
       if (cached != app->events_cached) {
@@ -5708,8 +5708,7 @@ void report_events_availability(App& a, const char* what) {
 }
 
 
-/// Walks the whole event-cache loop the way a user does: trigger mode on (the real toggle, which is
-/// what reveals the pane), a latch recorded automatically, the cache listed, the newest event
+/// Walks the whole event-cache loop the way a user does: trigger mode on (the real toggle), a latch recorded automatically, the cache listed, the newest event
 /// replayed through the loader `--open` uses, and *Live* taken back. What it reports is what each
 /// step must be able to do -- a cache nothing can replay is a directory of files, and a replay with
 /// no way back is a one-way door.