Index: /trunk/quest-plugin-mfc/src/main/java/de/ugoe/cs/quest/plugin/mfc/guimodel/MFCGUIElementSpec.java
===================================================================
--- /trunk/quest-plugin-mfc/src/main/java/de/ugoe/cs/quest/plugin/mfc/guimodel/MFCGUIElementSpec.java	(revision 714)
+++ /trunk/quest-plugin-mfc/src/main/java/de/ugoe/cs/quest/plugin/mfc/guimodel/MFCGUIElementSpec.java	(revision 715)
@@ -270,5 +270,5 @@
         
         // if the hwnd and the name did not stay the same, then the name should be checked first.
-        // the current name of one of the specs must be contained in the former names of the
+        // The current name of one of the specs must be contained in the former names of the
         // respective other spec for similarity. Either of the specs should contain the name of the
         // respective other spec in its former names. We can rely on this, as in the MFC context
@@ -277,6 +277,5 @@
         // elements, as only one of them may have experienced more name changes then the other.
 
-        if ((otherSpec.name != null) && formerNames.contains(otherSpec.name))
-        {
+        if ((otherSpec.name != null) && formerNames.contains(otherSpec.name)) {
             return true;
         }
@@ -286,5 +285,5 @@
         }
         
-        // ok. Even the names to not match. This is usually a clear indication, that the elements
+        // ok. Even the names do not match. This is usually a clear indication, that the elements
         // are distinct. However, we check, if the former handles matched. This is very unlikely
         // to happen. But it may occur, if a GUI element does not have a name or its name stays