From fa6341a4659de688677cf5756ead92ad18f3911e Mon Sep 17 00:00:00 2001
From: Jeremy Elbourn <jelbourn@gmail.com>
Date: Fri, 22 Jan 2016 13:24:25 -0800
Subject: [PATCH] docs(): fix coding standards example w/ wrong language

---
 CODING_STANDARDS.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/CODING_STANDARDS.md b/CODING_STANDARDS.md
index fb6c96fedb8..ded56c3335c 100644
--- a/CODING_STANDARDS.md
+++ b/CODING_STANDARDS.md
@@ -15,7 +15,7 @@ ES6 or TypeScript.
 Comments that explain what some block of code does are nice; they can tell you something in less time than it would take to follow through the code itself.
 
 Comments that explain why some block of code exists at all, or does something the way it does, 
-are invaluable. The "why" is difficult, or sometimes impossible, to track down without seeking out 
+are _invaluable_. The "why" is difficult, or sometimes impossible, to track down without seeking out 
 the original author. When collaborators are in the same room, this hurts productivity. 
 When collaborators are in different timezones, this can be devastating to productivity.
 
@@ -40,14 +40,14 @@ if (!$attrs['tabindex']) {
 #### Prefer more focused, granular components vs. complex, configurable components.
 
 For example, rather than doing this:
-```ts
+```html
 <md-button>Basic button</md-button>
 <md-button class="md-fab">FAB</md-button>
 <md-button class="md-icon-button">pony</md-button>
 ```
 
 do this:
-```ts
+```html
 <md-button>Basic button</md-button>
 <md-fab>FAB</md-fab>
 <md-icon-button>pony</md-icon-button>