chore(mono): apply caching suggestion

Author: jstirnaman

content/influxdb3/core/admin/distinct-value-cache/_index.md

@@ -16,4 +16,5 @@ source: /shared/influxdb3-admin/distinct-value-cache/_index.md
 ---
 
 <!-- The content for this page is located at
-// SOURCE content/shared/influxdb3-admin/distinct-value-cache/_index.md -->
+// SOURCE content/shared/influxdb3-admin/distinct-value-cache/_index.md
+-->

content/influxdb3/core/admin/last-value-cache/_index.md

@@ -17,4 +17,5 @@ source: /shared/influxdb3-admin/last-value-cache/_index.md
 ---
 
 <!-- The content for this page is located at
-// SOURCE content/shared/influxdb3-admin/last-value-cache/_index.md -->
+// SOURCE content/shared/influxdb3-admin/last-value-cache/_index.md
+-->

content/shared/influxdb3-admin/distinct-value-cache/_index.md

@@ -8,7 +8,6 @@ in a table. When you create a DVC, you can specify what columns' distinct
 values to cache, the maximum number of distinct value combinations to cache, and
 the maximum age of cached values. A DVC is associated with a table, which can
 have multiple DVCs.
-Caches import historical data when first created and reload data on restart.
 
 {{< children type="anchored-list" >}}
 - [Important things to know about the Distinct Value Cache](#important-things-to-know-about-the-distinct-value-cache)
@@ -69,11 +68,17 @@ similar to this:
 DVCs are stored in memory; the larger the cache, the more memory your InfluxDB 3
 node requires to maintain it. Consider the following:
 
+- [Cache data loading](#cache-data-loading)
 - [High cardinality limits](#high-cardinality-limits)
 {{% show-in "core" %}}
 - [Distinct Value Caches are flushed when the server stops](#distinct-value-caches-are-flushed-when-the-server-stops)
 {{% /show-in %}}
 
+## Cache data loading
+
+On cache creation, {{% product-name %}} loads historical data into the cache.
+On restart, the server automatically reloads cache data.
+
 ### High cardinality limits
 
 “Cardinality” refers to the number of unique key column combinations in your 

content/shared/influxdb3-admin/last-value-cache/_index.md

@@ -10,8 +10,6 @@ what fields to cache, what tags to use to identify each series, and the
 number of values to cache for each unique series.
 An LVC is associated with a table, which can have multiple LVCs.
 
-Caches import historical data when first created and reload data on restart.
-
 {{< children type="anchored-list" >}}
 - [Important things to know about the Last Value Cache](#important-things-to-know-about-the-last-value-cache)
   - [High cardinality key columns](#high-cardinality-key-columns)
@@ -83,11 +81,17 @@ similar to the following:
 LVCs are stored in memory; the larger the cache, the more memory your InfluxDB 3 node requires to
 maintain it. Consider the following:
 
+- [Cache data loading](#cache-data-loading)
 - [High cardinality key columns](#high-cardinality-key-columns)
 - [Value count](#value-count)
 {{% show-in "core" %}}
 - [Last Value Caches are flushed when the server stops](#last-value-caches-are-flushed-when-the-server-stops)
-{{% /show-in %}}lue-columns)
+{{% /show-in %}}
+
+## Cache data loading
+
+On cache creation, {{% product-name %}} loads historical data into the cache.
+On restart, the server automatically reloads cache data.
 
 ### High cardinality key columns