Minor clarifications.

Author: DarkDimius

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

@@ -18,7 +18,7 @@ Some JVM and JavaScript frameworks require classes to have specific static field
 
 For example, classes extending `android.os.Parcelable` are required to have a static field named `CREATOR` of type `android.os.Parcelable$Creator`.
 
-Another example is using an [`AtomicReferenceFieldUpdater`](http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/atomic/AtomicReferenceFieldUpdater.html).
+Another example is using an [`AtomicReferenceFieldUpdater`](http://docs.oracle.com/javase/8/docs/api/java/util/concurrent/atomic/AtomicReferenceFieldUpdater.html).
 
 On the JavaScript side, one example is [Relay Route Definitions](https://facebook.github.io/relay/docs/guides-routes.html), whose subclasses must define static fields such as `queries`.
 Static methods and fields for JavaScript classes are one of the very few things (if not the only thing) that Scala.js "cannot do" at the moment, at least not declaratively.
@@ -103,8 +103,8 @@ object O {
 ```
 
 Under the proposed scheme users will be able to opt-in to have the field `f` defined in the inner object `I` emited as a static field. 
-In case `O.d` is annotated with `@static` the field will be crated as a static field in `class O`.
-If not annotated, it will be created in the companion module with a static forwarder in `class O`.
+In case `O.d` is annotated with `@static` the field will be crated as a static field `d` in `class O`.
+If not annotated, it will be created in the companion module with a static forwarder `d` in `class O`.
 
 ## Restrictions ##