diff --git a/website/content/docs/configuration/events/configure-events.mdx b/website/content/docs/configuration/events/configure-events.mdx
index 0bd00348cc..9f259eff5e 100644
--- a/website/content/docs/configuration/events/configure-events.mdx
+++ b/website/content/docs/configuration/events/configure-events.mdx
@@ -5,7 +5,7 @@ description: |-
   Configure log event sinks to monitor Boundary resources and actions.
 ---
 
-# Configure events
+# Configure event logging
 
 The [`events`](/boundary/docs/configuration/events) stanza lets you log system information in a well-defined, structured format that gives you visibility into emitted events.
 
diff --git a/website/content/docs/configuration/events/index.mdx b/website/content/docs/configuration/events/index.mdx
index 61731d2c8c..0e451e9948 100644
--- a/website/content/docs/configuration/events/index.mdx
+++ b/website/content/docs/configuration/events/index.mdx
@@ -73,6 +73,6 @@ events {
 
 ## Next steps
 
-Refer to [Configure events](/boundary/docs/configuration/events/configure-events) to configure a controller or worker server to emit events.
+Refer to [Configure event logging](/boundary/docs/configuration/events/configure-events) to configure a controller or worker server to emit events.
 
 Refer to [Telemetry data](/boundary/docs/configuration/events/telemetry-data) for a list of the events and data you can track by enabling telemetry events.
\ No newline at end of file