diff --git a/docs/html/training/improving-layouts/reusing-layouts.jd b/docs/html/training/improving-layouts/reusing-layouts.jd
index 87431d3a59c39..8c63afb65e3cc 100644
--- a/docs/html/training/improving-layouts/reusing-layouts.jd
+++ b/docs/html/training/improving-layouts/reusing-layouts.jd
@@ -43,7 +43,7 @@ to embed another layout inside the current layout.</p>
 <p>Reusing layouts is particularly powerful as it allows you create reusable complex layouts. For
 example, a yes/no button panel, or custom progress bar with description text.
 It also means that any elements of your application that are common across multiple layouts can be
-extracted, managed separately, then included in each layout. So while 
+extracted, managed separately, then included in each layout. So while
 you can create individual UI components by writing a custom {@link android.view.View}, you can
 do it even more easily by re-using a layout file.</p>
 
@@ -56,14 +56,14 @@ included in each activity (<code>titlebar.xml</code>):</p>
 
 <pre>
 &lt;FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width=”match_parent”
+    android:layout_width="match_parent"
     android:layout_height="wrap_content"
     android:background="&#64;color/titlebar_bg">
 
     &lt;ImageView android:layout_width="wrap_content"
-               android:layout_height="wrap_content" 
-               android:src="&#64;drawable/gafricalogo" />
-&lt;/FrameLayout>
+               android:layout_height="wrap_content"
+               android:src="&#64;drawable/gafricalogo" /&gt;
+&lt;/FrameLayout&gt;
 </pre>
 
 <p>The root {@link android.view.View} should be exactly how you'd like it to appear in each
@@ -80,18 +80,18 @@ G-Kenya codelab that includes the title bar from above:</p>
 
 <pre>
 &lt;LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:orientation="vertical" 
-    android:layout_width=”match_parent”
-    android:layout_height=”match_parent”
+    android:orientation="vertical"
+    android:layout_width="match_parent"
+    android:layout_height="match_parent"
     android:background="&#64;color/app_bg"
-    android:gravity="center_horizontal">
+    android:gravity="center_horizontal"&gt;
 
-    <strong>&lt;include layout="&#64;layout/titlebar"/></strong>
+    <strong>&lt;include layout="&#64;layout/titlebar"/&gt;</strong>
 
-    &lt;TextView android:layout_width=”match_parent”
+    &lt;TextView android:layout_width="match_parent"
               android:layout_height="wrap_content"
               android:text="&#64;string/hello"
-              android:padding="10dp" />
+              android:padding="10dp" /&gt;
 
     ...
 
@@ -103,10 +103,10 @@ included layout's root view by specifying them in the {@code &lt;include/&gt;} t
 example:</p>
 
 <pre>
-&lt;include android:id=”&#64;+id/news_title”
-         android:layout_width=”match_parent”
-         android:layout_height=”match_parent”
-         layout=”@layout/title”/>
+&lt;include android:id="&#64;+id/news_title"
+         android:layout_width="match_parent"
+         android:layout_height="match_parent"
+         layout="@layout/title"/&gt;
 </pre>
 
 <p>However, if you want to override layout attributes using
@@ -130,17 +130,17 @@ serves no real purpose other than to slow down your UI performance.</p>
 {@code &lt;merge&gt;} element as the root view for the re-usable layout. For example:</p>
 
 <pre>
-&lt;merge xmlns:android="http://schemas.android.com/apk/res/android">
+&lt;merge xmlns:android="http://schemas.android.com/apk/res/android"&gt;
 
     &lt;Button
-        android:layout_width="fill_parent" 
+        android:layout_width="fill_parent"
         android:layout_height="wrap_content"
-        android:text="@string/add"/>
+        android:text="@string/add"/&gt;
 
     &lt;Button
-        android:layout_width="fill_parent" 
+        android:layout_width="fill_parent"
         android:layout_height="wrap_content"
-        android:text="@string/delete"/>
+        android:text="@string/delete"/&gt;
 
 &lt;/merge>
 </pre>