From 934d0408b940f3109c144b3d425f9f3cb25224ee Mon Sep 17 00:00:00 2001
From: Ashwin Ramesh <ashwin2007ray@gmail.com>
Date: Fri, 11 Mar 2016 09:48:48 +0530
Subject: [PATCH] Fix typos

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index ba17f7b7..4f46a188 100644
--- a/README.md
+++ b/README.md
@@ -50,7 +50,7 @@ $ docker pull dgraph/dgraph:latest
 $ docker run -t -i -v /somedir:/dgraph -p 80:8080 dgraph/dgraph:latest
 ```
 
-You that you're within the Docker instance, you can start the server.
+Now that you're within the Docker instance, you can start the server.
 ```
 $ mkdir /dgraph/m # Ensure mutations directory exists.
 $ server --mutations /dgraph/m --postings /dgraph/p --uids /dgraph/u
@@ -187,7 +187,7 @@ merge all the mutations to posting lists, and writes them to rocksdb which persi
 There're 2 types of merging going on: Gentle merge, and Aggressive merge.
 Gentle merging picks up N% of `dirty` posting lists, where N is currently 7, and merges them. This happens every 5 seconds.
 
-Aggressive merging hapepns when the memory usage goes above `stw_ram_mb`.
+Aggressive merging happens when the memory usage goes above `stw_ram_mb`.
 When that happens, the loader would *stop the world*, start the merge process, and evict all posting lists from memory.
 The more memory is available for loader to work with, the less frequently aggressive merging needs to be done, the faster the loading.
 
-- 
GitLab