From 527fbc968daec7bb16e99d1101d499f6ab9e2987 Mon Sep 17 00:00:00 2001
From: Jah-yee <166608075+Jah-yee@users.noreply.github.com>
Date: Fri, 6 Nov 2026 13:14:43 +0800
Subject: [PATCH] fix: correct spelling errors in docstrings and test docs

Fix four misspellings outside the vendored pydevd tree: 'occured' -> 'occurred' in src/debugpy/common/messaging.py, 'succesful'/'sucessful' -> 'successful' in tests/timeline.md, and 'writen' -> 'written' in tests/pytest_fixtures.py.
---
 src/debugpy/common/messaging.py | 2 +-
 tests/pytest_fixtures.py        | 2 +-
 tests/timeline.md               | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/debugpy/common/messaging.py b/src/debugpy/common/messaging.py
index fb9092cc1..e4fb7a20f 100644
--- a/src/debugpy/common/messaging.py
+++ b/src/debugpy/common/messaging.py
@@ -1059,7 +1059,7 @@ def __init__(self, reason, cause=None, silent=False):
         """Creates a new instance of this class, and immediately logs the exception.
 
         Message handling errors are logged immediately unless silent=True, so that the
-        precise context in which they occured can be determined from the surrounding
+        precise context in which they occurred can be determined from the surrounding
         log entries.
         """
 
diff --git a/tests/pytest_fixtures.py b/tests/pytest_fixtures.py
index 6c99b760d..cb1243d4f 100644
--- a/tests/pytest_fixtures.py
+++ b/tests/pytest_fixtures.py
@@ -196,7 +196,7 @@ def script_file():
     that it uses locally. When linter complains, use #noqa.
 
     Returns a py.path.local instance that has the additional attribute "lines".
-    After the source is writen to disk, tests.code.get_marked_line_numbers() is
+    After the source is written to disk, tests.code.get_marked_line_numbers() is
     invoked on the resulting file to compute the value of that attribute.
     """
 
diff --git a/tests/timeline.md b/tests/timeline.md
index 8b77e30e9..a5fbb3335 100644
--- a/tests/timeline.md
+++ b/tests/timeline.md
@@ -101,7 +101,7 @@ For responses, it is often desirable to specify success or failure in general, w
 Response(request, some.error)
 Response(request, ~some.error)  # success
 ```
-Note that you don't need to do it if you specify the body of the response explicitly, since a succesful response will always have a dict as a body, and a failed response will have an exception as a body.
+Note that you don't need to do it if you specify the body of the response explicitly, since a successful response will always have a dict as a body, and a failed response will have an exception as a body.
 
 Since it is very common to wait for a response to a particular request, there is a shortcut to do it directly via the request occurrence:
 ```py
@@ -112,7 +112,7 @@ and a further shortcut to issue a request, wait for response, and retrieve the r
 ```py
 initialize_response_body = debug_session.request('initialize', {'adapterID': 'test'})
 ```
-On success, `request()` returns the body of the sucessful response directly, rather than the `Response` object. On failure, it raises the appropriate exception.
+On success, `request()` returns the body of the successful response directly, rather than the `Response` object. On failure, it raises the appropriate exception.
 
 ## Expectation algebra