docs(rules): add emojis

Author: alecxe

docs/rules/array-callback-return.md

@@ -25,7 +25,7 @@ it would not be detected as a violation. Look into having [`array-callback-retur
 
 ## Rule details
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element.all(by.css(".myclass")).filter(function() {
@@ -42,7 +42,7 @@ $$(".myclass").filter(a ? function() {} : function() {});
 $$(".myclass").filter(function(){ return function() {}; }())
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element.all(by.css(".myclass")).filter(function(elm) { 

docs/rules/bare-element-finders.md

@@ -12,7 +12,7 @@ It is easy to forget to actually call an ElementFinder method and the rule would
 ## Rule details
 
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.id('signin_submit_btn'));
@@ -27,7 +27,7 @@ $$(".class1").first().element(by.css(".class2"));
 $(".class1").$(".class2");
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.id('signin_submit_btn')).click();

docs/rules/by-css-shortcut.md

@@ -6,7 +6,7 @@ Recommend using `$` and `$$` shortcuts instead of `element(by.css())` and `eleme
 
 The rule is disabled by default.
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.css(".class"));
@@ -15,7 +15,7 @@ element(by.id("id")).element(by.css(".class"));
 element(by.id("id")).all(by.css(".class"));
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 $(".class");

docs/rules/correct-chaining.md

@@ -17,7 +17,7 @@ element(by.css('.parent')).all(by.css('.child'));
 
 ## Rule details
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.css('.parent')).element.all(by.css('.child'));
@@ -26,7 +26,7 @@ element.all(by.css('.child')).first().element.all(by.css('.child'));
 $$('.parent').first().element.all(by.css('.child'));
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.css('.parent')).all(by.css('.child'));

docs/rules/limit-selector-depth.md

@@ -22,7 +22,7 @@ Number of nodes is configurable, default value is `5`.
 
 This rule is based on [`css-selector-parser`](https://github.com/mdevils/node-css-selector-parser) parsing abilities.
 
-Any use of the following patterns are considered warnings (with the default depth value of `5`):
+:thumbsdown: Any use of the following patterns are considered warnings (with the default depth value of `5`):
 
 ```js
 element(by.css(".content > table > tbody > tr:nth-child(2) > td.cell > input#email"));
@@ -31,7 +31,7 @@ $(".content > table > tbody > tr:nth-child(2) > td.cell > input#email");
 $$(".content > table > tbody > tr:nth-child(2) > td.cell > input#email");
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.css(".myclass"));

docs/rules/missing-perform.md

@@ -7,14 +7,14 @@ Ensure `perform()` is called on `browser.actions()` chain of actions.
 This rule triggers an error if there is no `perform()` at the end of the `browser.actions()` chain. 
 Note that there has to be at least one applied action to trigger the rule. In other words, `var actions = browser.actions();` is considered valid since it is quite a common pattern.
 
-The following patterns are considered errors:
+:thumbsdown: The following patterns are considered errors:
 
 ```js
 browser.actions().click();
 browser.actions().mouseMove(elm);
 ```
 
-The following patterns are not errors:
+:thumbsup: The following patterns are not errors:
 
 ```js
 var actions = browser.actions();

docs/rules/missing-wait-message.md

@@ -7,14 +7,14 @@ Ensure the timeout message is set when `browser.wait()` is called.
 This rule triggers a warning if there is no message in case `browser.wait()` timeouts. 
 Having explicit timeout messages helps in debugging and troubleshooting the test failures.
 
-The following patterns are considered warnings:
+:thumbsdown: The following patterns are considered warnings:
 
 ```js
 browser.wait(EC.presenceOf(elm), 5000);
 browser.wait(EC.visibilityOf(elm), 5000);
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 browser.wait(EC.presenceOf(elm), 5000, "The user menu is not present");

docs/rules/no-absolute-url.md

@@ -7,14 +7,14 @@ This helps to easily switch to a different target application URL by simply chan
 
 ## Rule details
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 browser.get("http://google.com");
 browser.driver.get("https://google.com");
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 browser.get("login");

docs/rules/no-angular-attributes.md

@@ -6,7 +6,7 @@ Ensure attributes used by Angular internally are not used to locate elements via
 
 The rule would scan attributes used inside CSS selectors and would complain about any attribute that starts with `ng-` or `data-ng-` or `x-ng-`.
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.css("[ng-show=test]"));
@@ -20,7 +20,7 @@ element(by.id("id")).$$("[ng-blur^=expression], a[href^=/]");
 element(by.id("id")).$("[data-ng-pattern*='test']");
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.css("input"));

docs/rules/no-angular-classes.md

@@ -16,7 +16,7 @@ Current list of Angular classes this rule would complain about (based on the [CS
  * `ng-touched`
  * `ng-untouched`
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.css(".ng-scope"));
@@ -30,7 +30,7 @@ element(by.id("id")).$$(".ng-touched.myclass");
 element(by.id("id")).$("input.ng-untouched");
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.css(".myclass"));

docs/rules/no-array-finder-methods.md

@@ -10,7 +10,7 @@ Here is the current list of methods the rule is looking for:
 
     'first', 'last', 'get', 'filter', 'map', 'each', 'reduce', 'count'
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.css(".class")).get(0);
@@ -25,7 +25,7 @@ $(".class1").element(by.css(".class2")).first();
 $(".class1").$(".class2").first();
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element.all(by.css(".class")).get(0);

docs/rules/no-bootstrap-classes.md

@@ -9,7 +9,7 @@ Compare these classes with, for example, `product` or `itemPrice` classes - thes
 
 Current list of Bootstrap classes this rule would complain about can be viewed [here](../../lib/bootstrap-layout-classes.js) (hand-picked).
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 element(by.css(".col-lg-12"));
@@ -23,7 +23,7 @@ element(by.id("id")).$$(".col-lg-offset-8.myclass");
 element(by.id("id")).$("input.col-lg-pull-8");
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.css(".myclass"));

docs/rules/no-browser-driver.md

@@ -4,14 +4,14 @@ The rule would warn if using `browser.driver` instead of using `browser` directl
 
 ## Rule details
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 browser.driver.sleep(2000);
 var driver = browser.driver;
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 browser.sleep(1000);

docs/rules/no-browser-pause.md

@@ -7,13 +7,13 @@ Ensure `browser.pause()` is not used.
 `browser.pause()` usage is useful for debugging, but can cause problems in automated environments.
 This rule would issue an error if `browser.pause()` is used.
 
-The following patterns are considered warnings:
+:thumbsdown: The following patterns are considered warnings:
 
 ```js
 browser.pause();
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 browser.notPause();

docs/rules/no-browser-sleep.md

@@ -7,14 +7,14 @@ Ensure `browser.sleep()` is not used.
 `browser.sleep()` usage is usually considered a bad practice and an Explicit Wait via the `browser.wait()` is suggested to be used instead.
 This rule would issue a warning if `browser.sleep()` is used.
 
-The following patterns are considered warnings:
+:thumbsdown: The following patterns are considered warnings:
 
 ```js
 browser.sleep(10);
 browser.sleep(10000);
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 SomeObject.sleep(10);

docs/rules/no-by-xpath.md

@@ -6,14 +6,14 @@ Ensure `by.xpath` locator is not used.
 
 According to the [Protractor's style guide](https://github.com/angular/protractor/blob/master/docs/style-guide.md#never-use-xpath), using `by.xpath` is considered a bad practice. 
 
-The following patterns are considered warnings:
+:thumbsdown: The following patterns are considered warnings:
 
 ```js
 element(by.xpath("//a[starts-with(@href, 'something')]"));
 element.all(by.xpath("//a[starts-with(@href, 'something')]"));
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 element(by.css("a[href^=something]"));

docs/rules/no-compound-classes.md

@@ -6,7 +6,7 @@ Ensure that there are no compound class names (multiple space-delimited classes)
 
 ## Rule details
 
-Any use of the following patterns are considered errors:
+:thumbsdown: Any use of the following patterns are considered errors:
 
 ```js
 element(by.className("class1 class2"));
@@ -15,7 +15,7 @@ element(by.id("myid")).all(by.className("class1 class2 class3"));
 element(by.id("myid")).element(by.className("class1 class2 class3"));
 ```
 
-The following patterns are not errors:
+:thumbsup: The following patterns are not errors:
 
 ```js
 element(by.css("tag1 tag2"));

docs/rules/no-describe-selectors.md

@@ -6,7 +6,7 @@ Ensure raw selectors are not used within `describe` blocks.
 
 As described in [Protractor's documentation](https://github.com/angular/protractor/blob/master/docs/page-objects.md), it is recommended that query selectors be organized within Page Objects in order to keep code cleaner, more reusable, and easier to maintain.
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 describe(function () {
@@ -36,7 +36,7 @@ describe(function () {
 });
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 var AngularHomepage = function() {

docs/rules/no-get-in-it.md

@@ -6,14 +6,14 @@ The rule currently does not allow to configure the test function names and will
 
 ## Rule details
 
-Any use of the following patterns are considered warnings:
+:thumbsdown: Any use of the following patterns are considered warnings:
 
 ```js
 it("should do something", function() { browser.get("mypage"); });
 it("should do something", function() { browser.driver.get("mypage"); });
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 beforeEach(function() { browser.get("mypage"); });

docs/rules/no-get-inner-outer-html.md

@@ -5,7 +5,7 @@ And, hence, [`Protractor` removed them as well in version 5.0.0](https://github.
 
 ## Rule details
 
-Any use of the following patterns are considered errors:
+:thumbsdown: Any use of the following patterns are considered errors:
 
 ```js
 expect(element(by.id("myid")).getInnerHtml()).toEqual("test");
@@ -16,7 +16,7 @@ $$(".class").first().getOuterHtml();
 $(".class").getInnerHtml().then(function (html) { console.log(html) });
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 expect(element(by.id("myid")).getText()).toEqual("test");

docs/rules/no-get-raw-id.md

@@ -5,7 +5,7 @@ Use `getId()` method instead.
 
 ## Rule details
 
-Any use of the following patterns are considered errors:
+:thumbsdown: Any use of the following patterns are considered errors:
 
 ```js
 expect(element(by.id("myid")).getRawId()).toEqual("id");
@@ -15,7 +15,7 @@ $$(".class").first().getRawId();
 $(".class").getRawId().then(function (id) { console.log(id) });
 ```
 
-The following patterns are not warnings:
+:thumbsup: The following patterns are not warnings:
 
 ```js
 expect(element(by.id("myid")).getId()).toEqual("id");

docs/rules/no-invalid-selectors.md

@@ -8,7 +8,7 @@ This rule works great when ESLint is tied up to your editor of choice to make ch
 
 This rule is almost entirely based on [`css-selector-parser`](https://github.com/mdevils/node-css-selector-parser) parsing abilities.
 
-Any use of the following patterns are considered errors:
+:thumbsdown: Any use of the following patterns are considered errors:
 
 ```js
 element(by.css("["));
@@ -22,7 +22,7 @@ element(by.id("id")).$$("input::first-type");
 element(by.id("id")).$("input::first-of--type()");
 ```
 
-The following patterns are not errors:
+:thumbsup: The following patterns are not errors:
 
 ```js
 element(by.css(".myclass"));