From 1d8c814a622b2705715ffe2284ea13fd691c07dd Mon Sep 17 00:00:00 2001
From: Anuj <oyeanuj@users.noreply.github.com>
Date: Thu, 2 Mar 2017 17:17:55 -0800
Subject: [PATCH] Fix typo: cummulative -> cumulative (#643)

---
 docs/reference/plugins/plugin.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reference/plugins/plugin.md b/docs/reference/plugins/plugin.md
index 2e99ede89..2035e3377 100644
--- a/docs/reference/plugins/plugin.md
+++ b/docs/reference/plugins/plugin.md
@@ -205,7 +205,7 @@ _Note: This is **not** Slate's internal selection representation (although it mi
 
 The `onChange` handler isn't a native browser event handler. Instead, it is invoked whenever the editor state changes. Returning a new state will update the editor's state, continuing down the plugin stack.
 
-Unlike the native event handlers, results from the `onChange` handler **are cummulative**! This means that every plugin in the stack that defines an `onChange` handler will have its handler resolved for every change the editor makes; the editor will not return early after the first plugin's handler is called.
+Unlike the native event handlers, results from the `onChange` handler **are cumulative**! This means that every plugin in the stack that defines an `onChange` handler will have its handler resolved for every change the editor makes; the editor will not return early after the first plugin's handler is called.
 
 This allows you to stack up changes across the entire plugin stack.