From c1071f55db21099cbb3e1ef7aaefa402e851f603 Mon Sep 17 00:00:00 2001
From: Paul Dorsch <107068277+pauld-msft@users.noreply.github.com>
Date: Fri, 19 Jun 2026 17:19:02 -0400
Subject: [PATCH] Clarify Experimental detector behavior in documentation

Updated the behavior description for the Experimental stage to clarify that enabling experimental detectors will include output in scan results.
---
 docs/creating-a-new-detector.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/creating-a-new-detector.md b/docs/creating-a-new-detector.md
index eafe08413..41739b8d8 100644
--- a/docs/creating-a-new-detector.md
+++ b/docs/creating-a-new-detector.md
@@ -54,7 +54,7 @@ New detectors progress through three stages before becoming default. Contributor
 | Stage | Interface | Behavior |
 |-------|-----------|----------|
 | **1. Default Off** | `IDefaultOffComponentDetector` | Must be explicitly enabled via `--DetectorArgs YourDetectorId=EnableIfDefaultOff`. Detector should be fully functional and produce correct output. |
-| **2. Experimental** | `IExperimentalDetector` | Runs automatically but output is NOT included in scan results. Used to measure performance impact. |
+| **2. Experimental** | `IExperimentalDetector` | Runs automatically but output is NOT included in scan results. Used to measure performance impact. Enabling experimental detectors via `--DetectorArgs YourDetectorId=EnableIfDefaultOff` will cause output to be included in scan results. |
 | **3. Default** | `IComponentDetector` | Fully integrated. Runs by default and output is included in results. Can be filtered via `--DetectorCategory` or `--DetectorFilters`. |
 
 ## Step 1: Define Your Component Type