Merge pull request #718 from nexushoratio/proofreading

Fix a number of typos in comments and site content

code/boot.js

@@ -179,7 +179,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]);

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
 //  {

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)

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;
     }
 

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.
 </p>
 <p>
-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:
 </p>
 <ul>
 <li>Location</li>

website/page/home.php

@@ -19,7 +19,7 @@ Just in time for the holidays, another IITC update. IITC 0.16.1 and IITC Mobile
 Changes include
 </p>
 <ul>
-<li>Portals list plugin returns - but less data than before due to the Niatnic backend changes</li>
+<li>Portals list plugin returns - but less data than before due to the Niantic backend changes</li>
 <li>Resonators plugin returns - but only shows the selected portal</li>
 <li>Mobile:
  <ul>

website/page/news.php

@@ -6,7 +6,7 @@ Just in time for the holidays, another IITC update. IITC 0.16.1 and IITC Mobile
 Changes include
 </p>
 <ul>
-<li>Portals list plugin returns - but less data than before due to the Niatnic backend changes</li>
+<li>Portals list plugin returns - but less data than before due to the Niantic backend changes</li>
 <li>Resonators plugin returns - but only shows the selected portal</li>
 <li>Mobile:
  <ul>