From 45aba2a51bf627aa080279e59511b4078e92cb16 Mon Sep 17 00:00:00 2001 From: Tim Gates Date: Tue, 1 Sep 2020 06:12:04 +1000 Subject: [PATCH] docs: Fix simple typo, twise -> twice There is a small typo in build/director.js, lib/director/browser.js. Should read `twice` rather than `twise`. --- build/director.js | 4 ++-- lib/director/browser.js | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) 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() {