From 53099485033ef9c2ccec5bb87d066162478200a4 Mon Sep 17 00:00:00 2001
From: Chia-Ping Tsai <chia7712@gmail.com>
Date: Tue, 4 Mar 2025 23:02:38 +0800
Subject: [PATCH] address DJ comment

---
 docs/ops.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ops.html b/docs/ops.html
index c201d602e3f61..b58026a9233a1 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -4187,7 +4187,7 @@ <h4 class="anchor-heading"><a id="consumer_rebalance_protocol_server" class="anc
   <p>The assignment strategy is also controlled by the server. The <code>group.consumer.assignors</code> configuration can be used to specify the list of available
     assignors for <code>Consumer</code> groups. By default, the <code>uniform</code> assignor and the <code>range</code> assignor are configured. The first assignor
     in the list is used by default unless the Consumer selects a different one. It is also possible to implement custom assignment strategies on the server side
-    by implementing the <code style="font-size: 12px;">org.apache.kafka.coordinator.group.api.assignor.ConsumerGroupPartitionAssignor</code> interface and specifying the full class name in the configuration.</p>
+    by implementing the <code>ConsumerGroupPartitionAssignor</code> interface and specifying the full class name in the configuration.</p>
 
   <h4 class="anchor-heading"><a id="consumer_rebalance_protocol_consumer" class="anchor-link"></a><a href="#consumer_rebalance_protocol_consumer">Consumer</a></h4>