Merge pull request #89289 from changeworld/patch-58

Fix typo

Author: ShannonLeavitt

articles/service-fabric/service-fabric-diagnostics-events.md

@@ -30,7 +30,7 @@ Here are some examples of scenarios that you should see events for in your clust
 
 There are a few different ways through which Service Fabric events can be accessed:
 * The events are logged through standard channels such as ETW/Windows Event logs and can be visualized by any monitoring tool that supports these such as Azure Monitor logs. By default, clusters created in the portal have diagnostics turned on and have the Windows Azure diagnostics agent sending the events to Azure table storage, but you still need to integrate this with your log analytics resource. Read more about configuring the [Azure Diagnostics agent](service-fabric-diagnostics-event-aggregation-wad.md) to modify the diagnostics configuration of your cluster to pick up more logs or performance counters and the [Azure Monitor logs integration](service-fabric-diagnostics-event-analysis-oms.md)
-* EventStore service's Rest APIs that allow you to query the cluster directly, or through the Service Fabric Client Library. See [Query EventStore APIs for cluster events](service-fabric-diagnostics-eventstore-query.md).
+* EventStore service's REST APIs that allow you to query the cluster directly, or through the Service Fabric Client Library. See [Query EventStore APIs for cluster events](service-fabric-diagnostics-eventstore-query.md).
 
 ## Next steps
 * More information on monitoring your cluster - [Monitoring the cluster and platform](service-fabric-diagnostics-event-generation-infra.md).