appy suggestions from review

Author: renetapopova

modules/ROOT/pages/database-internals/store-formats.adoc

@@ -554,12 +554,14 @@ The following data is stored for each element:
 * Relationships: a unique ID, one type, a source node, a target node, and a collection of properties.
 * Properties: key-value pairs.
 
+All graph data files are stored under _$NEO4J_HOME/data/databases/databasename_.
+
 [[block-format-store-files]]
 == Block format store files
 
-The block format graph data files are stored under _$NEO4J_HOME/data/databases/databasename_.
-They are organized into a three-store logical structure that adapts to the amount of data stored for each node and relationship.
-The following is an overview of the most important store files, the store they belong to, data they contain, the size of each record, and what they are used for.
+In `block` format, all graph elements are stored in a set of store files with the prefix _block._.
+They are organized into three types of stores that adapt to the amount of data stored for each node and relationship.
+The following is an overview of the most important store files, the store type they belong to, data they contain, the size of each record, and what they are used for.
 
 === Small store
 
@@ -572,7 +574,7 @@ The encoding attempts to fit as much data into this block as possible, typically
 The amount of data that fits depends heavily on the type and size of the data.
 If you have more labels, but no properties or small properties, more labels will fit, and vice versa.
 The same applies to relationships.
-You can fit more relationships if there are fewer properties, and vice versa.
+You can fit more relationships if there are fewer relationship properties, and vice versa.
 Keep in mind that if no data is present, the block still occupies 128 B.
 This block persists as long as the node exists.
 
@@ -596,19 +598,19 @@ The size of this record also adapts to the total size of the relationship data,
 The record in _block.x1.db_ stores a reference to this dynamic record.
 This record can typically contain hundreds of relationships.
 
-=== Dense stores
-
-When the data connected to nodes, relationships, or properties exceeds the capacity of both the small and dynamic stores, the data is stored in the dense store files.
-It is based on a multi-root generational B+ tree structure that allows for efficient storage and retrieval of large amounts of data, where each node has a separate root.
-The following dense store files exist:
-
 _block.big_values.db_::
 All properties of total _size < ~31 B_ are inlined with the node and relationship data in the small or dynamic stores. +
 Properties exceeding 31 B when encoded, typically longer strings or arrays, are stored in this file, and a reference is placed in the value's stead.
 The size of these records adapts to the encoded size of the property value, where the _size = X * 64 B_, with a maximum record size of 8192 B.
 If the encoded size of a property exceeds the maximum record size, the data is split into multiple records and linked together as a linked list.
 See xref:performance/space-reuse.adoc#space-reuse-large-property-values[Reuse of space for large property values in block format] for more details.
 
+=== Dense stores
+
+When the data connected to nodes and relationships exceeds the capacity of both the small and dynamic stores, the data is stored in the dense store files.
+It is based on a multi-root generational B+ tree structure that allows for efficient storage and retrieval of large amounts of data, where each node has a separate root.
+The following dense store files exist:
+
 _block.relationship.dense.db_::
 Relationship dense store holds relationships for nodes with a large number of relationships.
 When the relationship data of a node exceeds the maximum size of the dynamic relationship record, the overflowing relationships are moved to this store.

modules/ROOT/pages/performance/space-reuse.adoc

@@ -44,11 +44,11 @@ If you want to shrink the size of your database, do not delete the _.id_ files.
 The store files must _only_ be modified by the Neo4j database and the `neo4j-admin` tools.
 ====
 
-[role=label--new-2025.12]
+[role=label--new-2026.01]
 [[space-reuse-large-property-values]]
 == Reuse of space for large property values in block format
 
-Starting with Neo4j 2025.12, when allocating a large value of N units, if no such ID is available, the record is split into multiple smaller records.
+Starting with Neo4j 2026.01, when allocating a large value of N units, if no such ID is available, the record is split into multiple smaller records.
 This guarantees the reuse of space for large property values stored in the _block.big_values.db_ store file, sacrificing colocation in some cases.
 The level of accepted fragmentation is dynamic and depends on the fraction of unused records, i.e., no fragmentation if < 5% of the space is unused, then accepting some fragmentation for a bit higher unused percentage.
 If the unused percentage is high, records can be even more fragmented.