From 52c58b41dab7998a0ed9a2e11ec689ada2bdaba3 Mon Sep 17 00:00:00 2001
From: Matt <85322+mattmassicotte@users.noreply.github.com>
Date: Thu, 9 Feb 2023 18:02:24 -0500
Subject: [PATCH] Clarify non-highlighting usage

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 9d9e86b..1bf0cef 100644
--- a/README.md
+++ b/README.md
@@ -7,13 +7,13 @@
 A Swift library for efficient, flexible content-based text styling.
 
 - Minimal text invalidation
-- Support for multiple sources of highlighting data
+- Support for multiple sources of token data
 - A hybrid sync/async system for targeting flicker-free styling on keystrokes
 - [tree-sitter](https://tree-sitter.github.io/tree-sitter/) integration
 - Compatibility with lazy text loading
 - Text-system agnostic
 
-Neon has a strong focus on efficiency and flexibility. It sits in-between your text system and wherever you get your semantic token information.
+Neon has a strong focus on efficiency and flexibility. It sits in-between your text system and wherever you get your semantic token information. Neon was developed for syntax highlighting and it can serve that need very well. However, it is more general-purpose than that and could be used for any system that needs to style text based its content.
 
 Many people are looking for a drop-in editor View subclass that does it all. This is a lower-level library. You could, however, use Neon to drive highlighting for a view like this.