docs only.

fix some typos.

2 files changed, 5 insertions, 5 deletions

diff --git a/docs/html/guide/guide_toc.cs b/docs/html/guide/guide_toc.cs
index 264fe54..39f0ffa 100644
--- a/docs/html/guide/guide_toc.cs
+++ b/docs/html/guide/guide_toc.cs
@@ -98,7 +98,7 @@
       </li>
       <li class="toggle-list">
         <div><a href="<?cs var:toroot ?>guide/topics/resources/index.html">
-               <span class="en">Resources and Assests</span> 
+               <span class="en">Resources and Assets</span> 
              </a></div>
         <ul>
           <li><a href="<?cs var:toroot ?>guide/topics/resources/resources-i18n.html">
diff --git a/docs/html/guide/topics/ui/ui-events.jd b/docs/html/guide/topics/ui/ui-events.jd
index f4d114a..5628d46 100644
--- a/docs/html/guide/topics/ui/ui-events.jd
+++ b/docs/html/guide/topics/ui/ui-events.jd
@@ -28,8 +28,8 @@ the specific View object that the user interacts with. The View class provides t
 methods that look useful for UI events. These methods are called by the Android framework when the 
 respective action occurs on that object. For instance, when a View (such as a Button) is touched,
 the <code>onTouchEvent()</code> method is called on that object. However, in order to intercept this, you must extend
-the class and override the method. Obviously, extending every View object
-you want to use (just to handle an event) would be obsurd. This is why the View class also contains
+the class and override the method. However, extending every View object
+in order to handle such an event would not be practical. This is why the View class also contains
 a collection of nested interfaces with callbacks that you can much more easily define. These interfaces,
 called <a href="#EventListeners">event listeners</a>, are your ticket to capturing the user interaction with your UI.</p>
 
@@ -102,7 +102,7 @@ protected void onCreate(Bundle savedValues) {
 }
 </pre>
 
-<p>You may also find it more conventient to implement OnClickListener as a part of your Activity.
+<p>You may also find it more convenient to implement OnClickListener as a part of your Activity.
 This will avoid the extra class load and object allocation. For example:</p>
 <pre>
 public class ExampleActivity extends Activity implements OnClickListener {
@@ -168,7 +168,7 @@ you'll learn see some of the common callbacks used for event handling, including
   <li><code>{@link  android.view.View#onTouchEvent}</code> - Called when a touch screen motion event occurs.</li>
   <li><code>{@link  android.view.View#onFocusChanged}</code> - Called when the view gains or loses focus.</li>
 </ul>
-<p>There are some other methods that you should be awere of, which are not part of the View class, 
+<p>There are some other methods that you should be aware of, which are not part of the View class, 
 but can directly impact the way you're able to handle events. So, when managing more complex events inside 
 a layout, consider these other methods:</p>
 <ul>