Changelog, cleanup for orchestration events change

Author: OverZealous

CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## [2.2.0](https://github.com/OverZealous/run-sequence/releases/tag/v2.2.0) - 2017-09-19
+
+### Changed
+
+- Fixed handling of `orchestration aborted` errors, thanks to [@memoryhole](https://github.com/memoryhole)
+
 ## [2.1.0](https://github.com/OverZealous/run-sequence/releases/tag/v2.1.0) - 2017-07-24
 
 ### Changed

index.js

@@ -104,14 +104,14 @@ function runSequence(gulp) {
 
 	function onGulpError(e) {
 		// In the case that you call gulp.stop after a successful run,
-		// we will not recieve a task_err or task_stop event. This callback
+		// we will not receive a task_err or task_stop event. This callback
 		// will finish the run sequence execution in case of an 'orchestration aborted'
 		// even coming from gulp's global error handler. That event is fired in when
 		// gulp.stop is called.
 		if(e.message === 'orchestration aborted') {
 			finish(e);
 		}
-	};
+	}
 
 	function runNextSet() {
 		if(taskSets.length) {