From: Eduardo San Martin Morote <posva13@gmail.com>
Date: Thu, 12 May 2022 09:57:51 +0000 (+0200)
Subject: docs: link
X-Git-Tag: @pinia/nuxt@0.2.0~33
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2a2e6fc79220e4127e4542c12847d6f7cd69b19e;p=thirdparty%2Fvuejs%2Fpinia.git

docs: link

close #1287
---

diff --git a/packages/docs/introduction.md b/packages/docs/introduction.md
index aecc3e8e..4899bee9 100644
--- a/packages/docs/introduction.md
+++ b/packages/docs/introduction.md
@@ -9,7 +9,7 @@ Pinia [started](https://github.com/vuejs/pinia/commit/06aeef54e2cad66696063c6282
 
 ## Why should I use Pinia?
 
-Pinia is a store library for Vue, it allows you to share a state across components/pages. If you are familiar with the Composition API, you might be thinking you can already share a global state with a simple `export const state = reactive({})`. This is true for single page applications but **exposes your application to security vulnerabilities** if it is server side rendered. But even in small single page applications, you get a lot from using Pinia:
+Pinia is a store library for Vue, it allows you to share a state across components/pages. If you are familiar with the Composition API, you might be thinking you can already share a global state with a simple `export const state = reactive({})`. This is true for single page applications but **exposes your application to [security vulnerabilities](https://vuejs.org/guide/scaling-up/ssr.html#cross-request-state-pollution)** if it is server side rendered. But even in small single page applications, you get a lot from using Pinia:
 
 - Devtools support
   - A timeline to track actions, mutations
@@ -86,8 +86,8 @@ const useCounterStore = defineStore('counter', {
   actions: {
     increment() {
       this.count++
-    }
-  }
+    },
+  },
 })
 
 const useUserStore = defineStore('user', {