Update the metric in the cluster endpoint description (neo4j#2516)

Author: NataliaIvakina

modules/ROOT/pages/clustering/monitoring/endpoints.adoc

@@ -173,7 +173,7 @@ A cluster member may still report `"isHealthy": true` even if the database curre
                                                                                               Not relevant to secondaries, and hence is not included.
 | `raftCommandsPerSecond` label:deprecated[]  | number   | yes    | `124`                       | An estimate of the average Raft state machine throughput over a sampling window configurable via `clustering.status_throughput_window` setting.
 `raftCommandsPerSecond` is not an effective way to monitor that servers are not falling behind in updated and is hence deprecated and will be removed in the next major release of Neo4j.
-It is recommended to use the metric `<prefix>.clustering.core.commit_index` on each server and look for divergence instead.
+It is recommended to use the metric `<prefix>.cluster.raft.commit_index` on each server and look for divergence instead.
 |===
 
 After an instance has been switched on, the status endpoint can be accessed in order to make sure all the guarantees listed in the table below are met.