It’s unclear where doc bugs are supposed to be reported (oh please why can’t I do that from the doc pages?).
Anyhow Interactive Data Exploration with Altair - OmniSci Docs has multiple problems.
There is a section titled “Adding Interactivity” which has nothing to do with “Interactivity” or adding it. It’s about basic connection to an OmniSci database. Why not just call it that… “tool tips” at the end are just a silly example of “interactivity”. Get people started with the basic charts (without issues below) is much more important, and then maybe add more chart type examples and then futz with “interactivity”.
And the first two code fragments in that section don’t match the surrounding text. Like “Here is a chart definition using Altair” is not preceding a chart definition, it’s preceding what looks like an unintended near duplicate of the previous code example… except the second one has a typo, if the connection object is meant to be omnisci_cli then it needs to also use t = omnisci_cli.table(). I suspect somebody is just copying and pasting code samples without testing they work, come on, please automate testing of code samples in docs.
Maybe it would be better to put doc effort into doc and samples in Jupyter notebooks.