From: Hussain Panahy <144150970+HP8585@users.noreply.github.com>
Date: Wed, 3 Apr 2024 13:15:17 +0000 (+0330)
Subject: docs: improve (#2634)
X-Git-Tag: @pinia/nuxt@0.5.2-beta.0~20
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=98493b5ef4453dbf8c2e4ef03f45e10c23f38b58;p=thirdparty%2Fvuejs%2Fpinia.git

docs: improve (#2634)
---

diff --git a/packages/docs/core-concepts/index.md b/packages/docs/core-concepts/index.md
index d443e8c3..d414568e 100644
--- a/packages/docs/core-concepts/index.md
+++ b/packages/docs/core-concepts/index.md
@@ -68,7 +68,7 @@ In _Setup Stores_:
 - `computed()`s become `getters`
 - `function()`s become `actions`
 
-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](../cookbook/composables.md), devtools, and other plugins.
+Note that 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](../cookbook/composables.md), 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.