From 3b8de85e1b4d5003d2bd64e8b599585e05a9b70d Mon Sep 17 00:00:00 2001
From: Karen Metts <35154725+karenzone@users.noreply.github.com>
Date: Wed, 20 Nov 2024 09:05:43 -0500
Subject: [PATCH] Doc: Fix link format for proper rendering (#204)

---
 ...your-data-ingest-data-through-integrations-logstash.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc b/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc
index d2c109be..5cca7bbb 100644
--- a/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc
+++ b/serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc
@@ -21,7 +21,7 @@ such as data routed to multiple destinations or when you need to make your data
 {ls} is a powerful, versatile ETL (Extract, Transform, Load) engine that can play an important role in organizations of all sizes.
 Some capabilities and features for large, self-managed users aren't appropriate for {serverless-short}.
 
-You'll use the {ls} {logstash-ref}/plugins-outputs-elasticsearch.html[`((es)) output plugin`] to send data to {es3}.
+You'll use the {ls} {logstash-ref}/plugins-outputs-elasticsearch.html[{es} output plugin] to send data to {es3}.
 Some differences to note between {es3} and self-managed {es}:
 
 * Your logstash-output-elasticsearch configuration uses **API keys** to access {es} from {ls}.