Fix typos.

Author: rkistner

docs/compacting-operations.md

@@ -62,7 +62,7 @@ The disadvantage here is that these rows will be re-synced by existing clients.
 
 This is a process that compacts all buckets, by iterating through all operations. This process can be run periodically, for example once a day, or after bulk data modifications.
 
-The process iterates through all operations in reverse order. This effectively processes one bucket at a time, in reverse order of operatoins.
+The process iterates through all operations in reverse order. This effectively processes one bucket at a time, in reverse order of operations.
 
 We track each row we've seen in a bucket, along with the last PUT/REMOVE operation we've seen for the row. Whenever we see the same row again, we replace that operation with a MOVE operation, using the PUT/REMOVE op_id as the target.
 

docs/sync-protocol.md

@@ -26,7 +26,7 @@ This is typically (but not necessarily) be the first message in the response, an
 
 ## StreamingSyncCheckpointDiff
 
-This has the same conceptual meaning as a StreamingSyncCheckpoint. It is an optimization to only sent details for buckets that changed, instead of sending the entire checkpoint over.
+This has the same conceptual meaning as a StreamingSyncCheckpoint. It is an optimization to only send details for buckets that changed, instead of sending the entire checkpoint over.
 
 Format:
 

packages/service-core/src/storage/mongo/MongoCompactor.ts

@@ -65,7 +65,7 @@ export class MongoCompactor {
   }
 
   /**
-   * Compact buckets by converting operatoins into MOVE and/or CLEAR operations.
+   * Compact buckets by converting operations into MOVE and/or CLEAR operations.
    *
    * See /docs/compacting-operations.md for details.
    */