From f498e87b0407cb269a16a26ac18cff808e9dafa1 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Tue, 6 Feb 2024 14:22:48 -0500
Subject: [PATCH] spelling: described

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
 src/debugpy/common/messaging.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/debugpy/common/messaging.py b/src/debugpy/common/messaging.py
index b133f71b..f064ee6b 100644
--- a/src/debugpy/common/messaging.py
+++ b/src/debugpy/common/messaging.py
@@ -974,7 +974,7 @@ class MessageHandlingError(Exception):
     escape the message loop unhandled, and terminate the process.
 
     If any message handler raises this exception, but applies_to(message) is False, it
-    is treated as if it was a generic exception, as desribed above. Thus, if a request
+    is treated as if it was a generic exception, as described above. Thus, if a request
     handler issues another request of its own, and that one fails, the failure is not
     silently propagated. However, a request that is delegated via Request.delegate()
     will also propagate failures back automatically. For manual propagation, catch the