Fix cmp documentation.

Also make it clearer that example is referring to arbitrary variables,
not dex bytecode fields.

Bug: http://code.google.com/p/android/issues/detail?id=35751
Change-Id: Iea467ed8d5ff1b1d8c9665357cdbd36854f0850f

1 files changed, 8 insertions, 8 deletions

diff --git a/src/tech/dalvik/dalvik-bytecode.html b/src/tech/dalvik/dalvik-bytecode.html
index 66c9c488..e848d9ee 100644
--- a/src/tech/dalvik/dalvik-bytecode.html
+++ b/src/tech/dalvik/dalvik-bytecode.html
@@ -598,18 +598,18 @@
     <code>B:</code> first source register or pair<br/>
     <code>C:</code> second source register or pair</td>
   <td>Perform the indicated floating point or <code>long</code> comparison,
-    storing <code>0</code> if the two arguments are equal, <code>1</code>
-    if the second argument is larger, or <code>-1</code> if the first
-    argument is larger. The "bias" listed for the floating point operations
-    indicates how <code>NaN</code> comparisons are treated: "Gt bias"
+    setting <code>a</code> to <code>0</code> if <code>b == c</code>,
+    <code>1</code> if <code>b &gt; c</code>,
+    or <code>-1</code> if <code>b &lt; c</code>.
+    The "bias" listed for the floating point operations
+    indicates how <code>NaN</code> comparisons are treated: "gt bias"
     instructions return <code>1</code> for <code>NaN</code> comparisons,
-    and "lt bias" instructions return
-    <code>-1</code>.
+    and "lt bias" instructions return <code>-1</code>.
     <p>For example, to check to see if floating point
-    <code>a &lt; b</code>, then it is advisable to use
+    <code>x &lt; y</code> it is advisable to use
     <code>cmpg-float</code>; a result of <code>-1</code> indicates that
     the test was true, and the other values indicate it was false either
-    due to a valid comparison or because one or the other values was
+    due to a valid comparison or because one of the values was
     <code>NaN</code>.</p>
   </td>
 </tr>