Allow parameters in CREATE/ALTER DATABASE TOPOLOGY

modules/ROOT/pages/clustering/databases.adoc

@@ -36,6 +36,24 @@ However, over time, or after several `CREATE DATABASE` commands have been issued
 At this point you can run `REALLOCATE DATABASES` to make the cluster re-balance databases across all servers that are part of the cluster.
 ====
 
+The `CREATE DATABASE` and `ALTER DATABASE` commands support the usage of link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/syntax/parameters[parameters] when providing the database, the number of primaries and/or the number of secondaries.
+
+.Parameters
+[source,javascript, indent=0]
+----
+{
+  "dbname": "foo",
+  "primary": 1,
+  "secondary": 2
+}
+----
+
+.Query
+[source, cypher, indent=0]
+----
+CREATE DATABASE $dbname TOPOLOGY $primary PRIMARIES $secondary SECONDARIES
+----
+
 [[alter-database]]
 == `ALTER DATABASE`
 
@@ -75,7 +93,7 @@ Keep in mind that during such a transition, the database will be unavailable for
 `ALTER DATABASE` commands are optionally idempotent, with the default behavior to fail with an error if the database does not exist.
 Appending `IF EXISTS` to the command ensures that no error is returned and nothing happens should the database not exist.
 
-If the `ALTER DATABASE` command decreases the number of allocations of a database, allocations on xref:clustering/servers.adoc#_cordoned_servers[cordoned servers] are removed first.
+If the `ALTER DATABASE` command decreases the number of allocations of a database, allocations on xref:clustering/servers.adoc#cordoned-state[cordoned servers] are removed first.
 
 .Query
 [source, cypher]
@@ -401,7 +419,7 @@ In this case, the address for `server01` is `localhost:7687` and thus, the serve
 The topology of `foo` is stored in the `system` database and when you create it, it is allocated according to the default topology (which can be shown with `CALL dbms.showTopologyGraphConfig`).
 This may be different from the topology of `foo` when it was backed up.
 If you want to ensure a certain allocation across the cluster, you can specify the desired topology with the `TOPOLOGY` clause in the `CREATE DATABASE` command.
-See <<#_create_database, `CREATE DATABASE`>> for more information.
+See <<create-database, `CREATE DATABASE`>> for more information.
 +
 [source, cypher, role=noplay]
 ----

modules/ROOT/pages/clustering/servers.adoc

@@ -92,11 +92,12 @@ When a server is in the deallocated state, it no longer hosts any databases besi
 Additionally, deallocated servers cannot have any further databases allocated to them.
 Note that there is a known situation in which a previously deallocated offline server can transiently show as deallocating when restarting, it will, however, eventually return to the deallocated state without intervention.
 
+[cordoned-state]
 === Cordoned state
 
 The _Cordoned_ state is similar to _Deallocating_ in that servers in this state will not be allocated to host additional databases.
 Unlike _Deallocating_ however, cordoned servers do not lose the databases they already host.
-It is worth noting that when decreasing the number of allocations of a database, allocations on cordoned servers are removed first. 
+It is worth noting that when decreasing the number of allocations of a database, allocations on cordoned servers are removed first.
 
 A server is transitioned from the _Enabled_ state to the _Cordoned_ state by executing the procedure `dbms.cluster.cordonServer`.
 A server in the _Cordoned_ state may be transitioned to _Deallocating_, or back to _Enabled_.