From 6c91c029e8d17bb3412299831d1034c474134368 Mon Sep 17 00:00:00 2001
From: nick-soutouras <123987365+nick-soutouras@users.noreply.github.com>
Date: Thu, 25 Jul 2024 20:28:10 -0600
Subject: [PATCH] Update incident-response-checklist.md

Adding embedded links in two places in the Messenger section.
---
 _articles/incident-response-checklist.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_articles/incident-response-checklist.md b/_articles/incident-response-checklist.md
index ead959fe..1891e434 100644
--- a/_articles/incident-response-checklist.md
+++ b/_articles/incident-response-checklist.md
@@ -128,12 +128,12 @@ These additional roles are external to, and highly engaged with, responders in t
 ## Messenger
 ### Initiate
 1. For public impacting incidents, post initial incident notice following StatusPage Process
-1. Situation Report (sitrep) ticket created in identity-security-private repo
+1. Situation Report (sitrep) ticket created in [identity-security-private](https://github.com/18F/identity-security-private) repo
 1. Create email notice to GSA IR, ISSM, ISSO using the [Incident Response - GSA IR Email Template](https://docs.google.com/document/u/0/d/16h4gDq9JeW8JBhBDswSvoGRWx6qQvX_4spyEZVbjlcA/edit)
 1. Once the situation is assessed, ping @login-comms-oncall with brief triage summary
 
 ### Assess
-- Check the Incident Comms Playbook every 30 minutes
+- Check the [Incident Comms Playbook](https://docs.google.com/document/d/1kG7LXaEThJFJfCVP3jnimEvqbHKlFNvJ_PokZkpu1K8/edit#heading=h.vjtsg6mj5w6c) every 30 minutes
 - Update the platform [StatusPage]({% link _articles/statuspage-process.md %}#update) (if an incident is posted) every 30 minutes
 
 ### Contain