From 9b6687bbc6a3e2866fdfd8ac3c725138d4c7ecbf Mon Sep 17 00:00:00 2001
From: Andy McFadden <fadden@android.com>
Date: Tue, 15 Jan 2013 12:26:04 -0800
Subject: [PATCH] Fix code snippet

One of the examples was incorrect (both here and in the original).

http://b.android.com/42776

Change-Id: I2a218b724f50caf47d5185ef529ae8ab3104794f
---
 docs/html/training/articles/smp.jd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/html/training/articles/smp.jd b/docs/html/training/articles/smp.jd
index 53d78798ae7c3..d46787d14f8ed 100644
--- a/docs/html/training/articles/smp.jd
+++ b/docs/html/training/articles/smp.jd
@@ -628,7 +628,7 @@ array.</p>
 
 <p>The “loop_until” seen in previous examples has been expanded to show the load
 of B into reg0.  reg1 is assigned the numeric value 8, and reg2 is loaded from
-the address [A+reg1] (same location that thread 1 is accessing).</p>
+the address [A+reg1] (the same location that thread 1 is accessing).</p>
 
 <p>This will not behave correctly because the load from B could be observed
 after the load from [A+reg1].  We can fix this with a load/load barrier after
@@ -640,7 +640,7 @@ the loop, but on ARM we can also just do this:</p>
 <th>Thread 2</th>
 </tr>
 <tr>
-<td><code>A = 41<br />
+<td><code>[A+8] = 41<br />
 <em>store/store barrier</em><br />
 B = 1    // “A is ready”</code></td>
 <td><code>loop:<br />