Fix typos (#938)

docs/01 Top Level API/DragDropContextProvider.md

@@ -69,6 +69,6 @@ export default class YourApp {
 In order to support iframes, we need to be able to inject the window we're subscribing for events in into the HTML5 Backend. You can do this in a couple of ways.
 
 * Via the `window` prop. This has the highest precedent for determining the window to use.
-* Via the `window` context value. This has the next higest precedent.
+* Via the `window` context value. This has the next highest precedent.
 
 If neither of these arguments are present, then the global `window` variable is used.

docs/01 Top Level API/DropTarget.md

@@ -112,7 +112,7 @@ For easier [testing](docs-testing.html), it provides an API to reach into the in
 
 ### Nesting Behavior
 
-If a drop target is nested in another drop target, both `hover()` and `drop()` bubble from the innermost target up the chain. There is no way to cancel the propagation by design. Instead, any drop target may compare `monitor.isOver()` and `monitor.isOver({ shallow: true })` to verify whether a child, or just the current drop target is being hovered. When dropping, any drop target in the chain may check whether it is the first in chain by testing if `monitor.didDrop()` returns `false`. Any parent drop target may override the drop result specified by the child drop target by explicitly returning another drop result from `drop()`. If a parent target returns `undefined` from its `drop()` handler, it does not change the existing drop result that may have been specified by a nested drop target. The drop targets that return `false` from `canDrop()` are exluded from the `drop()` dispatch.
+If a drop target is nested in another drop target, both `hover()` and `drop()` bubble from the innermost target up the chain. There is no way to cancel the propagation by design. Instead, any drop target may compare `monitor.isOver()` and `monitor.isOver({ shallow: true })` to verify whether a child, or just the current drop target is being hovered. When dropping, any drop target in the chain may check whether it is the first in chain by testing if `monitor.didDrop()` returns `false`. Any parent drop target may override the drop result specified by the child drop target by explicitly returning another drop result from `drop()`. If a parent target returns `undefined` from its `drop()` handler, it does not change the existing drop result that may have been specified by a nested drop target. The drop targets that return `false` from `canDrop()` are excluded from the `drop()` dispatch.
 
 ### Handling Files and URLs
 

docs/02 Connecting to DOM/DragSourceConnector.md

@@ -25,9 +25,9 @@ The functions returned by the connector methods also accept options. They need t
 
 * `captureDraggingState`: Optional. A boolean. By default, `false`. If `true`, the component will learn that it is being dragged immediately as the drag starts instead of the next tick. This means that the screenshotting would occur with `monitor.isDragging()` already being `true`, and if you apply any styling like a decreased opacity to the dragged element, this styling will also be reflected on the screenshot. This is rarely desirable, so `false` is a sensible default. However, you might want to set it to `true` in rare cases, such as if you want to make the custom drag layers work in IE and you need to hide the original element without resorting to an empty drag preview which IE doesn't support.
 
-* `anchorX`: Optional. A number betwen `0` and `1`. By default, `0.5`. Specifies how the offset relative to the drag source node is translated into the the horizontal offset of the drag preview when their sizes don't match. `0` means “dock the preview to the left”, `0.5` means “interpolate linearly” and `1` means “dock the preview to the right”.
+* `anchorX`: Optional. A number between `0` and `1`. By default, `0.5`. Specifies how the offset relative to the drag source node is translated into the horizontal offset of the drag preview when their sizes don't match. `0` means “dock the preview to the left”, `0.5` means “interpolate linearly” and `1` means “dock the preview to the right”.
 
-* `anchorY`: Optional. A number betwen `0` and `1`. By default, `0.5`. Specifies how the offset relative to the drag source node is translated into the the vertical offset of the drag preview when their sizes don't match. `0` means “dock the preview to the top, `0.5` means “interpolate linearly” and `1` means “dock the preview to the bottom.
+* `anchorY`: Optional. A number between `0` and `1`. By default, `0.5`. Specifies how the offset relative to the drag source node is translated into the vertical offset of the drag preview when their sizes don't match. `0` means “dock the preview to the top, `0.5` means “interpolate linearly” and `1` means “dock the preview to the bottom.
 
 * `offsetX`: Optional. A number or null if not needed. By default, null. Specifies the vertical offset between the cursor and the drag preview element. If offsetX has a value, anchorX won't be used.
 

packages/dnd-core/README.md

@@ -33,6 +33,6 @@ As it turns out, these problems are much easier to solve when DOM is thrown out
 
 ## What's the API like?
 
-[Tests](https://github.com/react-dnd/dnd-core/tree/master/test) should give you some idea. You register drag sources and drop targets, hook up a backend (you can use barebone `TestBackend` or implement a fancy real one yourself), and your drag sources and drop targets magically begin to interact.
+[Tests](https://github.com/react-dnd/dnd-core/tree/master/test) should give you some idea. You register drag sources and drop targets, hook up a backend (you can use barebones `TestBackend` or implement a fancy real one yourself), and your drag sources and drop targets magically begin to interact.
 
 ![](http://i.imgur.com/6l8CpxZ.png)

packages/react-dnd-html5-backend/README.md

@@ -27,7 +27,7 @@ You may point your Bower config to it.
 
 ## Browser Support
 
-We strive to support the evergreen browsers, Safari 7+, as well as IE11+. IE10 should also work, but `DragLayer` is fairly useless because IE10 doesn’t support `pointer-events: none`. We don’t officialy support IE9 and less.
+We strive to support the evergreen browsers, Safari 7+, as well as IE11+. IE10 should also work, but `DragLayer` is fairly useless because IE10 doesn’t support `pointer-events: none`. We don’t officially support IE9 and less.
 
 Unfortunately the browser bugs, inconsistencies, and regressions come up from time to time, so please make sure you test your app on the browsers you’re interested in, and report any bugs to us.