From 79779796b196b852db1f62c59690764b0f6f886c Mon Sep 17 00:00:00 2001
From: bicarus <202771338+bicarus-dev@users.noreply.github.com>
Date: Sun, 6 Sep 2026 22:44:29 -0700
Subject: [PATCH] Updated Spice SDK (markdown)

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

diff --git a/Spice-SDK.md b/Spice-SDK.md
index 8f1a34b..fe1dc3b 100644
--- a/Spice-SDK.md
+++ b/Spice-SDK.md
@@ -1,8 +1,8 @@
 Spice SDK is a flat C, header-only library that can be included in your hook DLL to write **spice plugins**.
 
-Once initialized, you can call directly into helper routines provided by Spicetools executable, making low-latency and high-throughput interactions possible. There are no network packets or JSON marshalling; it's just function pointers.
+Once initialized, the plugin call directly into helper routines provided by Spicetools executable, making low-latency and high-throughput interactions possible. There are no network packets or JSON marshalling; it's just function pointers.
 
-This is meant to be an alternative to writing applications over Spice API; as the API uses JSON over the network (or serial), there are issues with performance, latency, and reliability.
+Plugins are meant to be an alternative to writing applications over Spice API; as the API uses JSON over the network (or serial), there are issues with performance, latency, and reliability.
 
 For example, you could write a DLL that communicates to your custom controller over COM, knowing that if you call `set_button` from your DLL, it will be consumed by Spice the next time the game polls for I/O.