From adfa5ed0cf8cf9291c4cd396e242eccfbf3f69a9 Mon Sep 17 00:00:00 2001
From: thiswillbeyourgithub
 <26625900+thiswillbeyourgithub@users.noreply.github.com>
Date: Fri, 9 May 2025 11:22:24 +0200
Subject: [PATCH] fix: update the other valves page for pipelines

it was not making it clear that valves are not a pipeline only feature

Signed-off-by: thiswillbeyourgithub <26625900+thiswillbeyourgithub@users.noreply.github.com>
---
 docs/pipelines/valves.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/pipelines/valves.md b/docs/pipelines/valves.md
index b0334d5..de4bbc4 100644
--- a/docs/pipelines/valves.md
+++ b/docs/pipelines/valves.md
@@ -5,7 +5,9 @@ title: "⚙️ Valves"
 
 # Valves
 
-Valves are input variables that are set per pipeline. Valves are set as a subclass of the `Pipeline` class, and initialized as part of the `__init__` method of the `Pipeline` class.
+`Valves` (see the dedicated [Valves & UserValves](../features/plugin/valves/index.mdx) page) can also be set for `Pipeline`. In short, `Valves` are input variables that are set per pipeline.
+
+`Valves` are set as a subclass of the `Pipeline` class, and initialized as part of the `__init__` method of the `Pipeline` class.
 
 When adding valves to your pipeline, include a way to ensure that valves can be reconfigured by admins in the web UI. There are a few options for this: