H2s

Author: spelluru

articles/event-hubs/event-processor-balance-partition-load.md

@@ -35,7 +35,7 @@ You don't need to build your own solution to meet these requirements. The Azure
 
 For most production scenarios, we recommend that you use the event processor client for reading and processing events. The processor client is intended to provide a robust experience for processing events across all partitions of an event hub in a performant and fault tolerant manner while providing a means to checkpoint its progress. Event processor clients can work cooperatively within the context of a consumer group for a given event hub. Clients will automatically manage distribution and balancing of work as instances become available or unavailable for the group.
 
-## Partition ownership tracking
+## Partition ownership 
 
 An event processor instance typically owns and processes events from one or more partitions. Ownership of partitions is evenly distributed among all the active event processor instances associated with an event hub and consumer group combination. 
 
@@ -62,7 +62,7 @@ When you create an event processor, you specify functions that will process even
 
 We recommend that you do things relatively fast. That is, do as little processing as possible. If you need to write to storage and do some routing, it's better to use two consumer groups and have two event processors.
 
-## Checkpointing
+## Checkpoint
 
 *Checkpointing* is a process by which an event processor marks or commits the position of the last successfully processed event within a partition. Marking a checkpoint is typically done within the function that processes the events and occurs on a per-partition basis within a consumer group.