The change was to the "trains batches of units faster" part so I think the string can stay.
The change here was just a temporary fix until we decide about D904 (I still don't know).
I don't disagree, but "nearby" isn't used by any heroes so far, and e.g. Hannibal uses "all" even though he has a range. Maybe a clean-up can be done after a23 so our translators aren't swamped by little changes.
It is not because something else is wrong that we should not fix that. And using "all" for a range aura is certainly misleading and just lying, so should be fixed.
And why waiting for after a23, we are not yet in feature freeze! then we'll have i guess 2 or 3 weeks before going to commit freeze, which will last i guess at least one week and then only we'll go to string freeze. So already preventing us to fix strings one month before string freeze looks really inefficient to me.
Agree with mimo. (Firstly wrong strings must be fixed either way, preferably sooner rather than later. Secondly transifex users, even on the webinterface see strings that match the previous translation sorted by similarity, so they can copy & paste the old translation and just change one or two words. A handful of strings is not much work at all. Also if one is quick with changing the strings (same day), the transifex users won't see the first version of the string.)