Curator is not used anymore as the main tool for log retention

Document URL:
https://docs.openshift.com/container-platform/4.7/logging/config/cluster-logging-curator.html
Section Number and Name:
First paragraph.

Describe the issue:
The first sentence is very misleading. It gives the understanding that Curator still the main tool being used in the stack when actually are the rollover and delete cronjobs specially from 4.5 and later.

~~~
In OpenShift Container Platform 4.7, log curation is performed by Elasticsearch Curator, based on a retention policy that you define.
The Elasticsearch Curator tool removes Elasticsearch indices that use the data model prior to OpenShift Container Platform 4.5. You can modify the Curator index retention policy for your old data.
~~~

Suggestions for improvement:

~~~
In OpenShift Container Platform 4.7, log curation is performed by ElasticSearch `rollover` and `delete` cronjobs that can be set in [retentionPolicy](
https://docs.openshift.com/container-platform/4.7/logging/config/cluster-logging-log-store.html#cluster-logging-elasticsearch-retention_cluster-logging-store
).

Elasticsearch Curator will be deprecated in future versions and if the cluster was deployed on RHOCP 4.5 version, Elasticsearch Curator is not required.
The Elasticsearch Curator tool removes Elasticsearch indices that use the data model prior to OpenShift Container Platform 4.5. You can modify the Curator index retention policy for your old data.
~~~

Additional information:
The same modification can be applied to OCP 4.5 and 4.6