changed step from 3 to 5 business days

Author: aldiazRH

modules/policy-incident.adoc

@@ -25,7 +25,7 @@ The general workflow of how a new incident is managed by Red Hat:
 . After the initial investigation, the incident is assigned an incident lead, who coordinates the recovery efforts.
 . The incident lead manages all communication and coordination around recovery, including any relevant notifications or support case updates.
 . The incident is recovered.
-. The incident is documented and a root cause analysis is performed within 3 business days of the incident.
+. The incident is documented and a root cause analysis is performed within 5 business days of the incident.
 . A root cause analysis (RCA) draft document is shared with the customer within 7 business days of the incident.
 
 [id="notifications_{context}"]

modules/rosa-policy-incident.adoc

@@ -25,7 +25,7 @@ When managing a new incident, Red Hat uses the following general workflow:
 . After the initial investigation, the incident is assigned an incident lead, who coordinates the recovery efforts.
 . An incident lead manages all communication and coordination around recovery, including any relevant notifications and support case updates.
 . The incident is recovered.
-. The incident is documented and a root cause analysis (RCA) is performed within 3 business days of the incident.
+. The incident is documented and a root cause analysis (RCA) is performed within 5 business days of the incident.
 . An RCA draft document will be shared with the customer within 7 business days of the incident.
 
 [id="rosa-policy-notifications_{context}"]