A couple of small tweaks

Author: tjvantoll

index.html

@@ -536,13 +536,13 @@ <h4 class="exercise-start">
 				<h2 id="application-logic">Application Logic</h2>
 <p>In this chapter you’ll learn how to add JavaScript logic to your app, how to create services that talk to backend endpoints, and how to architect an app that uses multiple pages. There’s a lot to cover, so let’s start by discussing how to handle events and data binding.</p>
 <h3 id="events">Events</h3>
-<p>Most user interfaces are driven by events. In NativeScript apps, those events are usually some user action, such as tapping, swiping, or rotating—and NativeScript abstracts the iOS- and Android-specific code for handling such events into a handful of easy-to-use APIs. Let’s start with the most common event you’ll use in a NativeScript app—<code>tap</code>.</p>
+<p>Most user interfaces are driven by events. In NativeScript apps, those events are usually some user action, such as tapping, swiping, or rotating—and NativeScript abstracts the iOS- and Android-specific code for handling such events into a handful of easy-to-use APIs. Let’s start with the most common event you’ll use in a NativeScript app: <code>tap</code>.</p>
 <h4 class="exercise-start">
     <b>Exercise</b>: Add a <code>tap</code> event handler
 </h4>
 
 <p>Open <code>app/app.component.ts</code>, find the existing sign in button within your component’s <code>template</code> (<code>&lt;Button text=&quot;Sign in&quot;&gt;&lt;/Button&gt;</code>), and replace it with the following code:</p>
-<pre><code class="lang-JavaScript">&lt;Button text=&quot;Sign in&quot; (tap)=&quot;signIn()&quot;&gt;&lt;/Button&gt;
+<pre><code class="lang-JavaScript">&lt;Button text=&quot;Sign in&quot; id=&quot;submit-button&quot; (tap)=&quot;signIn()&quot;&gt;&lt;/Button&gt;
 </code></pre>
 <p>Next, in the same file, replace the current <code>AppComponent</code> declaration with the one shown below:</p>
 <pre><code class="lang-JavaScript">export class AppComponent {
@@ -554,16 +554,16 @@ <h4 class="exercise-start">
 <div class="exercise-end"></div>
 
 <p>The <code>(eventName)=&quot;functionName()&quot;</code> syntax is part of <a href="https://angular.io/docs/ts/latest/guide/template-syntax.html#!#event-binding">Angular 2’s event binding system</a>, which lets you bind an event that occurs on a UI element to a function in your component’s class. In this case, the <code>(tap)=&quot;signIn()&quot;</code> syntax tells Angular to run the <code>AppComponent</code> class’s <code>signIn()</code> function whenever the user taps the sign in button.</p>
-<p>To verify this binding works try tapping the sign in button in your app; you should see “hello” logged in your terminal or command prompt as such:</p>
-<p><img src="images/chapter3/terminal-1.png" alt="Terminal showing the word hello logged"></p>
+<p>To verify this binding works tap the “Sign In” button in your app; you should see “hello” logged in your terminal or command prompt as such:</p>
+<p><img alt="Terminal showing the word hello logged" src="images/chapter3/terminal-1.png" class="plain"></p>
 <blockquote>
 <p><strong>TIP</strong>:</p>
 <ul>
 <li>In NativeScript you can find a list of events available in the appropriate UI element’s API documentation. For instance, the <a href="http://docs.nativescript.org/ApiReference/ui/button/Button">button element’s API documentation</a> lists its <code>tap</code> event.</li>
 <li>The Angular 2 docs have a helpful <a href="https://angular.io/docs/ts/latest/guide/cheatsheet.html">cheat sheet</a> that includes the various syntaxes available when building templates. Don’t worry too much about knowing how all these work at the moment; we’ll progressively introduce the most common syntaxes in this guide.</li>
 </ul>
 </blockquote>
-<p>With the <code>tap</code> event in place, we now have a way of tying our UI elements in our template to TypeScript code. To make a login page actually work though, we need to introduce one other way of connecting a template to code: data binding.</p>
+<p>With the <code>tap</code> event in place, you now have a way of tying the UI elements in your template to your TypeScript code. To make a login page actually work though, we need to introduce one other way of connecting a template to code: data binding.</p>
 <h3 id="data-binding">Data Binding</h3>
 <p>Angular 2 provides several ways to bind data in your TypeScript code to UI controls, and through the magic of NativeScript those same methods are available in your iOS and Android apps.</p>
 <p>The first of these is a way to bind UI attributes to properties defined in your TypeScript class. Let’s look at how it works.</p>
@@ -572,7 +572,7 @@ <h4 class="exercise-start">
 </h4>
 
 <p>In <code>app/app.component.ts</code> replace the current <code>AppComponent</code> declaration with the one shown below, which adds a new <code>email</code> property, and changes the <code>signIn()</code> method to display its value:</p>
-<pre><code class="lang-JavaScript">export class AppComponent {
+<pre><code class="lang-TypeScript">export class AppComponent {
   email = &quot;nativescriptrocks@telerik.com&quot;;
   signIn() {
     alert(&quot;You’re using: &quot; + this.email);

scripts/built.js

@@ -4,7 +4,7 @@ In this chapter you’ll learn how to add JavaScript logic to your app, how to c
 
 ### Events
 
-Most user interfaces are driven by events. In NativeScript apps, those events are usually some user action, such as tapping, swiping, or rotating—and NativeScript abstracts the iOS- and Android-specific code for handling such events into a handful of easy-to-use APIs. Let’s start with the most common event you’ll use in a NativeScript app—`tap`.
+Most user interfaces are driven by events. In NativeScript apps, those events are usually some user action, such as tapping, swiping, or rotating—and NativeScript abstracts the iOS- and Android-specific code for handling such events into a handful of easy-to-use APIs. Let’s start with the most common event you’ll use in a NativeScript app: `tap`.
 
 <h4 class="exercise-start">
     <b>Exercise</b>: Add a `tap` event handler
@@ -13,7 +13,7 @@ Most user interfaces are driven by events. In NativeScript apps, those events ar
 Open `app/app.component.ts`, find the existing sign in button within your component’s `template` (`<Button text="Sign in"></Button>`), and replace it with the following code:
 
 ``` JavaScript
-<Button text="Sign in" (tap)="signIn()"></Button>
+<Button text="Sign in" id="submit-button" (tap)="signIn()"></Button>
 ```
 
 Next, in the same file, replace the current `AppComponent` declaration with the one shown below:
@@ -30,15 +30,15 @@ export class AppComponent {
 
 The `(eventName)="functionName()"` syntax is part of [Angular 2’s event binding system](https://angular.io/docs/ts/latest/guide/template-syntax.html#!#event-binding), which lets you bind an event that occurs on a UI element to a function in your component’s class. In this case, the `(tap)="signIn()"` syntax tells Angular to run the `AppComponent` class’s `signIn()` function whenever the user taps the sign in button.
 
-To verify this binding works try tapping the sign in button in your app; you should see “hello” logged in your terminal or command prompt as such:
+To verify this binding works tap the “Sign In” button in your app; you should see “hello” logged in your terminal or command prompt as such:
 
-![Terminal showing the word hello logged](images/chapter3/terminal-1.png)
+<img alt="Terminal showing the word hello logged" src="images/chapter3/terminal-1.png" class="plain">
 
 > **TIP**:
 > * In NativeScript you can find a list of events available in the appropriate UI element’s API documentation. For instance, the [button element’s API documentation](http://docs.nativescript.org/ApiReference/ui/button/Button) lists its `tap` event.
 > * The Angular 2 docs have a helpful [cheat sheet](https://angular.io/docs/ts/latest/guide/cheatsheet.html) that includes the various syntaxes available when building templates. Don’t worry too much about knowing how all these work at the moment; we’ll progressively introduce the most common syntaxes in this guide.
 
-With the `tap` event in place, we now have a way of tying our UI elements in our template to TypeScript code. To make a login page actually work though, we need to introduce one other way of connecting a template to code: data binding.
+With the `tap` event in place, you now have a way of tying the UI elements in your template to your TypeScript code. To make a login page actually work though, we need to introduce one other way of connecting a template to code: data binding.
 
 ### Data Binding
 
@@ -52,7 +52,7 @@ The first of these is a way to bind UI attributes to properties defined in your
 
 In `app/app.component.ts` replace the current `AppComponent` declaration with the one shown below, which adds a new `email` property, and changes the `signIn()` method to display its value:
 
-``` JavaScript
+``` TypeScript
 export class AppComponent {
   email = "nativescriptrocks@telerik.com";
   signIn() {

src/chapters/chapter3.md

@@ -47,7 +47,7 @@
 		"c#": "clike",
 		"appbuilder" : "javascript",
 		"javascript" : "javascript",
-		"typescript" : "javascript",
+		"typescript" : "typescript",
 		"c++" : "clike",
 		"c" : "clike",
 		"css" : "css",