Capitalize Dotty in docs

Author: DarkDimius

docs/blog/_posts/2015-10-23-dotty-compiler-bootstraps.md

@@ -29,7 +29,7 @@ fine, yet gets translated to something subtly wrong by the compiler.
 
 Having the compiler compile itself is a good test to demonstrate that
 the generated code has reached a certain level of quality. Not only is
-a compiler a large program (44k lines in the case of dotty), it is
+a compiler a large program (44k lines in the case of Dotty), it is
 also one that exercises a large part of the language in quite
 intricate ways. Moreover, bugs in the code of a compiler don't tend to
 go unnoticed, precisely because every part of a compiler feeds into

docs/blog/_posts/2016-01-02-new-year-resolutions.md

@@ -11,14 +11,14 @@ there are a couple of things where I would like to do better in 2016
 than in 2015. The first is that I would like to do more blogging and
 writing in general. I have been pretty silent for most of the last
 year. This was mostly caused by the fact that I had been heads down to
-work on DOT, Scala's foundations, and _dotty_, the new Scala compiler
+work on DOT, Scala's foundations, and _Dotty_, the new Scala compiler
 platform we are working on. It's been a lot of work, but we are finally
 getting good results. DOT now has a mechanized proof of type soundness
-and the dotty compiler [can now compile
+and the Dotty compiler [can now compile
 itself](http://www.scala-lang.org/blog/2015/10/23/dotty-compiler-bootstraps.html)
 as well as large parts of Scala's standard library.
 
-The dotty compiler has a completely new and quite unusual
+The Dotty compiler has a completely new and quite unusual
 architecture, which makes it resemble a functional database or a
 functional reactive program. My [talk at the JVM language
 summit](https://www.youtube.com/watch?v=WxyyJyB_Ssc) gives an

docs/blog/_posts/2016-02-03-essence-of-scala.md

@@ -131,7 +131,7 @@ project are important.
     wildcard parameters `[_ <: T]`, `[_ >: T]` should be.
 
  3. DOT also provides a blueprint for Scala compilation. The new Scala
-    compiler _dotty_ has internal data structures that closely resemble DOT.
+    compiler _Dotty_ has internal data structures that closely resemble DOT.
     In particular, type parameters are immediately mapped to type members,
     in the way we propose to encode them also in the calculus.
 

docs/blog/_posts/2016-02-17-scaling-dot-soundness.md

@@ -70,7 +70,7 @@ categories:
 We can in fact construct soundness issues in all of these cases. Look
 at the discussion for issues [#50](https://github.com/lampepfl/dotty/issues/50)
 and [#1050](https://github.com/lampepfl/dotty/issues/1050) in the
-[dotty](https://github.com/lampepfl/dotty/issues/1050) repository
+[Dotty](https://github.com/lampepfl/dotty/issues/1050) repository
 on GitHub. All issues work fundamentally in the same way: Construct a type `S`
 which has a type member `T` with bad bounds, say
 
@@ -138,7 +138,7 @@ arithmetic.
 
 To ease the transition, we will continue for a while to allow unrestricted type
 projections under a flag, even though they are potentially
-unsound. In the current dotty compiler, that flag is a language import
+unsound. In the current Dotty compiler, that flag is a language import
 `-language:Scala2`, but it could be something different for other
 compilers, e.g. `-unsafe`.  Maybe we can find rules that are less
 restrictive than the ones we have now, and are still sound.  But one

docs/blog/_posts/2016-12-05-implicit-function-types.md

@@ -53,7 +53,7 @@ scenarios where plain parameters would be too cumbersome. For
 instance, type classes would be a lot less popular if one would have
 to pass all dictionaries by hand. Implicit parameters are also very
 useful as a general context passing mechanism. For instance in the
-_dotty_ compiler, almost every function takes an implicit context
+_Dotty_ compiler, almost every function takes an implicit context
 parameter which defines all elements relating to the current state of
 the compilation. This is in my experience much better than the cake
 pattern because it is lightweight and can express context changes in a
@@ -151,7 +151,7 @@ implicit parameter:
 
 A three-times repetition might not look so bad here, but it certainly
 smells of boilerplate. In real-sized projects, this can get much worse.
-For instance, the _dotty_ compiler uses implicit abstraction
+For instance, the _Dotty_ compiler uses implicit abstraction
 over contexts for most of its parts. Consequently it ends up with currently
 no fewer than 2641 occurrences of the text string
 
@@ -180,7 +180,7 @@ type of `f1` is:
 
 Just like the normal function type syntax `A => B`, desugars to `scala.Function1[A, B]`
 the implicit function type syntax `implicit A => B` desugars to `scala.ImplicitFunction1[A, B]`.
-The same holds at other function arities. With dotty's [pull request #1758](https://github.com/lampepfl/dotty/pull/1758)
+The same holds at other function arities. With Dotty's [pull request #1758](https://github.com/lampepfl/dotty/pull/1758)
 merged there is no longer an upper limit of 22 for such functions.
 
 The type `ImplicitFunction1` can be thought of being defined as follows:

docs/docs/contributing/backend.md

@@ -8,7 +8,7 @@ lives at
 
 > https://github.com/lampepfl/scala/tree/sharing-backend
 
-The dotty source tree contains a git submodule in the directory
+The Dotty source tree contains a git submodule in the directory
 [scala-backend](https://github.com/lampepfl/dotty/tree/master/scala-backend)
 that points to this fork. We do not compile every file in this submodule,
 instead we add the subset of files we need to the dotty-compiler project in the
@@ -60,14 +60,14 @@ $ cd ..
 ```
 
 Once your PR has been merged into the backend, you'll need to make another PR
-against dotty itself to update the backend, the following commands should be run
-in the root dotty repository, not in the submodule:
+against Dotty itself to update the backend, the following commands should be run
+in the root Dotty repository, not in the submodule:
 
 ``` shell
 # The --remote option will update the submodule to the latest commit in the
 # https://github.com/lampepfl/dotty/tree/master/scala-backend branch
 git submodule update --init --remote
 
 git commit -am "Update backend to include ..."
-# Then push and make a PR against dotty as usual
+# Then push and make a PR against Dotty as usual
 ```

docs/docs/contributing/intellij-idea.md

@@ -8,7 +8,7 @@ Setup
 
 You can setup IntelliJ [IDEA >= 2016.1](https://www.jetbrains.com/idea/nextversion) to run Dotty.
 
-Assuming you have cloned dotty's repository from Github (and run `sbt managedSources` as described in [Getting Started](getting-started.md)),
+Assuming you have cloned Dotty's repository from Github (and run `sbt managedSources` as described in [Getting Started](getting-started.md)),
 you can now proceed with importing it to IDEA by selecting the
 corresponding option from the startup menu. Navigate on the corresponding directory and select it. Next, you need
 to select the model of the import and as the screenshot shows, select SBT.

docs/docs/internals/classpaths.md

@@ -43,5 +43,5 @@ file:/usr/lib/jvm/java-7-oracle/jre/lib/ext/sunpkcs11.jar:file:/usr/lib/jvm/java
 =====================================================
 ```
 Since scala/dotty only pick up `java.class.path` and `sun.boot.class.path`,
-it's clear why dotty crashes in sbt and Eclipse unless we set the boot
+it's clear why Dotty crashes in sbt and Eclipse unless we set the boot
 classpath explicitly.

docs/docs/usage/cbt-projects.md

@@ -3,7 +3,7 @@ layout: doc-page
 title: "Using Dotty with cbt"
 ---
 
-cbt comes with built-in dotty support. Follow the
+cbt comes with built-in Dotty support. Follow the
 [cbt tutorial](https://github.com/cvogt/cbt/), then simply extend `Dotty` in the Build class.
 
 ```scala

docs/docs/usage/dottydoc.md

@@ -256,5 +256,5 @@ A blog page uses files placed in `./blog/_posts/` as input to render a blog.
 
 Default Includes
 ================
-* `scala-logo.svg`: the scala in dotty version as svg
+* `scala-logo.svg`: the scala in Dotty version as svg
 * `toc.html`: the default table of contents template