chore(docs): fix several minor typos in comments

Author: tullmann

docs/locators.md

@@ -102,7 +102,7 @@ element.all(by.css('.selector')).then(function(elements) {
 // Number of elements.
 element.all(locator).count();
 
-// Get my index (starting at 0).
+// Get by index (starting at 0).
 element.all(locator).get(index);
 
 // First and last.

docs/referenceConf.js

@@ -108,7 +108,7 @@ exports.config = {
     browserName: 'chrome',
 
     // Name of the process executing this capability.  Not used directly by
-    // protractor or the browser, but instead pass directly to third patries
+    // protractor or the browser, but instead pass directly to third parties
     // like SauceLabs as the name of the job running this test
     name: 'Unnamed Job',
 

docs/server-setup.md

@@ -69,7 +69,7 @@ In your config file, set these options:
 
 Please note that if you set `sauceUser` and `sauceKey`, the settings for `seleniumServerJar`, `seleniumPort` and `seleniumArgs` will be ignored.
 
-You can optionally set the [`name` property](referenceConf.js#L113) in a capability in order to give the jobs a name on the server.  Otherwise they will just be called `Unanmed Job`.
+You can optionally set the [`name` property](referenceConf.js#L113) in a capability in order to give the jobs a name on the server.  Otherwise they will just be called `Unnamed Job`.
 
 
 Connecting Directly to Browser Drivers

lib/clientsidescripts.js

@@ -651,7 +651,7 @@ functions.setLocation = function(selector, url) {
  * that is not an instance of the Error type into an Error type.  If we
  * don't do so, then the resulting stack trace is completely unhelpful
  * and the exception message is just "unknown error."  These types of
- * exceptins are the common case for dart2js code.  This wrapping gives
+ * exceptions are the common case for dart2js code.  This wrapping gives
  * us the Dart stack trace and exception message.
  */
 var util = require('util');

lib/expectedConditions.js

@@ -23,7 +23,7 @@ var webdriver = require('selenium-webdriver');
  * browser.wait(isClickable, 5000); //wait for an element to become clickable
  * button.click();
  *
- * // You can defined your own expected condition, which is a function that
+ * // You can define your own expected condition, which is a function that
  * // takes no parameter and evaluates to a promise of a boolean.
  * var urlChanged = function() {
  *   return browser.getCurrentUrl().then(function(url) {

plugins/ngHint/index.js

@@ -33,7 +33,7 @@ var q = require('q'),
  */
 
 /*
- * The stratagy for this plugin is as follows:
+ * The strategy for this plugin is as follows:
  *
  * During setup, install the ngHint code and listeners to capture its output.
  * Store the output in the following format: