install-a-bonita-bpm-cluster.adoc: fix broken anchors

modules/runtime/pages/bonita-platform-setup.adoc

@@ -185,7 +185,7 @@ It is made of both data entered in file `database.properties` as well as other d
 This file *should not* be modified manually in most cases, unless for specific use-cases like adding parameters in the connection URL or using a specific database driver.
 
 This file contains the Database configuration information that are not inside file `database.properties` (database driver class name, connection URL, etc).
-Those information are used internally by the Bonita Setup tool to configure properly the bundle (See <<run_bundle_configure,configure command>>) and the database initialization procedure (See <<init_platform_conf,init command>>). +
+This information are used internally by the Bonita Setup tool to configure properly the bundle (See <<run_bundle_configure,configure command>>) and the database initialization procedure (See <<init_platform_conf,init command>>). +
 Bonita Setup tool uses the values provided in file `database.properties` as replacement strings to the properties defined in file `internal.properties`. Those new processed values are then used by the tool.
 
 _Usage_: +

modules/runtime/pages/install-a-bonita-bpm-cluster.adoc

@@ -223,21 +223,21 @@ To dismantle a cluster:
 . When all nodes have been stopped, update the load balancer to remove the cluster.
 
 The individual nodes can now be used as standalone Bonita server, provided the following change in the configuration is done:
-Update file `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the  xref:runtime:bonita-platform-setup.adoc#configuration_files[platform setup tool] to update it and set back the *`bonita.cluster`* property to *`false`*.
+Update file `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the xref:runtime:bonita-platform-setup.adoc[platform setup tool] to update it and set back the *`bonita.cluster`* property to *`false`*.
 
-See xref:runtime:bonita-platform-setup.adoc#updating_configuration[How to update a Bonita Tomcat Bundle configuration] for more details on updating the configuration.
+See xref:runtime:bonita-platform-setup.adoc#run_bundle_configure[How to update a Bonita Tomcat Bundle configuration] for more details on updating the configuration.
 
 === Managing the cluster with Hazelcast
 
-As said before, Bonita cluster uses Hazelcast as the distributed cluster dispatcher layer. Therefore you can use the Hazelcast tools to manage the cluster topology.
+As said before, Bonita cluster uses Hazelcast as the distributed cluster dispatcher layer. Therefore, you can use the Hazelcast tools to manage the cluster topology.
 See the http://www.hazelcast.com/docs.jsp[Hazelcast documentation] for details.
 
 Note that a Bonita cluster uses multicast for discovery by default. You can disable this in Hazelcast.
 If you are using multicast, you must ensure that your production environment is insulated from any test environment that might also contain cluster nodes.
 This is to ensure the nodes do not discover each other on the network, if they are not supposed to run inside the same cluster.
 
 It is possible to have more than one cluster on the same network. In this case, you must configure the cluster names to be sure that it is clear which node belongs to which cluster.
-You can configure the cluster name through Hazelcast or by updating `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the  xref:runtime:bonita-platform-setup.adoc#configuration_files[platform setup tool] to update it.
+You can configure the cluster name through Hazelcast or by updating `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the  xref:runtime:bonita-platform-setup.adoc[platform setup tool] to update it.
 
 == image:troubleshooting.png[troubleshooting-icon] Troubleshooting