From 9af4a69d3ef9c9786678d6246dcdfd13fabc2389 Mon Sep 17 00:00:00 2001
From: Roger Dingledine <arma@torproject.org>
Date: Tue, 10 Sep 2019 08:50:50 -0400
Subject: [PATCH] include a close-paren

---
 tsa/howto/incident-response.mdwn | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tsa/howto/incident-response.mdwn b/tsa/howto/incident-response.mdwn
index d4baab25..99526fb0 100644
--- a/tsa/howto/incident-response.mdwn
+++ b/tsa/howto/incident-response.mdwn
@@ -18,8 +18,9 @@ If it does respond, you can try to diagnose the issue by looking at
 
 If it does *not* respond, you should see if it's a virtual machine,
 and in this case, which server is hosting it. This information is
-available in [[ldap]] (or [the web interface](https://db.torproject.org/machines.cgi), under the
-`physicalHost` field. Then login to that server to diagnose this
+available in [[ldap]]
+(or [the web interface](https://db.torproject.org/machines.cgi), under the
+`physicalHost` field). Then login to that server to diagnose this
 issue.
 
 If the physical host is not responding or is empty (in which case it
-- 
GitLab