Fix the syntax in a few pages (#2403) (#2405)

Author: NataliaIvakina

modules/ROOT/pages/backup-restore/restore-backup.adoc

@@ -177,13 +177,11 @@ That means, if you restore `neo4j-2023-06-29T14-50-45.backup`, your database wil
 The following examples assume that you want to restore your data in a new database, called `mydatabase`.
 If you want to replace an existing database, you need to stop it first, and add the option `--overwrite-destination=true` to the restore command.
 
-==== Restore a full backup
-
 . Restore a database backup by running the following command:
 +
 [source, shell,role=nocopy noplay]
 ----
-bin/neo4j-admin database restore --from-path=/path/to/backups/neo4j-2023-05-05T11-26-38.backup mydatabase
+bin/neo4j-admin database restore --from-path=/path/to/backups/neo4j-2023-06-29T14-51-33.backup mydatabase
 ----
 +
 The `--from-path=` argument must contain the path to the last backup of a chain, in this case, `neo4j-2023-06-29T14-51-33.backup`.

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

@@ -151,14 +151,12 @@ Therefore, details such as `leader` and `raftCommandsPerSecond` are database-spe
 |===
 | Field                          | Type     |Optional| Example                                | Description
 | `core`                         | boolean  | no     | `true`                                 | Used to distinguish between if the server is hosting the database in primary (core) or secondary mode.
-| `lastAppliedRaftIndex`         | number   | no     | `4321`                                 | Every transaction in a cluster is associated with a raft index.
-
-                                                                                              Gives an indication of what the latest applied raft log index is.
+| `lastAppliedRaftIndex`         | number   | no     | `4321`                                 | Every transaction in a cluster is associated with a raft index. +
+Gives an indication of what the latest applied raft log index is.
 | `participatingInRaftGroup`     | boolean  | no     | `false`                                | A participating member is able to vote.
                                                                                               A primary is considered participating when it is part of the voter membership and has kept track of the leader.
-| `votingMembers`                | string[] | no     | `[]`                                   | A member is considered a voting member when the leader has been receiving communication with it.
-
-                                                                                              List of member's `memberId` that are considered part of the voting set by this primary.
+| `votingMembers`                | string[] | no     | `[]`                                   | A member is considered a voting member when the leader has been receiving communication with it. +
+List of member's `memberId` that are considered part of the voting set by this primary.
 | `isHealthy`                      | boolean  | no     | `true`                                 | Indicates that the local database on this cluster member has not encountered a critical error that can block database operation.
 
 [CAUTION]