From 6f2e9fec20e53cbd28c31e64a2a5b86742c7d8d2 Mon Sep 17 00:00:00 2001
From: Andrew <84722778+abottoms-coder@users.noreply.github.com>
Date: Thu, 3 Feb 2022 13:47:52 -0500
Subject: [PATCH] Update 009-git-workflow.md

---
 .../Architecture-Decision-Record/009-git-workflow.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Technical-Documentation/Architecture-Decision-Record/009-git-workflow.md b/docs/Technical-Documentation/Architecture-Decision-Record/009-git-workflow.md
index 3c42856b26..36666b9ec2 100644
--- a/docs/Technical-Documentation/Architecture-Decision-Record/009-git-workflow.md
+++ b/docs/Technical-Documentation/Architecture-Decision-Record/009-git-workflow.md
@@ -50,7 +50,7 @@ The proposed workflow below provides a remedy to these issues, as well as many o
 
 5. Assigned Raft reviewer(s) perform the review and/or requests changes.
     * For project management, research, and design work, review is conducted async.
-    * For development work, author is expected to schedule a [tabletop meeting]() at least 48 hours after `raft review` label added. 
+    * For development work, author is expected to schedule a [tabletop meeting](https://github.com/raft-tech/TANF-app/docs/How-We-Work/Developer-Tabletops.md) at least 48 hours after `raft review` label added. 
     * When changes are requested, the changes are made by the author.
     * When satisfied, the reviewer(s) confirm that ACs are met,  `approve` the PR, remove `raft review` and add `QASP review` labels.
         * See exceptions in [Notes](https://github.com/raft-tech/TANF-app/blob/dffd79adf7a5ae87cf1a93c8adf655c76cf45089/docs/Architecture%20Decision%20Record/009-git-workflow.md#notes) section