Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Fix grammar & typos: CrowdStrike capitalization and stray Splunk heading (#257)

mintlify[bot]084b980cad80
diff --git a/docs/guides/jamf-falcon-mdm.mdx b/docs/guides/jamf-falcon-mdm.mdx
index 38f80399..43bab9a5 100644
--- a/docs/guides/jamf-falcon-mdm.mdx
+++ b/docs/guides/jamf-falcon-mdm.mdx
@@ -1,5 +1,5 @@
---
-title: "Claude with Jamf and Crowdstrike Falcon"
+title: "Claude with Jamf and CrowdStrike Falcon"
description: "Self-serve Jamf Pro setup for Beacon endpoint telemetry, Claude Code hooks, and CrowdStrike Falcon LogScale HEC forwarding"
---
diff --git a/docs/log-forwarding/splunk.mdx b/docs/log-forwarding/splunk.mdx
index 80027861..15728266 100644
--- a/docs/log-forwarding/splunk.mdx
+++ b/docs/log-forwarding/splunk.mdx
@@ -84,8 +84,6 @@ Your forwarder should wrap each Beacon JSON object in a Splunk HEC envelope:
Keep the HEC token in your endpoint-management secret store and pass it to Beacon at install or repair time.
-## Customer-managed forwarder behavior
-
## Collector behavior
When Splunk HEC is configured, Beacon writes a collector pipeline with both exporters enabled: