From 8d2dbdb82c69d116eb5931cb2ee0a4ca5cff6673 Mon Sep 17 00:00:00 2001 From: sajebehari <148820721+sajebehari@users.noreply.github.com> Date: Mon, 10 Jun 2024 17:53:56 -0400 Subject: [PATCH] docs: added punctuation (#6492) --- packages/docs/src/routes/docs/(qwik)/components/state/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/src/routes/docs/(qwik)/components/state/index.mdx b/packages/docs/src/routes/docs/(qwik)/components/state/index.mdx index bd33ead6a1e..acec764c74b 100644 --- a/packages/docs/src/routes/docs/(qwik)/components/state/index.mdx +++ b/packages/docs/src/routes/docs/(qwik)/components/state/index.mdx @@ -529,7 +529,7 @@ Qwik ensures that all application state is always serializable. This is importan Sometimes, it's necessary to store data that can't be serialized; `noSerialize()` instructs Qwik not to attempt serializing the marked value. For example, a reference to a third-party library such as [Monaco editor](https://microsoft.github.io/monaco-editor/) will always need `noSerialize()`, as it is not serializable. -If a value is marked as non-serializable then that value will not survive serialization events such as resuming the application on the client from SSR. In this situation the value will be set to `undefined` and it is up to the developer to re-initialize the value on the client. +If a value is marked as non-serializable, then that value will not survive serialization events, such as resuming the application on the client from SSR. In this situation, the value will be set to `undefined` and it is up to the developer to re-initialize the value on the client. ```tsx /noSerialize/