Merge pull request #14166 from SethTisue/typos

festive holiday typo fixes

Author: nicolasstucki

compiler/src/dotty/tools/dotc/typer/Typer.scala

@@ -336,7 +336,7 @@ class Typer(@constructorOnly nestingLevel: Int = 0) extends Namer
            *  A package object should always be skipped if we look for a term.
            *  That way we make sure we consider all overloaded alternatives of
            *  a definition, even if they are in different source files.
-           *  If we are looking for a type, a package object should ne skipped
+           *  If we are looking for a type, a package object should be skipped
            *  only if it does not contain opaque definitions. Package objects
            *  with opaque definitions are significant, since opaque aliases
            *  are only seen if the prefix is the this-type of the package object.

compiler/src/dotty/tools/repl/ReplCompillationUnit.scala renamed to compiler/src/dotty/tools/repl/ReplCompilationUnit.scala

@@ -85,7 +85,7 @@ class ReplCompilerTests extends ReplTest {
       assertEquals("x: Int = 10", storedOutput().trim)
     }
 
-  @Test def defaultParamter = fromInitialState { implicit state =>
+  @Test def defaultParameter = fromInitialState { implicit state =>
     run("def foo(a: Int = 1): 1 = 1")
     assertEquals("def foo(a: Int): 1", storedOutput().trim)
   }

compiler/test/dotty/tools/repl/ReplCompilerTests.scala

@@ -88,7 +88,7 @@ on the structure of a tree is error-prone.
 ## Errors
 `dotc/typer/ErrorReporting.scala`
 
-Sometimes there's an error during compilation, but we want to continue compilling (as opposed to failing outright), to
+Sometimes there's an error during compilation, but we want to continue compiling (as opposed to failing outright), to
 uncover additional errors.
 
 In cases where a tree is expected but there's an error, we can use the `errorTree` methods in `ErrorReporting` to create