Merge pull request #6 from ember-learn/feature/highlight-format

updating all hbs and js file code examples to get ribbon implementation working

Author: Jen Weber

guides/v1.10.0/components/customizing-a-components-element.md

@@ -18,7 +18,7 @@ To use a tag other than `div`, subclass `Ember.Component` and assign it
 a `tagName` property. This property can be any valid HTML5 tag name as a
 string.
 
-```js
+```javascript
 App.NavigationBarComponent = Ember.Component.extend({
   tagName: 'nav'
 });
@@ -47,7 +47,7 @@ If you want class names to be determined by properties of the component,
 you can use class name bindings. If you bind to a Boolean property, the
 class name will be added or removed depending on the value:
 
-```js
+```javascript
 App.TodoItemComponent = Ember.Component.extend({
   classNameBindings: ['isUrgent'],
   isUrgent: true

guides/v1.10.0/components/handling-user-interaction-with-actions.md

@@ -27,7 +27,7 @@ When the title is clicked, the entire post body is shown:
 </script>
 ```
 
-```js
+```javascript
 App.PostSummaryComponent = Ember.Component.extend({
   actions: {
     toggleBody: function() {

guides/v1.10.0/components/passing-properties-to-a-component.md

@@ -16,7 +16,7 @@ value of the `title` property inside the `<h1>`.
 
 Now imagine we have the following template and route:
 
-```js
+```javascript
 App.IndexRoute = Ember.Route.extend({
   model: function() {
     return {

guides/v1.10.0/components/sending-actions-from-components-to-your-application.md

@@ -44,7 +44,7 @@ So how do you trigger sending a component's primary action? After
 the relevant event occurs, you can call the `sendAction()` method
 without arguments:
 
-```js
+```javascript
 App.MyButtonComponent = Ember.Component.extend({
   click: function() {
     this.sendAction();
@@ -65,14 +65,14 @@ To send parameters with the primary action, call `sendAction()` with the
 string `'action'` as the first argument and any additional parameters
 following it:
 
-```js
+```javascript
 this.sendAction('action', param1, param2);
 ```
 
 For example, imagine we're building a todo list that allows the user to
 delete a todo:
 
-```js
+```javascript
 App.IndexRoute = Ember.Route.extend({
   model: function() {
     return {
@@ -109,7 +109,7 @@ action.
 In the component, when triggering the primary action, we'll pass an
 additional argument that the component user can specify:
 
-```js
+```javascript
 App.ConfirmButtonComponent = Ember.Component.extend({
   actions: {
     showConfirmation: function() {
@@ -183,7 +183,7 @@ particular event, calling `sendAction()` has no effect.
 For example, if you define a component that triggers the primary action
 on click:
 
-```js
+```javascript
 App.MyButtonComponent = Ember.Component.extend({
   click: function() {
     this.sendAction();

guides/v1.10.0/configuring-ember/embedding-applications.md

@@ -13,7 +13,7 @@ the document's `body` element.
 You can tell the application to append the application template to a
 different element by specifying its `rootElement` property:
 
-```js
+```javascript
 App = Ember.Application.create({
   rootElement: '#app'
 });
@@ -29,7 +29,7 @@ You can prevent Ember from making changes to the URL by [changing the
 router's `location`](../../routing/specifying-the-location-api) to
 `none`:
 
-```js
+```javascript
 App.Router = Ember.Router.extend({
   location: 'none'
 });

guides/v1.10.0/contributing/adding-new-features.md

@@ -41,7 +41,7 @@ precisely this format. We are choosing conditionals rather than a block
 form because functions change the surrounding scope and may introduce
 problems with early return.
 
-```js
+```javascript
 if (Ember.FEATURES.isEnabled("feature")) {
   // implementation
 } 
@@ -64,7 +64,7 @@ described above.
 
 #### Feature Naming Conventions
 
-```js
+```javascript
 Ember.FEATURES["<packageName>-<feature>"] // if package specific
 Ember.FEATURES["container-factory-injections"]
 Ember.FEATURES["htmlbars"]
@@ -77,7 +77,7 @@ guarded by the conditionals in the original source. This means that
 users of the canary build can enable whatever features they want by
 enabling them before creating their Ember.Application.
 
-```js
+```javascript
 Ember.FEATURES["htmlbars"] = true;
 ```
 
@@ -90,7 +90,7 @@ builds.
 This file is populated when branching, and may not gain additional
 features after the original branch. It may remove features.
 
-```js
+```javascript
 {
   "htmlbars": true
 }

guides/v1.10.0/cookbook/client_server_interaction/serving_compiled_templates_using_nodejs.md

@@ -44,7 +44,7 @@ for your grunt tasks.
 5. Open the Gruntfile and paste in the following code:
 
 
-```js
+```javascript
 'use strict'
 
 module.exports = function (grunt) {

guides/v1.10.0/cookbook/ember_data/linking_to_slugs.md

@@ -22,7 +22,7 @@ function on the route.
 Identifying records by slugs is a two step problem. Given a Router
 mapping that looks like this:
 
-```js
+```javascript
 App.Router.map(function() {
   this.route('post', { path: '/post/:post_slug' });
 });
@@ -41,7 +41,7 @@ by a property (other then the id property). Luckily, it is easy to
 extend Ember Data's store object to provide this functionality. The
 code below adds a `findOne` method to the store.
 
-```js
+```javascript
 App.ApplicationStore = DS.Store.extend({
   findOne: function() {
     return this.find.apply(this, arguments).then(function(results) {
@@ -54,7 +54,7 @@ App.ApplicationStore = DS.Store.extend({
 Using `findOne` we can easily fetch a record by its `slug` property in
 the Route's model hook.
 
-```js
+```javascript
 App.PostRoute = Ember.Route.extend({
   model: function(params) {
     return this.store.findOne('post', {slug: params.post_slug});
@@ -82,7 +82,7 @@ Unfortunately it will generate an anchor tag that includes the `Post`'s
 You can work around this behavior by defining a custom `serialize`
 method on the route.
 
-```js
+```javascript
 App.PostRoute = Ember.Route.extend({
   serialize: function(model) {
     return {

guides/v1.10.0/cookbook/event_handling_and_data_binding/binding_properties_of_an_object_to_its_own_properties.md

@@ -4,7 +4,7 @@ You want to base the value of one property on the value of another property.
 ### Solution
 Use one of the computed property macros like `Ember.computed.alias` or `Ember.computed.gte`
 
-```js
+```javascript
 App.Person = Ember.Object.extend({
 	firstName : null,
 	lastName : null,

guides/v1.10.0/cookbook/event_handling_and_data_binding/toggling_a_boolean_property.md

@@ -4,7 +4,7 @@ You want to toggle a boolean property.
 ### Solution
 Use the `toggleProperty` method of an `Ember.Object`.
 
-```js
+```javascript
 obj.toggleProperty('isVisible');
 ```