For these types of visual callouts, like [!TIP] or [!NOTE], you might just use the unicode versions which do not require special markdown support, like one of 💡,👉, ☞, 📝.

The advantage with these versions is that it displays the content as a nice aside that is visually separate from the main flow:

The unicode versions will have the icon, but won't demarcate the section as well. In other markdown renderers, it shows up a a standard quotation block, which still manages to demarcate the content even though it doesn't have the icon or the coloring:

Given that most people will be reading this on Github anyway I'd prefer to leave it as is for the time being.

The connection with "threads" feels a bit tenuous here. Can we make a more obvious connection?

I updated the wording like this:

// Views of an OnDiskGraphIndex with inline or separated vectors can be used as RAVVs!
// In multi-threaded scenarios you should have one searcher per thread
// and extract a view for each thread from the associated searcher.

Is that the kind of thing you meant?

As a side note, we may want to start using exec:java here. The trade-offs are meaningful for new users. The main one being: with exec:exec you have full process isolation and you can run anything but with exec:java you get to carry the classpath and process hierarchy with you which simplifies debugging and digging deeper. This can be a separate discussion, but wanted to plant a seed here.

The main problem I see with exec:java is that you can't pre-configure VM options like --add-modules=jdk.incubator.vector in the pom.xml. This has to be done during runtime while starting maven. For these tutorials I think the better approach is to stick with exec:exec since

• (a) It gets rid of the warnings about the vector API not being enabled
• (b) Users can go check the "recommended" config options in the pom.xml