Hey Frank...
I'm afraid this is not going to be a very satisfying answer, but here it is anyway.
As I think you know, we use a tool to create our documentation. All of our source material is in Microsoft Word, and to create the docs I say to our tool "process items1,2,3..." There are a bunch of rules and specs and options involved, of course, and at the end of the process out pops the document set which I post and you see.
Not surprisingly, "search" is one of the features of the tool that is handled without any input at all from the user (me). Therefore we/I have no control of it whatsoever.
I've noticed some odd behavior by "search" over the years, and your example is certainly an instance of that. But not only can I not do anything about it, I'm having trouble even figuring out what it's doing! I think what's going on is (a) Search is only looking for whole words, and (b) it decided that "no row" was the closest match to your first term so it searched for that (and found it), and (c) but didn't highlight the results.
Despite rather obsessively striving for perfection with some aspects of the documentation, there are other aspects of it where we've decided to simply live with "good enough." Search is definitely one of those. I believe the folks who make the tool we're using wrote their own search engine, and it leaves quite a bit to be desired. On the other hand, it seems to work well enough in most cases.
So how's that for unsatisfying?!!!