Merge pull request #226 from adriaanm/master

Fix more references to spec

Author: sjrd

_includes/footer.html

@@ -7,7 +7,7 @@
       <li><a href="http://www.scala-lang.org/api/current/index.html#package">API</a></li>
       <li><a href="http://docs.scala-lang.org/overviews/">Overviews/Guides</a></li>
       <li><a href="http://docs.scala-lang.org/tutorials/">Tutorials</a></li>
-      <li><a href="{{ site.baseurl }}/files/archive/nightly/pdfs/ScalaReference.pdf">Language Specification <img src="{{ site.baseurl }}/resources/img/pdf-red.png" alt="red pdf icon" /></a></li>
+      <li><a href="{{ site.baseurl }}/files/archive/spec/2.11/">Language Specification</a></li>
     </ul>
     <ul>
       <li><h5>Download</h5></li>

_layouts/frontpage2.html

@@ -64,7 +64,7 @@ <h2 style="font-weight: 700;">Object-Oriented Meets Functional</h2>
       <p class="getting-started"><b>API: </b><a href="http://www.scala-lang.org/api/current/"><b>Current</b></a> | <a href="http://www.scala-lang.org/files/archive/nightly/2.11.x/api/2.11.x/"><b>Nightly</b></a></p>
       <p class="dev-releases"><img src="{{ site.baseurl }}/resources/img/list.png" alt="list icon" /><a href="{{ site.baseurl }}/documentation/api.html">&nbsp;All Previous API Docs</a></p>
       <p class="dev-releases"><img src="{{ site.baseurl }}/resources/img/books.png" alt="books icon" /><a href="{{ site.baseurl }}/documentation/">&nbsp;Scala Documentation</a></p>
-      <p class="all-releases"><img src="{{ site.baseurl }}/resources/img/pdf.png" alt="pdf icon" /><a href="{{ site.baseurl }}/files/archive/spec/2.11/">&nbsp;Language Specification</a></p>
+      <p class="all-releases"><img src="{{ site.baseurl }}/resources/img/books.png" alt="books icon" /><a href="{{ site.baseurl }}/files/archive/spec/2.11/">&nbsp;Language Specification</a></p>
     </div>
   </div>
 </div>

contribute/bug-reporting-guide.md

@@ -43,7 +43,7 @@ If you have a code snippet that is resulting in bytecode which you believe is be
 
    5. If you want to file an improvement in the issue tracker please discuss it first on one of the mailing lists. They offer much bigger audience than issue tracker. The latter is not suitable for long discussions.
 
-* Keep in mind that the behavior you are witnessing could be intended. Good formal resources for verifying whether or not the language behavior is intended is either in the [Scala Improvement Proposal Documents](http://docs.scala-lang.org/sips/sip-list.html) or in the [Scala Language Specification](http://www.scala-lang.org/docu/files/ScalaReference.pdf). If in doubt, you may always ask on the [scala-internals mailing list](https://groups.google.com/forum/?fromgroups#!forum/scala-internals) or [stackoveflow](http://stackoverflow.com/questions/tagged/scala).
+* Keep in mind that the behavior you are witnessing could be intended. Good formal resources for verifying whether or not the language behavior is intended is either in the [Scala Improvement Proposal Documents](http://docs.scala-lang.org/sips/sip-list.html) or in the [Scala Language Specification](http://www.scala-lang.org/files/archive/spec/2.11/). If in doubt, you may always ask on the [scala-internals mailing list](https://groups.google.com/forum/?fromgroups#!forum/scala-internals) or [stackoveflow](http://stackoverflow.com/questions/tagged/scala).
 
 In general, if you find yourself stuck on any of these steps, asking on one of the following Scala mailing lists can be helpful: