docs: Fixed Option-Stores link (#2552)

Link under section "What syntax should I pick?"
`#option-stores` changed to `#Option-Stores`

diff --git a/packages/docs/core-concepts/index.md b/packages/docs/core-concepts/index.md
index c8cc37c85c40d4395f800fc29a9d5588e7763d37..981a1cc595cbebd4bb6b242a1a23e6c267c993fd 100644 (file)
--- a/packages/docs/core-concepts/index.md
+++ b/packages/docs/core-concepts/index.md
@@ -70,7 +70,7 @@ In _Setup Stores_:
 
 Note you **must** return **all state properties** in setup stores for pinia to pick them up as state. In other words, you cannot have _private_ state properties in stores. Not returning all state properties can break SSR, devtools, and other plugins.
 
-Setup stores bring a lot more flexibility than [Option Stores](#option-stores) as you can create watchers within a store and freely use any [composable](https://vuejs.org/guide/reusability/composables.html#composables). However, keep in mind that using composables will get more complex when using [SSR](../cookbook/composables.md).
+Setup stores bring a lot more flexibility than [Option Stores](#Option-Stores) as you can create watchers within a store and freely use any [composable](https://vuejs.org/guide/reusability/composables.html#composables). However, keep in mind that using composables will get more complex when using [SSR](../cookbook/composables.md).
 
 Setup stores are also able to rely on globally _provided_ properties like the Router or the Route. Any property [provided at the App level](https://vuejs.org/api/application.html#app-provide) can be accessed from the store using `inject()`, just like in components: