But the blog post states: "a calculation error that only manifested in scenarios where the actual ping was significantly lower than the target latency".
Sadly, my guess is that they are transparently lying about that. Since they apply the lag half on the client and half on the server, their lag compensation would have been off by a factor of 2x (or a factor of 100% from a relative perspective) and so they might be just claiming that a 100% error isn't very large when the total lag difference is small. "Yes we were supposed to add 2ms and we added 4ms instead, but at the end we were still only wrong by 2ms (in the other direction) which is not a big deal."
But the blog post states: "a calculation error that only manifested in scenarios where the actual ping was significantly lower than the target latency".