From 00cc870dff55622d70752770b3eca3ca82c6aaac Mon Sep 17 00:00:00 2001
From: Kanav <66438237+kanjurer@users.noreply.github.com>
Date: Fri, 28 Feb 2025 07:28:05 -0400
Subject: [PATCH] Fixed redirect link

---
 docs/docs/learn/programming/modules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/learn/programming/modules.md b/docs/docs/learn/programming/modules.md
index c4be6c2efa..3275ee0ae8 100644
--- a/docs/docs/learn/programming/modules.md
+++ b/docs/docs/learn/programming/modules.md
@@ -15,7 +15,7 @@ A **DSPy module** is a building block for programs that use LMs.
 
 ## How do I use a built-in module, like `dspy.Predict` or `dspy.ChainOfThought`?
 
-Let's start with the most fundamental module, `dspy.Predict`. Internally, all other DSPy modules are built using `dspy.Predict`. We'll assume you are already at least a little familiar with [DSPy signatures](/building-blocks/2-signatures), which are declarative specs for defining the behavior of any module we use in DSPy.
+Let's start with the most fundamental module, `dspy.Predict`. Internally, all other DSPy modules are built using `dspy.Predict`. We'll assume you are already at least a little familiar with [DSPy signatures](/building-blocks/signatures), which are declarative specs for defining the behavior of any module we use in DSPy.
 
 To use a module, we first **declare** it by giving it a signature. Then we **call** the module with the input arguments, and extract the output fields!