diff --git a/build/director.js b/build/director.js
index 1038878..97eeb70 100644
--- a/build/director.js
+++ b/build/director.js
@@ -66,7 +66,7 @@ var listener = {
       if (this.history === true) {
         // There is an old bug in Chrome that causes onpopstate to fire even
         // upon initial page load. Since the handler is run manually in init(),
-        // this would cause Chrome to run it twise. Currently the only
+        // this would cause Chrome to run it twice. Currently the only
         // workaround seems to be to set the handler after the initial page load
         // http://code.google.com/p/chromium/issues/detail?id=63040
         setTimeout(function() {
@@ -722,4 +722,4 @@ Router.prototype.mount = function(routes, path) {
 
 
 
-}(typeof exports === "object" ? exports : window));
\ No newline at end of file
+}(typeof exports === "object" ? exports : window));
diff --git a/lib/director/browser.js b/lib/director/browser.js
index 1e47293..3befc6a 100644
--- a/lib/director/browser.js
+++ b/lib/director/browser.js
@@ -57,7 +57,7 @@ var listener = {
       if (this.history === true) {
         // There is an old bug in Chrome that causes onpopstate to fire even
         // upon initial page load. Since the handler is run manually in init(),
-        // this would cause Chrome to run it twise. Currently the only
+        // this would cause Chrome to run it twice. Currently the only
         // workaround seems to be to set the handler after the initial page load
         // http://code.google.com/p/chromium/issues/detail?id=63040
         setTimeout(function() {