From 9ac3066fe19052bd9aa15d454bc97ab7e52e4a4f Mon Sep 17 00:00:00 2001 From: KaifAhmad1 Date: Thu, 2 Jul 2026 13:24:16 +0530 Subject: [PATCH] docs: fix node-count inconsistency in performance warning --- docs/guides/visualization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/visualization.md b/docs/guides/visualization.md index a4638923..75bbe861 100644 --- a/docs/guides/visualization.md +++ b/docs/guides/visualization.md @@ -69,7 +69,7 @@ Most effective visualization follows this pattern: Always filter before visualizing. A 10,000-node enterprise graph becomes meaningful when filtered to the 50 most central nodes or the subgraph around a specific entity of interest. - **Performance Warning:** Large graphs (>1000 nodes) cause browser performance issues and become visually overwhelming. Interactive network visualizations work best with 10-500 nodes. For larger graphs, use analytics to identify the most important subgraphs, then visualize those filtered results. + **Performance Warning:** Large graphs (>1000 nodes) cause browser performance issues and become visually overwhelming. Interactive network visualizations work best with 10-1000 nodes. For larger graphs, use analytics to identify the most important subgraphs, then visualize those filtered results.