Docs: Updates to style of "Note: "
Bug: #19015769
Change-Id: I21624e95b47d8c13618ca288d137e7f19001982f
diff --git a/src/devices/tech/dalvik/dalvik-bytecode.jd b/src/devices/tech/dalvik/dalvik-bytecode.jd
index 5695440..f449bce 100644
--- a/src/devices/tech/dalvik/dalvik-bytecode.jd
+++ b/src/devices/tech/dalvik/dalvik-bytecode.jd
@@ -174,7 +174,7 @@
<td>nop</td>
<td> </td>
<td>Waste cycles.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
Data-bearing pseudo-instructions are tagged with this opcode, in which
case the high-order byte of the opcode unit indicates the nature of
the data. See "<code>packed-switch-payload</code> Format",
@@ -209,7 +209,7 @@
<td><code>A:</code> destination register pair (4 bits)<br/>
<code>B:</code> source register pair (4 bits)</td>
<td>Move the contents of one register-pair to another.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
It is legal to move from <code>v<i>N</i></code> to either
<code>v<i>N-1</i></code> or <code>v<i>N+1</i></code>, so implementations
must arrange for both halves of a register pair to be read before
@@ -222,7 +222,7 @@
<td><code>A:</code> destination register pair (8 bits)<br/>
<code>B:</code> source register pair (16 bits)</td>
<td>Move the contents of one register-pair to another.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
Implementation considerations are the same as <code>move-wide</code>,
above.</p>
</td>
@@ -233,7 +233,7 @@
<td><code>A:</code> destination register pair (16 bits)<br/>
<code>B:</code> source register pair (16 bits)</td>
<td>Move the contents of one register-pair to another.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
Implementation considerations are the same as <code>move-wide</code>,
above.</p>
</td>
@@ -425,7 +425,7 @@
<td>monitor-exit vAA</td>
<td><code>A:</code> reference-bearing register (8 bits)</td>
<td>Release the monitor for the indicated object.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
If this instruction needs to throw an exception, it must do
so as if the pc has already advanced past the instruction.
It may be useful to think of this as the instruction successfully
@@ -446,7 +446,7 @@
<code>B:</code> type index (16 bits)</td>
<td>Throw a <code>ClassCastException</code> if the reference in the
given register cannot be cast to the indicated type.
- <p><b>Note:</b> Since <code>A</code> must always be a reference
+ <p class="note"><strong>Note:</strong> Since <code>A</code> must always be a reference
(and not a primitive value), this will necessarily fail at runtime
(that is, it will throw an exception) if <code>B</code> refers to a
primitive type.</p>
@@ -461,7 +461,7 @@
<td>Store in the given destination register <code>1</code>
if the indicated reference is an instance of the given type,
or <code>0</code> if not.
- <p><b>Note:</b> Since <code>B</code> must always be a reference
+ <p class="note"><strong>Note:</strong> Since <code>B</code> must always be a reference
(and not a primitive value), this will always result
in <code>0</code> being stored if <code>C</code> refers to a primitive
type.</td>
@@ -547,7 +547,7 @@
<td>goto +AA</td>
<td><code>A:</code> signed branch offset (8 bits)</td>
<td>Unconditionally jump to the indicated instruction.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
The branch offset must not be <code>0</code>. (A spin
loop may be legally constructed either with <code>goto/32</code> or
by including a <code>nop</code> as a target before the branch.)</p>
@@ -558,7 +558,7 @@
<td>goto/16 +AAAA</td>
<td><code>A:</code> signed branch offset (16 bits)<br/></td>
<td>Unconditionally jump to the indicated instruction.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
The branch offset must not be <code>0</code>. (A spin
loop may be legally constructed either with <code>goto/32</code> or
by including a <code>nop</code> as a target before the branch.)</p>
@@ -640,7 +640,7 @@
<code>C:</code> signed branch offset (16 bits)</td>
<td>Branch to the given destination if the given two registers' values
compare as specified.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
The branch offset must not be <code>0</code>. (A spin
loop may be legally constructed either by branching around a
backward <code>goto</code> or by including a <code>nop</code> as
@@ -661,7 +661,7 @@
<code>B:</code> signed branch offset (16 bits)</td>
<td>Branch to the given destination if the given register's value compares
with 0 as specified.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
The branch offset must not be <code>0</code>. (A spin
loop may be legally constructed either by branching around a
backward <code>goto</code> or by including a <code>nop</code> as
@@ -723,7 +723,7 @@
<code>C:</code> instance field reference index (16 bits)</td>
<td>Perform the identified object instance field operation with
the identified field, loading or storing into the value register.
- <p><b>Note:</b> These opcodes are reasonable candidates for static linking,
+ <p class="note"><strong>Note:</strong> These opcodes are reasonable candidates for static linking,
altering the field argument to be a more direct offset.</p>
</td>
</tr>
@@ -750,7 +750,7 @@
<code>B:</code> static field reference index (16 bits)</td>
<td>Perform the identified object static field operation with the identified
static field, loading or storing into the value register.
- <p><b>Note:</b> These opcodes are reasonable candidates for static linking,
+ <p class="note"><strong>Note:</strong> These opcodes are reasonable candidates for static linking,
altering the field argument to be a more direct offset.</p>
</td>
</tr>
@@ -788,7 +788,7 @@
<code>interface</code> method, that is, on an object whose concrete
class isn't known, using a <code>method_id</code> that refers to
an <code>interface</code>.</p>
- <p><b>Note:</b> These opcodes are reasonable candidates for static linking,
+ <p class="note"><strong>Note:</strong> These opcodes are reasonable candidates for static linking,
altering the method argument to be a more direct offset
(or pair thereof).</p>
</td>
@@ -955,7 +955,7 @@
<td>Perform the indicated binary op on the indicated register (first
argument) and literal value (second argument), storing the result in
the destination register.
- <p><b>Note:</b>
+ <p class="note"><strong>Note:</strong>
<code>rsub-int</code> does not have a suffix since this version is the
main opcode of its family. Also, see below for details on its semantics.
</p>
@@ -982,7 +982,7 @@
<td>Perform the indicated binary op on the indicated register (first
argument) and literal value (second argument), storing the result
in the destination register.
- <p><b>Note:</b> See below for details on the semantics of
+ <p class="note"><strong>Note:</strong> See below for details on the semantics of
<code>rsub-int</code>.</p>
</td>
</tr>
@@ -1031,7 +1031,7 @@
</tbody>
</table>
-<p><b>Note:</b> The total number of code units for an instance of this
+<p class="note"><strong>Note:</strong> The total number of code units for an instance of this
table is <code>(size * 2) + 4</code>.</p>
<h2 id="sparse-switch">sparse-switch-payload format</h2>
@@ -1071,7 +1071,7 @@
</tbody>
</table>
-<p><b>Note:</b> The total number of code units for an instance of this
+<p class="note"><strong>Note:</strong> The total number of code units for an instance of this
table is <code>(size * 4) + 2</code>.</p>
<h2 id="fill-array">fill-array-data-payload format</h2>
@@ -1108,13 +1108,13 @@
</tbody>
</table>
-<p><b>Note:</b> The total number of code units for an instance of this
+<p class="note"><strong>Note:</strong> The total number of code units for an instance of this
table is <code>(size * element_width + 1) / 2 + 4</code>.</p>
<h2 id="math">Mathematical operation details</h2>
-<p><b>Note:</b> Floating point operations must follow IEEE 754 rules, using
+<p class="note"><strong>Note:</strong> Floating point operations must follow IEEE 754 rules, using
round-to-nearest and gradual underflow, except where stated otherwise.</p>
<table class="math">
diff --git a/src/devices/tech/dalvik/dex-format.jd b/src/devices/tech/dalvik/dex-format.jd
index bd167fb..9b7a6a2 100644
--- a/src/devices/tech/dalvik/dex-format.jd
+++ b/src/devices/tech/dalvik/dex-format.jd
@@ -275,7 +275,7 @@
= "dex\n035\0"
</pre>
-<p><b>Note:</b> At least a couple earlier versions of the format have
+<p class="note"><strong>Note:</strong> At least a couple earlier versions of the format have
been used in widely-available public software releases. For example,
version <code>009</code> was used for the M3 releases of the
Android platform (November–December 2007),
@@ -306,10 +306,10 @@
<p>The constant <code>NO_INDEX</code> is used to indicate that
an index value is absent.</p>
-<p><b>Note:</b> This value isn't defined to be
+<p class="note"><strong>Note:</strong> This value isn't defined to be
<code>0</code>, because that is in fact typically a valid index.</p>
-<p><b>Also Note:</b> The chosen value for <code>NO_INDEX</code> is
+<p>The chosen value for <code>NO_INDEX</code> is
representable as a single byte in the <code>uleb128p1</code> encoding.</p>
<pre>
@@ -381,8 +381,8 @@
<td> </td>
<td> </td>
<td><code>synchronized</code>: associated lock automatically acquired
- around call to this method. <b>Note:</b> This is only valid to set when
- <code>ACC_NATIVE</code> is also set.</td>
+ around call to this method. <p class="note"><strong>Note:</strong> This is only valid to set when
+ <code>ACC_NATIVE</code> is also set. </p></td>
</tr>
<tr>
<td>ACC_VOLATILE</td>
@@ -482,8 +482,8 @@
<td>0x20000</td>
<td> </td>
<td> </td>
- <td>declared <code>synchronized</code>. <b>Note:</b> This has no effect on
- execution (other than in reflection of this flag, per se).
+ <td>declared <code>synchronized</code>. <p class="note"><strong>Note:</strong> This has no effect on
+ execution (other than in reflection of this flag, per se).</p>
</td>
</tr>
</tbody>
@@ -1567,7 +1567,7 @@
followed by a byte of value <code>0</code>. See
"MUTF-8 (Modified UTF-8) Encoding" above for details and
discussion about the data format.
- <p><b>Note:</b> It is acceptable to have a string which includes
+ <p class="note"><strong>Note:</strong> It is acceptable to have a string which includes
(the encoded form of) UTF-16 surrogate code units (that is,
<code>U+d800</code> … <code>U+dfff</code>)
either in isolation or out-of-order with respect to the usual
@@ -1897,7 +1897,7 @@
</tbody>
</table>
-<p><b>Note:</b> All elements' <code>field_id</code>s and
+<p class="note"><strong>Note:</strong> All elements' <code>field_id</code>s and
<code>method_id</code>s must refer to the same defining class.</p>
<h3 id="encoded-field-format">encoded_field format</h3>
@@ -2381,7 +2381,7 @@
to indicate that that value is unknown. (If <code>sig_idx</code> is
<code>-1</code>, though, the same data could be represented more
efficiently using the opcode <code>DBG_START_LOCAL</code>.)
- <p><b>Note:</b> See the discussion under
+ <p class="note"><strong>Note:</strong> See the discussion under
"<code>dalvik.annotation.Signature</code>" below for caveats about
handling signatures.</p>
</td>
@@ -2538,7 +2538,7 @@
</tbody>
</table>
-<p><b>Note:</b> All elements' <code>field_id</code>s and
+<p class="note"><strong>Note:</strong> All elements' <code>field_id</code>s and
<code>method_id</code>s must refer to the same defining class.</p>
<h3 id="field-annotation">field_annotation format</h3>