diff --git a/sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/README.md b/sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/README.md
index 232ae353f719..727660c66c74 100644
--- a/sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/README.md
+++ b/sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/README.md
@@ -86,9 +86,9 @@ downstream applications, and to provide resiliency if a failover between readers
 It is possible to return to older data by specifying a lower offset from this checkpointing process. Through this
 mechanism, checkpointing enables both failover resiliency and event stream replay.
 
-### Offsets & sequence numbers
+### Offsets & sequence numbers
 
-Both offset & sequence number refer to the position of an event within a partition. You can think of them as a
+Both offset & sequence number refer to the position of an event within a partition. You can think of them as a
 client-side cursor. The offset is a byte numbering of the event. The offset/sequence number enables an event consumer
 (reader) to specify a point in the event stream from which they want to begin reading events. You can specify the
 timestamp such that you receive events that were enqueued only after the given timestamp. Consumers are responsible for