diff --git a/docs/en/development/stores.md b/docs/en/development/stores.md
index 9c0978fbd..93928cf18 100644
--- a/docs/en/development/stores.md
+++ b/docs/en/development/stores.md
@@ -76,7 +76,7 @@ As for performance, [according to tests](https://github.com/vuesence/pinia-vs-re
 
 You should also keep in mind that any dependency (in this case the Pinia library) can bring problems similar to the "RIP Vuex" situation when the library dies, becomes obsolete, is no longer supported, or vulnerabilities are found in it. Composable features, on the other hand, look like a thorough innovation to the Vue framework.
 
-Here is an [interesting discussion](https://www.reddit.com/r/vuejs/comments/18fnilj/why_to_use_pinia_instead_of_global_refs/) about it on */r/vuejs*. [Code example](https://github.com/jellyfin/jellyfin-vue/blob/master/frontend/src/store/clientSettings.ts#L98) from Reddit user **@ferferga** shows how to use TypeScript classes with private modifiers, getters, setters (no *.value*) and first class type support as composable stores (which would be impossible with Pinia). Using TS classes here might not be a good practice but demonstrates flexibility and power of the Composition API.
+Here is an [interesting discussion](https://www.reddit.com/r/vuejs/comments/18fnilj/why_to_use_pinia_instead_of_global_refs/) about it on */r/vuejs*. [Code example](https://github.com/jellyfin/jellyfin-vue/tree/master/frontend/src/store) from Reddit user **@ferferga** shows how to use TypeScript classes with private modifiers, getters, setters (no *.value*) and first class type support as composable stores (which would be impossible with Pinia). Using TS classes here might not be a good practice but demonstrates flexibility and power of the Composition API.
 
 Also here is a lifehack for Devtools from user **@coolcosmos**: *I just use refs. The cons is you lose the Devtools but in dev mode I import all my refs and pass them to pinia so I have all the pros and no cons.*