Translation:

raw changes

3 files changed, 26 insertions, 7 deletions

diff --git a/ydb/docs/en/core/administration/upgrade.md b/ydb/docs/en/core/administration/upgrade.md
index a2ab3ef352d..295352fcc4d 100644
--- a/ydb/docs/en/core/administration/upgrade.md
+++ b/ydb/docs/en/core/administration/upgrade.md
@@ -2,14 +2,18 @@
 
 {{ ydb-short-name }} is a distributed system that supports rolling restart without downtime or performance degradation.
 
-## Update procedure {#upgrade_order}
+## Update procedure {#upgrade-order}
 
-The basic use case is rolling updates:
+The basic scenario is updating the executable file and restarting each node one by one:
 
-1. Updating storage nodes.
-2. Updating dynamic nodes.
+1. Updating and restarting storage nodes.
+1. Updating and restarting dynamic nodes.
 
-The shutdown and startup process is described on the [Safe restart and shutdown of nodes](../maintenance/manual/node_restarting.md) page. You must update {{ ydb-short-name }} nodes one by one and monitor the cluster status after each step in [{{ ydb-short-name }} Monitoring](../maintenance/embedded_monitoring/ydb_monitoring.md).
+The shutdown and startup process is described on the [Safe restart and shutdown of nodes](../maintenance/manual/node_restarting.md) page.
+You must update {{ ydb-short-name }} nodes one by one and monitor the cluster status after each step in [{{ ydb-short-name }} Monitoring](../maintenance/embedded_monitoring/ydb_monitoring.md): make sure the `Storage` tab has no pools in the `Degraded` status (as shown in the example below). Otherwise, stop the update process.
+
+
+![Monitoring_storage_state](../maintenance/embedded_monitoring/_assets/monitoring_storage_state.png)
 
 ## Version compatibility {#version-compatability}
 
@@ -20,4 +24,19 @@ All minor versions within a major version are compatible for updates. Major vers
 * X.Y.* → X.Y+2.*: Update is impossible, major versions are inconsistent.
 * X.Y.* → X.Y-2.*: Update is impossible, major versions are inconsistent.
 
-A list of available versions can be found on the [download page](https://ydb.tech/en/docs/downloads/).
\ No newline at end of file
+A list of available versions can be found on the [download page](https://ydb.tech/en/docs/downloads/).
+
+{% note info %}
+
+**Examples of compatible versions:**
+
+v.22.2.5	->	v.22.2.47: Update is possible.
+v.22.2.47	->	v.22.4.21: Update is possible.
+v.22.2.40	->	v.22.4.21: Update is impossible, first upgrade to the latest version (v.22.2.47).
+v.22.2.47	->	v.22.5.5: Update is impossible, upgrade to the next major version (v.22.4).*
+
+{% endnote %}
+
+## Checking update results {#upgrade_check}
+
+You can check the updated node versions on the `Nodes` page in Monitoring.
diff --git a/ydb/docs/en/core/maintenance/embedded_monitoring/_assets/monitoring_storage_state.png b/ydb/docs/en/core/maintenance/embedded_monitoring/_assets/monitoring_storage_state.png
new file mode 100644
index 00000000000..8ab2d020e13
--- /dev/null
+++ b/ydb/docs/en/core/maintenance/embedded_monitoring/_assets/monitoring_storage_state.png
diff --git a/ydb/docs/ru/core/administration/upgrade.md b/ydb/docs/ru/core/administration/upgrade.md
index dda97bfa1c7..48c7738a66f 100644
--- a/ydb/docs/ru/core/administration/upgrade.md
+++ b/ydb/docs/ru/core/administration/upgrade.md
@@ -7,7 +7,7 @@
 Базовым сценарием является обновление исполняемого файла и последовательный рестарт каждого узла:
 
 1. Обновление и рестарт storage узлов;
-2. Обновление и рестар динамических узлов.
+1. Обновление и рестар динамических узлов.
 
 Процесс остановки и запуска описан на странице [Безопасные рестарт и выключение узлов](../maintenance/manual/node_restarting.md). 
 Узлы {{ ydb-short-name }} следует обновлять последовательно по одному, после каждого шага контролировать состояние кластера через [{{ ydb-short-name }} Monitoring](../maintenance/embedded_monitoring/ydb_monitoring.md) - на вкладке `Storage` не должно быть пулов в состоянии `Degraded` (как на примере ниже). В противном случае обновление необходимо остановить.