Update the default value of dbms.record_format

modules/ROOT/pages/configuration/configuration-settings.adoc

@@ -1,6 +1,6 @@
 [[configuration-settings]]
 = Configuration settings
-:description: This page provides a complete reference to the Neo4j configuration settings. 
+:description: This page provides a complete reference to the Neo4j configuration settings.
 :description: Reference for Neo4j procedures.
 :page-aliases: ROOT:reference/configuration-settings.adoc
 :page-styles: hide-table-captions
@@ -67,7 +67,7 @@ m|+++250.00MiB+++
 |===
 
 [[config_dbms.checkpoint.iops.limit]]
-=== `dbms.checkpoint.iops.limit` 
+=== `dbms.checkpoint.iops.limit`
 
 label:dynamic[Dynamic]
 
@@ -125,7 +125,7 @@ m|+++true+++
 |===
 
 [[config_causal_clustering.cluster_allow_reads_on_leader]]
-=== `causal_clustering.cluster_allow_reads_on_leader` 
+=== `causal_clustering.cluster_allow_reads_on_leader`
 
 label:dynamic[Dynamic]
 
@@ -180,7 +180,7 @@ m|+++8+++
 |===
 
 [[config_causal_clustering.connect_randomly_to_server_group]]
-=== `causal_clustering.connect_randomly_to_server_group` 
+=== `causal_clustering.connect_randomly_to_server_group`
 
 label:dynamic[Dynamic]
 
@@ -1445,7 +1445,7 @@ a|fabric.graph.<graph ID>.name, A valid graph name. Containing only alphabetic c
 [frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
 |===
 |Description
-a|URI of the Neo4j DBMS hosting the database associated to the Fabric graph. Example: neo4j://somewhere:7687 
+a|URI of the Neo4j DBMS hosting the database associated to the Fabric graph. Example: neo4j://somewhere:7687
 A comma separated list of URIs is acceptable. This is useful when the Fabric graph is hosted on a cluster and more that one bootstrap address needs to be provided in order to avoid a single point of failure. The provided addresses will be considered as an initial source of a routing table. Example: neo4j://core-1:1111,neo4j://core-2:2222.
 |Valid values
 a|fabric.graph.<graph ID>.uri, a ',' separated list with elements of type 'a URI'.
@@ -2185,7 +2185,7 @@ a|Database record format. Valid values are blank(no value, default), `standard`,
 |Valid values
 a|dbms.record_format, a string
 |Default value
-m|Blank (no value). New databases will use `aligned`. Existing databases will stay on their current format
+m|`aligned` for new databases. Existing databases stay on their current format.
 |===
 
 [[config_dbms.relationship_grouping_threshold]]
@@ -2344,7 +2344,7 @@ m|+++false+++
 
 label:dynamic[Dynamic]
 
-.dbms.databases.read_only 
+.dbms.databases.read_only
 [frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
 |===
 |Description
@@ -2595,7 +2595,7 @@ m|+++true+++
 
 label:dynamic[Dynamic]
 
-.dbms.allow_upgrade 
+.dbms.allow_upgrade
 [frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
 |===
 |Description
@@ -5029,7 +5029,7 @@ label:dynamic[Dynamic]
 |===
 |Description
 a|An authorization mapping from LDAP group names to Neo4j role names. The map should be formatted as a semicolon separated list of key-value pairs, where the key is the LDAP group name and the value is a comma separated list of corresponding role names. For example: group1=role1;group2=role2;group3=role3,role4,role5
-You could also use whitespaces and quotes around group names to make this mapping more readable, for example: 
+You could also use whitespaces and quotes around group names to make this mapping more readable, for example:
 ----
 dbms.security.ldap.authorization.group_to_role_mapping=\
          "cn=Neo4j Read Only,cn=users,dc=example,dc=com"      = reader;    \
@@ -5273,7 +5273,7 @@ label:dynamic[Dynamic]
 |===
 |Description
 a|An authorization mapping from IdP group names to Neo4j role names. The map should be formatted as a semicolon separated list of key-value pairs, where the key is the IdP group name and the value is a comma separated list of corresponding role names. For example: group1=role1;group2=role2;group3=role3,role4,role5
-You could also use whitespaces and quotes around group names to make this mapping more readable, for example: 
+You could also use whitespaces and quotes around group names to make this mapping more readable, for example:
 ----
 dbms.security.oidc.<provider>.authorization.group_to_role_mapping=\
          "Neo4j Read Only"      = reader;    \
@@ -5467,7 +5467,7 @@ a|dbms.security.oidc.<provider>.redirect_uri, a URI
 
 label:dynamic[Dynamic]
 
-.dbms.security.oidc.<provider>.token_endpoint 
+.dbms.security.oidc.<provider>.token_endpoint
 [frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
 |===
 |Description
@@ -5839,7 +5839,7 @@ label:dynamic[Dynamic]
 [frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
 |===
 |Description
-a|Specify if Neo4j should try to preallocate the logical log file in advance. 
+a|Specify if Neo4j should try to preallocate the logical log file in advance.
 It optimizes the filesystem by ensuring there is room to accommodate newly generated files and avoid file-level fragmentation.
 |Valid values
 a|dbms.tx_log.preallocate, a boolean