So I’m new to this whole bug thing. Just trying to help.
It seems that after the letter ‘v’, and only in Arial, there is too much space. I’ve attached a snip as an example. The font size is 10 in this photo. I tried checking in other word processing software and I didn’t see the gap that is here.
I have the latest beta version, release candidate 5.
Just tested on mine - unable to reproduce this problem on Windows 10, high DPI.
Since I use Arial for all my texts I had to check this issue myself. 
I can confirm that it also happens on my computer (Windows 7 64-bit).
It initially didn’t happen with my default zoom level, but I noticed that LHunt’s picture is relatively small. So when I decreased the zoom I also noticed a little space behind ‘v’.
Here’s a video of that (.mp4).
It seems to happen on 100% zoom, but goes away at 110% zoom level. And the issue is neither there at 90% zoom level.
I wonder if the problem could be that your File | Options settings aren’t up-to-date with the careful fixes for such problems introduced some months ago?
As part of this thorough work by Tiho and Lee, there were intelligent Default settings provided, both labelled for Font Hinting, and those do seem to work.
You can refer to the screenshot below. If your settings are already both say Default, still there could have been some interaction with old settings meaning these didn’t get properly updated.
So if setting Default fixes this for you, fine. If not, I’d set both of them to the alternatevalue of No Hinting.
Then completely exit Scrivener, any and all windows.
Then start Scrivener again, and now set both to Default.
Then, once more, completely exit Scrivener, all windows, and then start it up again.
If you still see the problem after this ritual, then Tiho likely wants to know…!
Good fortune,
Clive
Ok, so I can’t tell if narrsd is being condescending in this post or not but I’m gonna hope not. Either way, this worked. I would still imagine that Tiho would want to know since it seems strange to me that I would have to use such a setting that I never would have been aware of otherwise. Either way, up to you. Just wanting to post my experience that it seems others have too.
Thanks.
The problem is that with some monitors and some computers, it acts just fine. No additional spaces, no issues. With others, it shows up in every font. Thus, the setting, as the bug’s appearance seems unpredictable. Also, this may be a limitation in the programming framework being used; I seem to recall a discussion about that.
In my experience, narrsd is not likely to be condescending – merely thorough and helpful.
Different fonts, different display resolutions, combined with different Windows flavors, and Windows OS settings (like Clear Type) result in different rendering of the fonts with the Qt font engine. Because of this we have added the font hinting options. The defaults will probably work for most, but not perfect for all combinations. Glad that adjusting the font hinting worked!