From 0a2d68a97faba7a9bf2368da21ead19c4c9f9292 Mon Sep 17 00:00:00 2001 From: Mateo Ochoa Date: Tue, 3 Apr 2018 03:31:20 -0700 Subject: [PATCH] Update faq.md (#1750) --- docs/general/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/general/faq.md b/docs/general/faq.md index 34d28ae87..9d90ed22a 100644 --- a/docs/general/faq.md +++ b/docs/general/faq.md @@ -10,7 +10,7 @@ A series of common questions people have about Slate: One of Slate's core principles is that, unlike most other editors, it does **not** prescribe a specific "schema" to the content you are editing. This means that Slate's core has no concept of "block quotes" or "bold formatting". -For this most part, this leads to increased flexbility without many downsides, but there are certain cases where you have to do a bit more work. Pasting is one of those cases. +For the most part, this leads to increased flexbility without many downsides, but there are certain cases where you have to do a bit more work. Pasting is one of those cases. Since Slate knows nothing about your schema, it can't know how to parse pasted HTML content (or other content). So, by default whenever a user pastes content into a Slate editor, it will parse it as plain text. If you want it to be smarter about pasted content, you need to define an [`onPaste`](../reference/slate-react/editor.md#onpaste) handler that parses the content as you wish.