diff --git a/modules/ROOT/pages/clustering/databases.adoc b/modules/ROOT/pages/clustering/databases.adoc
index fb0ddc566..cf1751e4c 100644
--- a/modules/ROOT/pages/clustering/databases.adoc
+++ b/modules/ROOT/pages/clustering/databases.adoc
@@ -235,7 +235,7 @@ Neo4j 5.24 introduces the xref:reference/procedures.adoc#procedure_dbms_cluster_
 
 * To make your database write-available again after it has been lost (for example, due to a disaster).
 // See xref:clustering/disaster-recovery.adoc[] for more information.
- 
+
 [CAUTION]
 ====
 The recreate procedure works only for real user databases and not for composite databases, or the `system` database.
@@ -304,7 +304,7 @@ If not used stores were more up to date than the used ones, this results in data
 
 You can specify a set of available servers.
 The stores on all allocations will be synchronized to the most up-to-date store from the defined servers.
-The number of defined servers cannot exceed the number of total allocations in the desired topology. 
+The number of defined servers cannot exceed the number of total allocations in the desired topology.
 
 [source, shell]
 ----
@@ -341,7 +341,7 @@ There is an option to define a new topology when recreating a database.
 This can be beneficial during a disaster, if enough servers are not available to recreate the database with the original topology.
 When altering the total number of allocations down during a recreation, it is important to remember that the number of seeding servers cannot exceed the number of total allocations of the database.
 This also holds true when using recreate with an empty list of seeders.
-If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail. 
+If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail.
 
 [source, shell]
 ----
@@ -488,7 +488,7 @@ Each configuration value is specified as a name followed by `=` and the value, a
 
 [source, cypher, role="noplay"]
 ----
-CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup’, seedConfig: 'region=eu-west-1' }
+CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedConfig: 'region=eu-west-1' }
 ----
 
 The available configuration options are: