docs: update Solana network page to SVM

[devin-ai-integration]

Description

Renames the Solana network page to SVM (Solana Virtual Machine) to align with the EVM naming convention used for Ethereum chains. Changes include:

• Renamed appkit/networks/solana.mdx → appkit/networks/svm.mdx with updated title and heading
• Updated sidebar navigation in docs.json to reference the new path
• Added a redirect from /appkit/networks/solana → /appkit/networks/svm to preserve existing links
• Updated the features overview table label from "Solana" to "SVM (Solana)"

Key things to review:

• Does the SVM naming/terminology match what's intended? The page follows the same pattern as the EVM page.
• The redirect should handle any existing external links to /appkit/networks/solana.
• The page content is minimal — confirm whether additional SVM-specific details are needed.
• The video asset still references /images/Solana.mp4 (unchanged, content is the same).

Verified locally:

SVM Chains page:

Features Overview table:

Requested by: @magiziz
Link to Devin run

Tests

• - Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
• - Ran a grammar check on the updated/created content using ChatGPT.

Direct link to the deployed preview files

• SVM Chains page
• Features Overview

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[claude]

Claude finished @devin-ai-integration[bot]'s task in 1m 13s —— View job

---

Review Complete

• Read tone of voice guidance
• Read changed files
• Review changes against origin/main
• Check automated rules (PR size, external URLs, etc.)
• Evaluate tone of voice compliance
• Check technical accuracy and consistency
• Post final review

---

Found 1 issue(s)

Issue 1: Potentially misleading "SVM chains" terminology

ID: svm-terminology-chains-plural-8a4f
File: appkit/networks/svm.mdx:6
Severity: MEDIUM
Category: code_quality

Context:

• Pattern: Documentation refers to "SVM (Solana Virtual Machine) chains" (plural) and "SVM Chains" in headings
• Risk: Unlike EVM which runs on multiple independent chains (Ethereum, Polygon, Arbitrum, etc.), SVM currently only runs on Solana mainnet and its testnets - there are no multiple independent "SVM chains"
• Impact: Users may expect multiple SVM-based blockchains similar to the EVM ecosystem, creating confusion about what networks are actually supported
• Trigger: Any user reading this documentation and comparing to the EVM page

Recommendation: Consider these alternatives:

1. Use "SVM (Solana)" to match the table entry
2. Use "Solana Network" or "Solana Support"
3. If future SVM-compatible chains are planned (e.g., Eclipse, Nitro), document them explicitly

Current state suggests supporting multiple SVM chains when only Solana is supported. Either clarify this is Solana-specific or document plans for additional SVM networks.

Example fix:

---
title: SVM (Solana)
sidebarTitle: Solana
---

## Solana Support

The AppKit SDK supports Solana via the SVM (Solana Virtual Machine), allowing users to connect their Solana wallets to applications.

---

Summary

PR successfully renames Solana documentation to use SVM terminology, following the EVM naming pattern. Changes are minimal, redirect is properly configured, and tone of voice aligns with Reown standards.

Key observations:

• ✅ Redirect configured correctly at docs.json:61-63
• ✅ Navigation updated to reference new path
• ✅ Features table updated with clear labeling "SVM (Solana)"
• ⚠️ "SVM chains" (plural) may be technically inaccurate - currently only Solana uses SVM, unlike EVM which has many chains

Recommendation: Verify whether "SVM chains" terminology reflects actual multi-chain support or planned expansion. If this is Solana-only, consider using "Solana" or "SVM (Solana)" consistently rather than "SVM Chains."

[github-actions]

🤖 Auto Review Issue: Potentially misleading "SVM chains" terminology

Severity: MEDIUM
Category: code_quality
Tool: Claude Auto Review

Context:

• Pattern: Documentation refers to "SVM (Solana Virtual Machine) chains" (plural) and "SVM Chains" in headings
• Risk: Unlike EVM which runs on multiple independent chains (Ethereum, Polygon, Arbitrum, etc.), SVM currently only runs on Solana mainnet and its testnets - there are no multiple independent "SVM chains"
• Impact: Users may expect multiple SVM-based blockchains similar to the EVM ecosystem, creating confusion about what networks are actually supported
• Trigger: Any user reading this documentation and comparing to the EVM page

Recommendation: Consider these alternatives:

1. Use "SVM (Solana)" to match the table entry
2. Use "Solana Network" or "Solana Support"
3. If future SVM-compatible chains are planned (e.g., Eclipse, Nitro), document them explicitly

Current state suggests supporting multiple SVM chains when only Solana is supported. Either clarify this is Solana-specific or document plans for additional SVM networks.