From f86f5ca065d9c660b141be9b12bfa6105cda8bf9 Mon Sep 17 00:00:00 2001 From: Charanjit Singh Date: Wed, 11 Mar 2020 20:41:42 +0530 Subject: [PATCH] Fix Typo (#3545) Typo fix in documentation --- docs/concepts/10-normalizing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/10-normalizing.md b/docs/concepts/10-normalizing.md index 89dd3205a..931e1bcc5 100644 --- a/docs/concepts/10-normalizing.md +++ b/docs/concepts/10-normalizing.md @@ -16,7 +16,7 @@ Slate editors come with a few built-in constraints out of the box. These constra 4. **The top-level editor node can only contain block nodes.** If any of the top-level children are inline or text nodes they will be removed. This ensures that there are always block nodes in the editor so that behaviors like "splitting a block in two" work as expected. -These default constraints are all mandated because they make working with Slate documents _much_ more preditable. +These default constraints are all mandated because they make working with Slate documents _much_ more predictable. > 🤖 Although these constraints are the best we've come up with now, we're always looking for ways to have Slate's built-in constraints be less constraining if possible—as long as it keeps standard behaviors easy to reason about. If you come up with a way to reduce or remove a built-in constraint with a different approach, we're all ears!