From e563d3670a7c62491c3b8a78995614252147c685 Mon Sep 17 00:00:00 2001
From: whoeevee <94960726+whoeevee@users.noreply.github.com>
Date: Thu, 29 Aug 2024 03:46:04 +0300
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index d56295c..169281f 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ If the tweak is unable to find a song or process the lyrics, you'll see a "Could
 
 ## How It Works
 
-**Starting with version 4.0, EeveeSpotify intercepts Spotify requests to load user data, deserializes it, and modifies the parameters in real-time. This method is the best so far and works incredibly stable. You can select the dynamic Premium patching method in the EeveeSpotify settings.**
+**Starting with version 4.0, EeveeSpotify intercepts Spotify requests to load user data, deserializes it, and modifies the parameters in real-time. This method is the best so far and works incredibly stable.**
 
 Upon login, Spotify fetches user data and caches it in the `offline.bnk` file in the `/Library/Application Support/PersistentCache` directory. It uses its proprietary binary format to store data, incorporating a length byte before each value, among other conventions. Certain keys, such as `player-license`, `financial-product`, `streaming-rules`, and others, determine the user abilities.