Skip to content
Browse files

Merge pull request #44 from impressivewebs/master

Added <abbr> to "OSS" and fixed a typo
  • Loading branch information...
2 parents 6fe19b1 + 17e3993 commit fe1f222817a8b4decc0e42e20fe689e0a7207b74 @paulirish committed
Showing with 2 additions and 2 deletions.
  1. +2 −2 index.html
View
4 index.html
@@ -192,7 +192,7 @@ <h1 id="intervention"><b>W3Schools</b> An Intervention</h1>
<section class="content"><h2 id="build-one-yourselves">&ldquo;Build One Yourself&rdquo;</h2>
<p>
- An oft-repeated mantra in OSS (and a critique we've already received) is that you shouldn't criticise something unless you're willing to put your money where your mouth is and build something better. It's an admirable ethos, but not really applicable here.</p>
+ An oft-repeated mantra in <abbr title="Open-source Software">OSS</abbr> (and a critique we've already received) is that you shouldn't criticise something unless you're willing to put your money where your mouth is and build something better. It's an admirable ethos, but not really applicable here.</p>
<p>W3Schools has put a lot of effort into positioning itself at the top of search results and, despite our efforts (such as the
<a href="http://promotejs.com/">PromoteJS</a> initiative), appears to be there to stay. Other, better resources already exist, but
none of them are capable of overcoming the inertia that W3Schools has built up over the years.</p>
@@ -331,7 +331,7 @@ <h1 id="intervention"><b>W3Schools</b> An Intervention</h1>
<p>
Extensions are not necessary at all and if they are present they don't have to be
<code>.htm</code> or <code>.html</code>. The key thing is that HTML files are served with
- the corrent content-type e.g. <code>text/html</code>. (many web servers have some built in
+ the correct content-type e.g. <code>text/html</code>. (many web servers have some built in
or preconfigured knowledge that <code>.htm</code> and <code>.html</code> should be served
with the <code>text/html</code> content-type)
</p>

0 comments on commit fe1f222

Please sign in to comment.
Something went wrong with that request. Please try again.