From 537eeef539ebfe0b645862b28624b0a1fbfa4159 Mon Sep 17 00:00:00 2001 From: nexushoratio Date: Sun, 29 Dec 2013 04:09:37 -0800 Subject: [PATCH] Fix a number of typos in comments and site content --- code/boot.js | 2 +- code/munge.js | 2 +- code/portal_info.js | 2 +- plugins/portals-list.user.js | 2 +- website/page/faq.php | 2 +- website/page/home.php | 2 +- website/page/news.php | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/code/boot.js b/code/boot.js index 22a59744..e37e909b 100644 --- a/code/boot.js +++ b/code/boot.js @@ -178,7 +178,7 @@ window.setupMap = function() { // faction-specific layers // these layers don't actually contain any data. instead, every time they're added/removed from the map, // the matching sub-layers within the above portals/fields/links are added/removed from their parent with - // the below 'onoverlayadd/onoverlayremovve' events + // the below 'onoverlayadd/onoverlayremove' events var factionLayers = [L.layerGroup(), L.layerGroup(), L.layerGroup()]; for (var fac in factionLayers) { map.addLayer (factionLayers[fac]); diff --git a/code/munge.js b/code/munge.js index 71998845..d9124808 100644 --- a/code/munge.js +++ b/code/munge.js @@ -16,7 +16,7 @@ var requestParameterMunges = [ // the current munge set auto-detection code is working very well. as any site update that breaks that detection // code will also, almost certainly, change the munges in use, it seems pointless keeping this set up to date by hand -// at this time. If that auto-detection breaks, it may be easier to quicky add a munge set by hand than update +// at this time. If that auto-detection breaks, it may be easier to quickly add a munge set by hand than update // the regular expressions, so the list-based code remains available for the future // // set 11 - 2013-12-06 // { diff --git a/code/portal_info.js b/code/portal_info.js index 69958823..a293d8c1 100644 --- a/code/portal_info.js +++ b/code/portal_info.js @@ -68,7 +68,7 @@ window.getLinkAmpRangeBoost = function(d) { // (at the time of writing, only rare link amps have been seen in the wild, so there's a little guesswork at how // the stats work and combine - jon 2013-06-26) - // link amps scale: first is full, second a quarter, the last two an eigth + // link amps scale: first is full, second a quarter, the last two an eighth var scale = [1.0, 0.25, 0.125, 0.125]; var boost = 0.0; // initial boost is 0.0 (i.e. no boost over standard range) diff --git a/plugins/portals-list.user.js b/plugins/portals-list.user.js index 05cbec98..e2c3a786 100644 --- a/plugins/portals-list.user.js +++ b/plugins/portals-list.user.js @@ -150,7 +150,7 @@ window.plugin.portalslist.portalTable = function(sortBy, sortOrder, filter) { } else if (aComp > bComp) { retVal = 1; } else { - // equal - compare GUIDs to ensure consistant (but arbitary) order + // equal - compare GUIDs to ensure consistent (but arbitrary) order retVal = a.guid < b.guid ? -1 : 1; } diff --git a/website/page/faq.php b/website/page/faq.php index e6594cd8..2aa798be 100644 --- a/website/page/faq.php +++ b/website/page/faq.php @@ -80,7 +80,7 @@ date, the full data for every portal on the map was sent to the browser, so IITC various features - resonator search, mitigation highlighters, portal age lists, many highlighters, etc.

-After this date they only send the bare nimimum of data for all the portals on the screen. The data available is: +After this date they only send the bare minimum of data for all the portals on the screen. The data available is: