diff --git a/docs/Software/Profiling_and_Debugging/Debugging.md b/docs/Software/Profiling_and_Debugging/Debugging.md
index eb1d71c8b..54a3eb9ba 100644
--- a/docs/Software/Profiling_and_Debugging/Debugging.md
+++ b/docs/Software/Profiling_and_Debugging/Debugging.md
@@ -7,9 +7,13 @@ zendesk_article_id: 360001008136
 zendesk_section_id: 360000278935
 ---
 
+!!! warning
+    REANNZ no longer has access to an ARM DDT parallel debugger. Discussions are under way to determine user interest in purchasing 
+    DDT or a similar debugger. Please send an email to `support@reannz.co.nz` if you would like REANNZ to buy DDT (or another tool). 
+
 There are many reasons why a program might crash. Some Slurm job states
 such as `TIMEOUT` or `OUT_OF_MEMORY` can indicate a clear reason, but when
-the job state is simply FAILED and the error message in the job's log
+the job state is simply `FAILED` and the error message in the job's log
 file simply states "Segmentation Fault" or "Illegal instruction",
 investigations become more complicated. In the following, a selection of
 tools is presented which might assist. Most of the following approaches