From 8d0bd5f4d7a39f56b6119b0f3ff22b1e92152c27 Mon Sep 17 00:00:00 2001
From: Ryan Link <47920994+ryanlink@users.noreply.github.com>
Date: Tue, 26 Nov 2024 13:54:11 -0600
Subject: [PATCH] Update test.md - stderr not stdout

---
 docs/references/subcommands/test.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/references/subcommands/test.md b/docs/references/subcommands/test.md
index 4026930b27..2efbfa4bc8 100644
--- a/docs/references/subcommands/test.md
+++ b/docs/references/subcommands/test.md
@@ -3,7 +3,7 @@
 
 The test command checks whether the most-recent scan of your FOSSA project raised license-policy or vulnerability issues. This command is usually run immediately after `fossa analyze`
 
-- If there are issues, it prints them to stdout and fails with an exit code of 1
+- If there are issues, it prints them to stderr and fails with an exit code of 1
 - If there are no issues, it prints nothing and succeeds with an exit code of 0
 
 `fossa test` supports the [Common FOSSA Project Flags](./analyze.md#common-fossa-project-flags) supported by all commands
@@ -54,4 +54,4 @@ For instance,
 
 
 * If the revision `v2.0.0` has issue: `A`, and the revision `34021e` has issues `A`, `B`, 
-  * `fossa-cli` reports issue `B` and exits with status code of 1.
\ No newline at end of file
+  * `fossa-cli` reports issue `B` and exits with status code of 1.