Update mark metrics recommendations.

docs/metrics/prometheus.md

@@ -48,9 +48,9 @@ Vouch will attest for accounts that are either `active_ongoing` or `active_exiti
 
 Vouch uses marks to show the point in time within a slot at which it completes its various operations.  The mark is made after the operation has submitted any results of its work to its beacon nodes, and so can be used to confirm that Vouch is acting in a timely fashion.  Each mark is a histogram from 0 to 12 seconds, in 0.1 second increments.  The marks are as follows:
 
-  - `vouch_attestation_mark_seconds` is the time in the slot at which the attestation(s) for the slot have been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 2 second mark.  Any significant number of these after the 3 second mark suggests that part of the validating infrastructure may be slow, and should be investigated
+  - `vouch_attestation_mark_seconds` is the time in the slot at which the attestation(s) for the slot have been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 6 second mark.  Any significant number of these after the 7 second mark suggests that part of the validating infrastructure may be slow, and should be investigated
   - `vouch_beaconblockproposal_mark_seconds` is the time in the slot at which the block for the slot has been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 1 second mark.  Any significant number of these after the 2 second mark suggests that part of the validating infrastructure may be slow, and should be investigated
-  - `vouch_synccommitteemessage_mark_seconds` is the time in the slot at which the sync committee message(s) for the slot has been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 2 second mark.  Any significant number of these after the 2 second mark suggests that part of the validating infrastructure may be slow, and should be investigated
+  - `vouch_synccommitteemessage_mark_seconds` is the time in the slot at which the sync committee message(s) for the slot has been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 6 second mark.  Any significant number of these after the 7 second mark suggests that part of the validating infrastructure may be slow, and should be investigated
   - `vouch_attestationaggregation_mark_seconds` is the time in the slot at which attestation aggregation message(s) for the slot has been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 9 second mark.  Any significant number of these after the 10 second mark suggests that part of the validating infrastructure may be slow, and should be investigated.  It would also be expected that all of these message would be after the 8 second mark.  Any number of these before the 8 second mark suggests a problem with system time, and should be investigated
   - `vouch_synccommitteeaggregation_mark_seconds` is the time in the slot at which sync committee aggregation message(s) for the slot has been submitted to the beacon nodes.  In a healthy network it would be expected that the majority of these would be before the 9 second mark.  Any significant number of these after the 10 second mark suggests that part of the validating infrastructure may be slow, and should be investigated.  It would also be expected that all of these message would be after the 8 second mark.  Any number of these before the 8 second mark suggests a problem with system time, and should be investigated