Should try to fix "hover" vs "hoover" mix-ups

I was just watching a financial YouTuber talk about "hovering up" something or other:

> And the third was private equity, which spent the era **hovering up** listed companies and taking them private, removing them from the market entirely.

Googling GitHub shows the reverse of that is not rare:
- When ever I use the debuger to hoover over variables to see the value it says undefiend
- **Hoovering** the mouse over a provide or requires should display the type.
- It's be great to have a tooltip shown with the name of the tab when **hoovering** over a chat tab
- I would get these errors when **hoovering** over variables or macros which are defined elsewhere

Looking for "hover up" though finds many potential false positives:
- **hovering** up/down to a line and hearing its full contents spoken you can quickly figure-out the relative position
- I want while coding with C#, show the comment of local variable when mouse **hover** up, just like coding with C++
- In the end we decided to **hover** up if we could fit in without issue
- Within Global styles you can set the Colour **Hover** up.

Start by locating Harper's existing spelling or word-confusion rules and the tests that cover similar corrections. Review the listed “hover” and “hoover” examples, including the possible false positives, and add coverage that distinguishes valid uses from mix-ups. Done means the intended errors are flagged without incorrectly changing the listed valid examples.

Written by the indexing model from the issue text.