Fixed Spelling.

CONTRIBUTING.md

@@ -64,7 +64,7 @@ After the release occurs, you will need to update the documentation. Here is a l
 
 (Other changes may be necessary, especially for large releases.)
 
-You can get a list of changes between release tags `v0.1.2` and `v0.2.0` via `git log v0.1.2..v0.2.0`. Scanning this list of commit messages is a good way to get a summary of what happened, although it does not account for conversations that occured on Github.
+You can get a list of changes between release tags `v0.1.2` and `v0.2.0` via `git log v0.1.2..v0.2.0`. Scanning this list of commit messages is a good way to get a summary of what happened, although it does not account for conversations that occurred on Github.
 
 Once the relevant documentation changes have been committed, new [release notes](https://github.com/twitter/scalding/releases) should be added. You can add a release by clicking the "Draft a new release" button on that page, or if the relevant release already exists, you can click "Edit release".
 

scalding-core/src/main/scala/com/twitter/scalding/typed/TypedPipe.scala

@@ -838,7 +838,7 @@ sealed abstract class TypedPipe[+T] extends Serializable with Product {
    * @return a pipe equivalent to the current pipe.
    */
   def write(dest: TypedSink[T])(implicit flowDef: FlowDef, mode: Mode): TypedPipe[T] = {
-    // We do want to record the line number that this occured at
+    // We do want to record the line number that this occurred at
     val next = withLine
     FlowStateMap.merge(flowDef, FlowState.withTypedWrite(next, dest, mode))
     next