From df8e536f24d9e7b2cd341b09d6c06dc5c1a3dd72 Mon Sep 17 00:00:00 2001 From: Ian Storm Taylor Date: Mon, 11 Jul 2016 13:40:46 -0700 Subject: [PATCH] update docs --- docs/reference/components/editor.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/reference/components/editor.md b/docs/reference/components/editor.md index 0db7a60ad..97cd3ae09 100644 --- a/docs/reference/components/editor.md +++ b/docs/reference/components/editor.md @@ -33,9 +33,7 @@ These properties are actually an implicit plugin defintion. Internally, they are #### `onChange(state)` -A change handler that will be called with the newly-changed editor `state`. You should usually pass the newly changed `state` back into the editor through its `state` property. - -This is how you can add persistence logic to your editor. +A change handler that will be called with the newly-changed editor `state`. You should usually pass the newly changed `state` back into the editor through its `state` property. This hook allows you to add persistence logic to your editor. #### `plugins` @@ -47,9 +45,7 @@ A [`State`](../models/state) object representing the current state of the editor #### `...` -All of the other properties of the editor are equivalent to the properties of a [`Plugin`](../plugins). - -They are convenience properties, treated equivalently to passing them as the first plugin in the plugin stack. For example: +All of the other properties of the editor are equivalent to the properties of a [`Plugin`](../plugins). They are convenience properties, treated equivalently to passing them as the first plugin in the plugin stack. For example: ```js const plugins = [somePlugin]