Add two links to surreal start, specify that many points pertain to versioned SurrealKV

Author: Dhghomon

src/content/doc-surrealkv/index.mdx

@@ -36,7 +36,7 @@ SurrealKV offers several key features that makes it a powerful and versatile dat
 
 - **Embedded Database**: SurrealKV is available for embedded environments.
 
-- **Built-in Versioning**: Track and access historical versions of your data.
+- **Built-in Versioning**: Start SurrealKV [in versioned mode](/docs/surrealdb/cli/start#surrealkv-beta) to track and access historical versions of your data.
 
 - **Compaction**: Efficient storage management through compaction.
 

src/content/doc-surrealkv/performance.mdx

@@ -5,7 +5,7 @@ title: Performance characteristics | SurrealQL
 description: Learn about the performance characteristics of SurrealQL and how it optimizes query execution and resource usage in SurrealDB.
 ---
 
-# Performance characteristics and trade-offs
+# SurrealKV performance characteristics and trade-offs
 
 ## Strengths
 
@@ -21,15 +21,15 @@ Operationally, SurrealKV offers significant advantages. The compaction process r
 
 ## Limitations
 
-SurrealKV does have some important limitations to consider:
+SurrealKV does have some important limitations to consider, many of which pertain to SurrealKV [when versioning is enabled](/docs/surrealdb/cli/start#surrealkv-beta):
 
-Memory management is a key consideration, as the index must reside in memory. Memory usage scales with the number of unique keys, key size distribution, and the number of versions per key.
+* Memory management is a key consideration, as the index must reside in memory. Memory usage scales with the number of unique keys, key size distribution, and the number of versions per key.
 
-Write amplification is another factor to consider. Each update creates a new version, requiring periodic compaction. During compaction, space usage temporarily increases.
+* Write amplification is another factor to consider. Each update creates a new version, requiring periodic compaction. During compaction, space usage temporarily increases.
 
-Range query performance varies depending on several factors: key distribution, version history depth, and range size. Large ranges may require multiple disk reads to complete.
+* Range query performance varies depending on several factors: key distribution, version history depth, and range size. Large ranges may require multiple disk reads to complete.
 
-From an operational standpoint, regular compaction is necessary for space reclamation. System restart time increases with log size, and high-cardinality keyspaces can create memory pressure.
+* From an operational standpoint, regular compaction is necessary for space reclamation. System restart time increases with log size, and high-cardinality keyspaces can create memory pressure.
 
 ## Performance implications