Incorporate feedback by @janekdb and @dwijnand

Thank you.

Author: DarkDimius

sips/pending/_posts/2016-01-11-static-members.md

@@ -25,7 +25,7 @@ Static methods and fields for JavaScript classes are one of the very few things
 
 ## Overview ##
 
-In order for method or field to be considered static it needs to be defined in an `object` and annotated `@static`.
+In order for a method or field to be considered static it needs to be defined in an `object` and annotated `@static`.
 There is no special syntax proposed to access these members, they are accessed as if they were a member of defining objects with all appropriate access requirements for accessing them.
 
 For example:
@@ -44,7 +44,7 @@ println(Foo.bar(12))
 {% endhighlight %}
 ```
 
-Intuively, the presence of the `@static` annotation ensures that a field/method is declared as a static member of the companion class.
+Intuitively, the presence of the `@static` annotation ensures that a field/method is declared as a static member of the companion class.
 For the JVM, the above would therefore look to other Java code as if it had been declared with the following Java code:
 
 ```java
@@ -87,7 +87,7 @@ Foo.x = 5; // in ES6, there is no declarative syntax for static fields yet
 {% endhighlight %}
 ```
 
-## Comparisson with mirror classes ##
+## Comparison with mirror classes ##
 
 Scalac currently generates static forwarders for fields and methods in top-level objects:
 
@@ -108,7 +108,7 @@ If not annotated, it will be created in the companion module with a static forwa
 
 ## Restrictions ##
 
-The following rules ensure that method can be correctly compiled into static member on both JVM and JavaScript:
+The following rules ensure that methods can be correctly compiled into static members on both JVM and JavaScript:
 
 1. Only objects can have members annotated with `@static`
 
@@ -130,14 +130,14 @@ If implemented in the dotty code base, the following modifications would be need
  - extend `LambdaLift` to trigger an error if a method annotated with `@static` method cannot be lifted to the top level scope;
  - extend `GenBCode` to emit static fields and methods in companion classes and forwarders to them in companion modules.
 
-## Overriding&Hiding ##
+## Overriding & Hiding ##
 Java allows classes to define static methods with the same name and signature as a static method of a superclass. In order to define the semantics of such cases, the Java Specification introduces the notion of [hiding](http://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.4.8.2).
 
 This is required because in Java calling a `static` method on a class instance is supported.
 This proposal does not need to introduce this notion as we do not support such calls.
 
 ## Comparison with [@lrytz's proposal](https://gist.github.com/lrytz/80f3141de8240f9629da) ##
-Lucas Rytz has proposed a similar SIP, but his SIP requires changes to the typer to ensure that `@static` fields do not capture `this`, as in his proposal `@static` fields are defined in the class, rather than its companion object.
+Lukas Rytz has proposed a similar SIP, but his SIP requires changes to the typer to ensure that `@static` fields do not capture `this`, as in his proposal `@static` fields are defined in the class, rather than its companion object.
 It also does not address the question of `@static` members in inner objects and inheritance/hiding of those methods in subclasses.
 
 ## Open questions ##