Description of problem:

Doc about ETCD metrics, in section of "Validating the hardware for etcd", there is description:

The output reports whether the disk is fast enough to host etcd by comparing the 99th percentile of the fsync metric captured from the run to see if it is less than 10 ms. ....

as feedback from user, OCP cluster still could work well when the metric value is beyond 10ms, but this description bring big concern to user, after analysis, we recommend user to reference to ETCD alert(alert: etcdHighFsyncDurations, etcdHighCommitDurations) in parallel.
So we suggest to update the description like below to erase user's confuse:

The output reports whether the disk is fast enough to host etcd by comparing the 99th percentile of the fsync metric captured from the run to see if it is less than 10 ms(the recommended values of the metrics, review also the etcd alert, such as: etcdHighFsyncDurations, etcdHighCommitDuration). ....

https://docs.openshift.com/container-platform/4.17/scalability_and_performance/recommended-performance-scale-practices/recommended-etcd-practices.html,

Version-Release number of selected component (if applicable):

OCP 4.17
How reproducible:

always

Steps to Reproduce:
1.
2.
3.

Actual results:

As description
Expected results:

As description
Additional info: