diff --git a/pages/clustering/high-availability/ha-commands-reference.mdx b/pages/clustering/high-availability/ha-commands-reference.mdx
index d743dab46..84fe3e3c2 100644
--- a/pages/clustering/high-availability/ha-commands-reference.mdx
+++ b/pages/clustering/high-availability/ha-commands-reference.mdx
@@ -88,6 +88,33 @@ REMOVE COORDINATOR coordinatorId;
 REMOVE COORDINATOR 2;
 ```
 
+### `UPDATE CONFIG`
+
+Updates the configuration of the data instance/coordinator in the cluster.
+
+```cypher
+UPDATE CONFIG FOR ( INSTANCE instanceName | COORDINATOR coordinatorServerId ) configsMap=configMap ;
+```
+
+{<h4 className="custom-header"> Parameters </h4>}
+
+- **`instanceName` (string)** — the name of the data instance for which the configuration changes will be applied.
+- **`coordinatorServerId` (int)** — previously registered coordinator ID for which the configuration changes will be applied.
+- **`configsMaps` (int)** — Map of KV pairs that signal which field should be updated. Currently, it is only supported to update bolt server
+of each instance.
+
+
+{<h4 className="custom-header"> Behavior & implications </h4>}
+
+- Must be executed on the **leader** coordinator.
+- Only bolt server can be updated.
+
+{<h4 className="custom-header"> Example </h4>}
+
+```cypher
+UPDATE CONFIG FOR COORDINATOR 1 {'bolt_server': '127.0.0.1:7690'};
+UPDATE CONFIG FOR INSTANCE instance_2 {'bolt_server': '127.0.0.1:7688'}
+```
 
 ### `REGISTER INSTANCE`