Update docs/operating-eck/upgrading-eck.asciidoc

Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>

docs/operating-eck/upgrading-eck.asciidoc

@@ -99,7 +99,7 @@ Upgrading the operator results in a one-time update to existing managed resource
 
  1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5
 
-NOTE: Stepping over one of these versions, for example upgrading ECK from 2.4 to 2.7, still triggers a rolling restart.
+NOTE: Stepping over one of these versions, for example upgrading ECK from 2.3 to 2.7, still triggers a rolling restart.
 
 If you have a very large Elasticsearch cluster or multiple Elastic Stack deployments, this rolling restart might be disruptive or inconvenient. To have more control over when the pods belonging to a particular deployment should be restarted, you can <<{p}-exclude-resource,add an annotation>> to the corresponding resources to temporarily exclude them from being managed by the operator. When the time is convenient, you can remove the annotation and let the rolling restart go through.