Apply suggestions from code review

Author: v-stsavell

articles/event-hubs/log-compaction.md

@@ -1,12 +1,12 @@
 ---
-title: Log Compaction
-description: This article describes how log compaction feature works in Event Hubs.
+title: Log compaction
+description: This article describes how the log compaction feature works in Event Hubs.
 ms.topic: article
 ms.date: 10/7/2022
 ms.custom: ignite-2022
 ---
 
-# Log Compaction
+# Log compaction
 
 Log compaction is a way of retaining data in Event Hubs using event key based retention. By default, each event hub/Kafka topic is created with time-based retention or *delete* cleanup policy, where events are purged upon the expiration of the retention time. Rather using coarser-grained time based retention, you can use event key-based retention mechanism where Event Hubs retrains the last known value for each event key of an event hub or a Kafka topic. 
 
@@ -15,7 +15,7 @@ Log compaction is a way of retaining data in Event Hubs using event key based re
 
 As shown below, an event log (of an event hub partition) may have multiple events with the same key. If you're using a compacted event hub, then Event Hubs service will take care of purging old events and only keeping the latest events of a given event key. 
 
-:::image type="content" source="./media/event-hubs-log-compaction/log-compaction.png" alt-text="Image showing how a topic get compacted." lightbox="./media/event-hubs-resource-governance-overview/app-groups.png":::
+:::image type="content" source="./media/event-hubs-log-compaction/log-compaction.png" alt-text="Image showing how a topic gets compacted." lightbox="./media/event-hubs-resource-governance-overview/app-groups.png":::
 
 ### Compaction key
 The partition key that you set with each event is used as the compaction key.