From 9406790224055d3ecfa937146370e8c1ffc6d450 Mon Sep 17 00:00:00 2001
From: Teju Nareddy <tnareddy@confluent.io>
Date: Thu, 8 Feb 2024 15:57:23 -0600
Subject: [PATCH] docs: Fix incorrect link in listener_filters.rst (#32285)

Signed-off-by: Teju Nareddy <tnareddy@confluent.io>
---
 .../root/intro/arch_overview/listeners/listener_filters.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/root/intro/arch_overview/listeners/listener_filters.rst b/docs/root/intro/arch_overview/listeners/listener_filters.rst
index 122d52238cfb..717be09e1c1a 100644
--- a/docs/root/intro/arch_overview/listeners/listener_filters.rst
+++ b/docs/root/intro/arch_overview/listeners/listener_filters.rst
@@ -3,15 +3,15 @@
 Listener filters
 ================
 
-Envoy's :ref:`listener filters <envoy_v3_api_msg_config.listener.v3.Filter>`
+Envoy's :ref:`listener filters <envoy_v3_api_msg_config.listener.v3.ListenerFilter>`
 may be used to manipulate connection metadata.
 
-The main purpose of :ref:`listener filters <envoy_v3_api_msg_config.listener.v3.Filter>`
+The main purpose of :ref:`listener filters <envoy_v3_api_msg_config.listener.v3.ListenerFilter>`
 are to make adding further system integration functions easier by not requiring changes
 to Envoy core functionality, and also to make interaction between multiple such features more
 explicit.
 
-The API for :ref:`listener filters <envoy_v3_api_msg_config.listener.v3.Filter>` is relatively
+The API for :ref:`listener filters <envoy_v3_api_msg_config.listener.v3.ListenerFilter>` is relatively
 simple since ultimately these filters operate on newly accepted sockets.
 
 Filters in the chain can stop and subsequently continue iteration to further filters. This allows