with something more customer oriented:
Or even better - doing globalization:
These changes are not expected to cause any non-UI regressions, right?
Consider the case where we originally had this
And now the documentation guys kindly asked to change to this:
A mismatch between the number of tokens in the string to the actual provided parameters may result in this error:
Conclusion: Proofing/Localizing always require running all your tests and doing a regression cycle.