Rename cleanup in comments in css/ directory.

third_party/WebKit/Source/core/css/CSSSelector.h

 /*
  * Copyright (C) 1999-2003 Lars Knoll (knoll@kde.org)
  *               1999 Waldo Bastian (bastian@kde.org)
  * Copyright (C) 2004, 2006, 2007, 2008, 2009, 2010, 2013 Apple Inc. All rights
  * reserved.
  *
  * This library is free software; you can redistribute it and/or
  * modify it under the terms of the GNU Library General Public
  * License as published by the Free Software Foundation; either
  * version 2 of the License, or (at your option) any later version.
@@ skipping 20 matching lines @@
 
 namespace blink {
 class CSSSelectorList;
 
 // This class represents a selector for a StyleRule.
 
 // CSS selector representation is somewhat complicated and subtle. A
 // representative list of selectors is in CSSSelectorTest; run it in a debug
 // build to see useful debugging output.
 //
-// ** tagHistory() and relation():
+// ** TagHistory() and Relation():
 //
 // Selectors are represented as a linked list of simple selectors (defined more
 // or less according to
 // http://www.w3.org/TR/css3-selectors/#simple-selectors-dfn). The tagHistory()
 // method returns the next simple selector in the list. The relation() method
 // returns the relationship of the current simple selector to the one in
 // tagHistory(). For example, the CSS selector .a.b #c is represented as:
 //
-// selectorText(): .a.b #c
-// --> (relation == Descendant)
-//   selectorText(): .a.b
-//   --> (relation == SubSelector)
-//     selectorText(): .b
+// SelectorText(): .a.b #c
+// --> (relation == kDescendant)
+//   SelectorText(): .a.b
+//   --> (relation == kSubSelector)
+//     SelectorText(): .b
 //
 // The order of tagHistory() varies depending on the situation.
 // * Relations using combinators
 //   (http://www.w3.org/TR/css3-selectors/#combinators), such as descendant,
 //   sibling, etc., are parsed right-to-left (in the example above, this is why
 //   #c is earlier in the tagHistory() chain than .a.b).
 // * SubSelector relations are parsed left-to-right in most cases (such as the
 //   .a.b example above); a counter-example is the
 //   ::content pseudo-element. Most (all?) other pseudo elements and pseudo
 //   classes are parsed left-to-right.
@@ skipping 470 matching lines @@
 }
 
 inline bool CSSSelector::IsIdClassOrAttributeSelector() const {
   return IsAttributeSelector() || Match() == CSSSelector::kId ||
          Match() == CSSSelector::kClass;
 }
 
 }  // namespace blink
 
 #endif  // CSSSelector_h