Update performance.md

I corrected a few grammatical mistakes and increased the document's readability by easing the language flow.

1 files changed, 14 insertions, 14 deletions

diff --git a/docs/performance.md b/docs/performance.md
index a6a144237..6bb0235ca 100644
--- a/docs/performance.md
+++ b/docs/performance.md
@@ -1,25 +1,25 @@
 # Protobuf Performance
-This benchmark result is tested on workstation with processor of Intel® Xeon® Processor E5-2630 and 32GB RAM
+The following benchmark test results were produced on a workstation utilizing an Intel® Xeon® Processor E5-2630 with 32GB of RAM.
 
-This table contains 3 languages' results:
+This table contains the results of three separate languages:
 
-* **C++** - For C++ there're 3 kinds of parsing ways:
-	* **new** - This is for using new operator for creating message instance.
-    * **new arena** - This is for using arena for creating new message instance.
+* **C++** - For C++, there are three parsing methods:
+	* **new** - This is for using a new operator for creating a message instance.
+    * **new arena** - This is for using arena for creating a new message instance.
     * **reuse** - This is for reusing the same message instance for parsing.
-* **Java** - For Java there're 3 kinds of parsing/Serialization ways:
+* **Java** - For Java, there are three parsing/serialization methods:
 	* **byte[]** - This is for parsing from a Byte Array.
     * **ByteString** - This is for parsing from a
     	com.google.protobuf.ByteString.
-    * **InputStream** - This is for parsing from a InputStream
-* **Python** - For Python there're 3 kinds of python protobuf for testing:
-	* **C++-genereated-code** - This is for using cpp generated code of the
-    	proto file as dynamic linked library.
-	* **C++-reflection** - This is for using cpp reflection, which there's no
-    	generated code, but still using cpp protobuf library as dynamic linked
+    * **InputStream** - This is for parsing from an InputStream.
+* **Python** - For Python, there are three types of Python protobuf for testing:
+	* **C++-genereated-code** - This is for using C++ generated code of the
+    	proto file as a dynamic linked library.
+	* **C++-reflection** - This is for using C++ reflection, for which there's no
+    	generated code, but still using C++ protobuf library as a dynamic linked
         library.
-	* **pure-Python** - This is for pure Python version, which don't link with
-    	any cpp protobuf library.
+	* **pure-Python** - This is for the pure version of Python, which does not link with
+    	any C++ protobuf library.
 
 ## Parsing performance