diff --git a/docs/src/main/asciidoc/overview.adoc b/docs/src/main/asciidoc/overview.adoc
index 9cb1e99a..29b42b52 100644
--- a/docs/src/main/asciidoc/overview.adoc
+++ b/docs/src/main/asciidoc/overview.adoc
@@ -324,7 +324,7 @@ When an application starts, the initial position in each assigned partition depe
 If `resetOffsets` is `false`, normal Kafka consumer https://kafka.apache.org/documentation/#consumerconfigs_auto.offset.reset[`auto.offset.reset`] semantics apply.
 i.e. If there is no committed offset for a partition for the binding's consumer group, the position is `earliest` or `latest`.
 By default, bindings with an explicit `group` use `earliest`, and anonymous bindings (with no `group`) use `latest`.
-These defaults can be overriden by setting the `startOffset` binding property.
+These defaults can be overridden by setting the `startOffset` binding property.
 There will be no committed offset(s) the first time the binding is started with a particular `group`.
 The other condition where no committed offset exists is if the offset has been expired.
 With modern brokers (since 2.1), and default broker properties, the offsets are expired 7 days after the last member leaves the group.