Merge pull request #84859 from snarayan-redhat/OSDOCS-11878_8to1

OSDOCS#11878: Check interval of vSphere Problem Detector Operator changed to 1

Author: snarayan-redhat

modules/vsphere-problem-detector-about.adoc

@@ -14,11 +14,11 @@ The Operator runs in the `openshift-cluster-storage-operator` namespace and is s
 
 The Operator runs the checks according to the following schedule:
 
-* The checks run every 8 hours.
+* The checks run every hour.
 
 * If any check fails, the Operator runs the checks again in intervals of 1 minute, 2 minutes, 4, 8, and so on. The Operator doubles the interval up to a maximum interval of 8 hours.
 
-* When all checks pass, the schedule returns to an 8 hour interval.
+* When all checks pass, the schedule returns to an hour interval.
 
 The Operator increases the frequency of the checks after a failure so that the Operator can report success quickly after the failure condition is remedied. You can run the Operator manually for immediate troubleshooting information.
 

modules/vsphere-problem-detector-running.adoc

@@ -10,7 +10,7 @@
 
 You can override the schedule for running the {operator-name} checks and run the checks immediately.
 
-The {operator-name} automatically runs the checks every 8 hours. However, when the Operator starts, it runs the checks immediately. The Operator is started by the Cluster Storage Operator when the Cluster Storage Operator starts and determines that the cluster is running on vSphere. To run the checks immediately, you can scale the {operator-name} to `0` and back to `1` so that it restarts the {operator-name}.
+The {operator-name} automatically runs the checks every hour. However, when the Operator starts, it runs the checks immediately. The Operator is started by the Cluster Storage Operator when the Cluster Storage Operator starts and determines that the cluster is running on vSphere. To run the checks immediately, you can scale the {operator-name} to `0` and back to `1` so that it restarts the {operator-name}.
 
 .Prerequisites