From 0e979ee33496d1f2008d06e0ef02772bf0cb28ea Mon Sep 17 00:00:00 2001 From: Dale Ribeiro Date: Thu, 19 Feb 2026 11:33:28 -0500 Subject: [PATCH] Fix typo in assignment instructions for incident response (#40064) --- handbook/engineering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 16418f3bb2..2d92b3548d 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -159,7 +159,7 @@ Fleet responds to all P0 incidents by initiating our incident response process: 1. Create a new [incident response issue](https://github.com/fleetdm/confidential/issues/new?template=incident-response.md) in our confidential repo. 2. Edit the issue template to reflect the details of the incident. -3. Assign to the bcurrent usiness hours or after hours on-call engineer (based on time of the incident) and the current infrastrucure on-call engineer. +3. Assign to the current business hours or after hours on-call engineer (based on time of the incident) and the current infrastrucure on-call engineer. 4. Complete the steps listed based on the type of incident. Mitigating the outage may require writing and merging code. The current infrastructure on-call engineer is first line for all reviews and QA required to deploy a hot-fix. If additional code review or engineering support is needed, the responding engineer should escalate to their manager.