From 040b43ca8a6365df8a11c2e1234a0b64013f93ed Mon Sep 17 00:00:00 2001 From: Victorio Berra <2934507+VictorioBerra@users.noreply.github.com> Date: Sun, 25 May 2025 09:56:08 -0500 Subject: [PATCH] Update getting-started.md --- docs/guide/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/getting-started.md b/docs/guide/getting-started.md index a6fbff244..2defa3dd1 100644 --- a/docs/guide/getting-started.md +++ b/docs/guide/getting-started.md @@ -105,7 +105,7 @@ Every time a validation function (or `ajv.validate`) is called the `errors` prop Ajv can compile efficient parsers and serializers from [JSON Type Definition](../json-type-definition) schemas. -Serializing the data with a function specialized to your data shape can be more than 10x compared with `JSON.stringify`. +Serializing the data with a function specialized to your data shape can be more than 10x faster compared with `JSON.stringify`. Parsing the data replaces the need for separate validation after generic parsing with `JSON.parse` (although validation itself is usually much faster than parsing). In case your JSON string is valid, the specialized parsing is approximately as fast as JSON.parse, but in case your JSON is invalid, the specialized parsing would fail much faster - so it can be very efficient in some scenarios.