Skip to content

Commit 4090d40

Browse files
Update integration-level-outputs.md (#1477)
1 parent ddd19f3 commit 4090d40

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

reference/fleet/integration-level-outputs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ If you have an `Enterprise` [{{stack}} subscription](https://www.elastic.co/subs
1212

1313
Integration-level outputs are very useful for certain scenarios. For example:
1414

15-
* 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.
15+
* You may want to send security logs monitored by an {{agent}} to one {{ls}} output, while informational logs are sent to another {{ls}} output.
1616
* 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.
1717

1818

0 commit comments

Comments
 (0)