Permalink
Browse files

spelling fix

  • Loading branch information...
1 parent 4ea613e commit a92217e7697955d8d532128062209db159071c60 @stvn committed Dec 16, 2012
Showing with 3 additions and 3 deletions.
  1. +1 −1 _posts/2012-12-17-second-post.html
  2. +1 −1 _site/index.html
  3. +1 −1 _site/tech/2012/12/17/second-post.html
@@ -20,7 +20,7 @@ <h4 class="post-title"><a href="{{ page.url }}">{{ page.title }}</a></h4>
</p>
<p>
- The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll except this is due to the framework's heavily opiniated ways (which I like btw).
+ The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll accept this is due to the framework's heavily opiniated ways (which I like btw).
</p>
<p class="section-title">
View
@@ -62,7 +62,7 @@ <h4 class="post-title"><a href="/tech/2012/12/17/second-post.html">Ember.js - in
</p>
<p>
- The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll except this is due to the framework's heavily opiniated ways (which I like btw).
+ The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll accept this is due to the framework's heavily opiniated ways (which I like btw).
</p>
<p class="section-title">
@@ -59,7 +59,7 @@ <h4 class="post-title"><a href="/tech/2012/12/17/second-post.html">Ember.js - in
</p>
<p>
- The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll except this is due to the framework's heavily opiniated ways (which I like btw).
+ The ember team does a great job getting documentation onto the website, however, it doesn't seem to be structured in a way that makes it easy to find information. Sure, at first glance it looks wonderful! But, as soon as you get past the most basic of examples and into the meat of a real application, the details go sparse. I've had to rely heavily on google and links to <a href="http://stackoverflow.com/search?q=emberjs" target="blank" class="inline-link">stackoverflow</a>. I'll accept this is due to the framework's heavily opiniated ways (which I like btw).
</p>
<p class="section-title">

0 comments on commit a92217e

Please sign in to comment.