From 891a06c2940b7aa441aac047a98d0dce86fb39a0 Mon Sep 17 00:00:00 2001 From: Remy Suen Date: Sun, 21 Sep 2025 20:18:17 -0400 Subject: [PATCH] docs: Small grammar fix to use a possessive pronoun (#38610) > Your extension can define it's own debug locators > Your extension can define it is own debug locators The sentence above does not make sense after expanding "it's". We should instead be using the possessive "its" in this scenario. Release Notes: - N/A Signed-off-by: Remy Suen --- docs/src/extensions/debugger-extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/extensions/debugger-extensions.md b/docs/src/extensions/debugger-extensions.md index 4412bf8b9aa576e736b5b6dc25c5f4bc48100b18..fa33c25732631ca98910f0b19275ab32475955ff 100644 --- a/docs/src/extensions/debugger-extensions.md +++ b/docs/src/extensions/debugger-extensions.md @@ -65,7 +65,7 @@ Put another way, it is supposed to answer the question: "Given a program, a list Zed offers an automatic way to create debug scenarios with _debug locators_. A locator locates the debug target and figures out how to spawn a debug session for it. Thanks to locators, we can automatically convert existing user tasks (e.g. `cargo run`) and convert them into debug scenarios (e.g. `cargo build` followed by spawning a debugger with `target/debug/my_program` as the program to debug). -> Your extension can define it's own debug locators even if it does not expose a debug adapter. We strongly recommend doing so when your extension already exposes language tasks, as it allows users to spawn a debug session without having to manually configure the debug adapter. +> Your extension can define its own debug locators even if it does not expose a debug adapter. We strongly recommend doing so when your extension already exposes language tasks, as it allows users to spawn a debug session without having to manually configure the debug adapter. Locators can (but don't have to) be agnostic to the debug adapter they are used with. They are simply responsible for locating the debug target and figuring out how to spawn a debug session for it. This allows for a more flexible and extensible debugging experience.