From 7238c6a82eee2694f8da78b8bf1f345346bd3b3d Mon Sep 17 00:00:00 2001 From: Andrew Fleming Date: Sat, 3 Mar 2018 23:59:14 +0000 Subject: [PATCH] Improve grammar in schemas.md (#1685) Grammar correction --- docs/guides/schemas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/schemas.md b/docs/guides/schemas.md index 1f2609811..3fd5bc97a 100644 --- a/docs/guides/schemas.md +++ b/docs/guides/schemas.md @@ -37,7 +37,7 @@ Hopefully just by reading this definition you'll understand what kinds of blocks This schema defines a document that only allows `paragraph` and `image` blocks. In the case of `paragraph` blocks, they can only contain text nodes. And in the case of `image` blocks, they are always void nodes with a `data.src` property that is a URL. Simple enough, right? -That magic is that by passing a schema like this into your editor, it will automatically "validate" the document when changes are made, to make sure the schema is being adhered to. If it is, great. But if it isn't, and one of the nodes in the document is invalid, the editor will automatically "normalize" the node, to make the document valid again. +The magic is that by passing a schema like this into your editor, it will automatically "validate" the document when changes are made, to make sure the schema is being adhered to. If it is, great. But if it isn't, and one of the nodes in the document is invalid, the editor will automatically "normalize" the node, to make the document valid again. This way you can guarantee that the data is in a format that you expect, so you don't have to handle tons of edge-cases or invalid states in your own code.