diff --git a/docs/src/extensions/debugger-extensions.md b/docs/src/extensions/debugger-extensions.md
index 3c9e291058e31a781fbfca57ad98a285bfff5e38..ad8e2c5e2970c21179d42ea32f9bab4414de4e44 100644
--- a/docs/src/extensions/debugger-extensions.md
+++ b/docs/src/extensions/debugger-extensions.md
@@ -8,7 +8,7 @@ A given extension may provide one or more DAP servers.
 Each DAP server must be registered in the `extension.toml`:
 
 ```toml
-[debug-adapters.my-debug-adapter]
+[debug_adapters.my-debug-adapter]
 # Optional relative path to the JSON schema for the debug adapter configuration schema. Defaults to `debug_adapter_schemas/$DEBUG_ADAPTER_NAME_ID.json`.
 # Note that while this field is optional, a schema is mandatory.
 schema_path = "relative/path/to/schema.json"
@@ -72,7 +72,7 @@ Locators can (but don't have to) be agnostic to the debug adapter they are used
 Your extension can define one or more debug locators. Each debug locator must be registered in the `extension.toml`:
 
 ```toml
-[debug-locators.my-debug-locator]
+[debug_locators.my-debug-locator]
 ```
 
 Locators have two components.
diff --git a/docs/src/extensions/developing-extensions.md b/docs/src/extensions/developing-extensions.md
index 2b8aaef3ec1c5b49a35356f662dbe79823a8fb32..a523218b43c022f5c1166d0e431ed193fdd3ef2e 100644
--- a/docs/src/extensions/developing-extensions.md
+++ b/docs/src/extensions/developing-extensions.md
@@ -89,6 +89,8 @@ impl zed::Extension for MyExtension {
 zed::register_extension!(MyExtension);
 ```
 
+> `stdout`/`stderr` is forwarded directly to the Zed process. In order to see `println!`/`dbg!` output from your extension, you can start Zed in your terminal with a `--foreground` flag.
+
 ## Forking and cloning the repo
 
 1. Fork the repo