Change read_time_pct / write_time_pct description because they are kept for backward compatibility as described in the code comment.
Motivation
Since this file serves as the basis for customer-facing documentation, any inaccuracies could lead to confusion.
In case 1901092, the customer inquired if the values for read_time_pct and write_time_pct might be incorrect.
Review checklist (to be filled by reviewers)
[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged
What does this PR do?
Change read_time_pct / write_time_pct description because they are kept for backward compatibility as described in the code comment.
Motivation
Since this file serves as the basis for customer-facing documentation, any inaccuracies could lead to confusion. In case 1901092, the customer inquired if the values for read_time_pct and write_time_pct might be incorrect.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged