[ignite] 02/05: update incorrect version

[ab...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

abudnikov pushed a commit to branch IGNITE-7595
in repository https://gitbox.apache.org/repos/asf/ignite.git

commit 42f88e7a357d04c5f41e9ff7c05331797d109b29
Author: abudnikov <ab...@gridgain.com>
AuthorDate: Thu Aug 20 17:53:44 2020 +0300

    update incorrect version
---
 docs/_docs/baseline-topology.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/_docs/baseline-topology.adoc b/docs/_docs/baseline-topology.adoc
index 91fcb1e..a0d3d98 100644
--- a/docs/_docs/baseline-topology.adoc
+++ b/docs/_docs/baseline-topology.adoc
@@ -34,9 +34,9 @@ In pure in-memory clusters, the default behavior is to adjust the baseline topol
 automatically when you add or remove server nodes from the cluster. The data is rebalanced automatically, too.
 You can disable the baseline autoadjustment feature and manage baseline topology manually.
 
-NOTE: In previous releases, baseline topology was relevant only to clusters with persistence. However, since version 8.7.14,
-it applies to in-memory clusters as well. If you have a pure in-memory cluster, the transition should be transparent
-for you because, by default, the baseline topology changes automatically when a server node leaves or joins the cluster.
+NOTE: In previous releases, baseline topology was relevant only to clusters with persistence.
+However, since version 2.8.0, it applies to in-memory clusters as well.
+If you have a pure in-memory cluster, the transition should be transparent for you because, by default, the baseline topology changes automatically when a server node leaves or joins the cluster.
 
 == Baseline Topology in Persistent Clusters