From 1f1f47e0646501e19c98c4abc62c0476f194bb75 Mon Sep 17 00:00:00 2001
From: jamie-wilson88 <168847178+jamie-wilson88@users.noreply.github.com>
Date: Fri, 23 May 2025 13:10:32 -0400
Subject: [PATCH] Update integration-level-outputs.md

---
 reference/fleet/integration-level-outputs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reference/fleet/integration-level-outputs.md b/reference/fleet/integration-level-outputs.md
index 876fc2462..7dfa006bb 100644
--- a/reference/fleet/integration-level-outputs.md
+++ b/reference/fleet/integration-level-outputs.md
@@ -12,7 +12,7 @@ If you have an `Enterprise` [{{stack}} subscription](https://www.elastic.co/subs
 
 Integration-level outputs are very useful for certain scenarios. For example:
 
-* You can may want to send security logs monitored by an {{agent}} to one {{ls}} output, while informational logs are sent to a another {{ls}} output.
+* You may want to send security logs monitored by an {{agent}} to one {{ls}} output, while informational logs are sent to another {{ls}} output.
 * If you operate multiple {{beats}} on a system and want to migrate these to {{agent}}, integration-level outputs enable you to maintain the distinct outputs that are currently used by each Beat.