Fixes some spelling and grammar problems

Author: saebyn

README.md

@@ -17,10 +17,10 @@ Licensed under the GPLv2. See the file COPYING for details.
 
 
 
-Requires
---------
+Requirements
+------------
 
-For using:  
+For use:  
  - C++ compiler with C++11 support.  
 
 
@@ -29,24 +29,24 @@ For development:
  - [GNU Make](https://www.gnu.org/software/make/);  
  - [CMake](http://www.cmake.org/) (2.8.12);  
  - the test suite requires the [Google C++ Test Framework](http://code.google.com/p/googletest/);  
- - microbenchmaring requires [Benchmark](https://github.com/google/benchmark), [Celero](https://github.com/DigitalInBlue/Celero), [Hayai](https://github.com/nickbruun/hayai) and [gprof](http://www.gnu.org/software/binutils/);  
+ - microbenchmarking requires [Benchmark](https://github.com/google/benchmark), [Celero](https://github.com/DigitalInBlue/Celero), [Hayai](https://github.com/nickbruun/hayai) and [gprof](http://www.gnu.org/software/binutils/);  
  - code coverage requires [gcov](https://gcc.gnu.org/onlinedocs/gcc/Gcov.html) and lcov;  
- - static code analyzis required [cppcheck](https://github.com/danmar/cppcheck).  
+ - static code analyzer requires [cppcheck](https://github.com/danmar/cppcheck).  
 
 
 
 Portability
 -----------
 
-The project is developing under GNU/Linux OS with gcc compiler and usualy not tested under other OS and compilers.
-But in the project not used OS or compiler specific features (types, attributes, etc) so it's expected that the project will be normally work under other platforms.
+The project is developed under the GNU/Linux OS with the gcc compiler and usualy not tested under other OSs and compilers.
+But the project does not use OS or compiler specific features (types, attributes, etc) so it's expected that the project will be normally work under other platforms.
 
 
 
 Usage
 -----
 
-To use the project the following steps are required:  
+These steps are the easiest way to get started:
   - download: ```$ git clone https://github.com/saebyn/munkres-cpp.git && cd munkres-cpp```  
   - build: ```$ mkdir build && cd build $$ cmake .. && make```  
   - install: ``` $ make install```  
@@ -63,12 +63,13 @@ TBD
 Development
 -----------
 
-For development purpose in the project implemented a variety of build targets.
+For development purpose, the project implements a variety of build targets.
 All of them help to continuously check correctness of algorithm implementation, performance, memory management, etc.
-To configure project in development mode ```-DMUNKRESCPP_DEVEL_MODE=ON``` option must be passed to CMake.
+Pass the```-DMUNKRESCPP_DEVEL_MODE=ON``` option to CMake to enable development mode.
 
-Launch of unit tests.
-The project contains unit tests to build and launch it performs the following steps:
+# Running unit tests:
+
+Build and execute the test suite with these commands:
 ```
 $ git clone https://github.com/saebyn/munkres-cpp.git
 $ cd munkres-cpp
@@ -79,38 +80,42 @@ $ tests/munkrestest
 ```
 
 
-Lunch code coverage analyze.
-To get correct report unit tests must be compiled in debug mode.
+# Running code coverage analyzer:
+
+You must compile unit tests in debug mode to get a correct code coverage report.
 ```
-$ <build and lunch unit tests>
+$ <build and Launch unit tests>
 $ make coverage
 $ firefox coverage/index.html &
 ```
 
 
-Lunch memory profiler.
-As far unit tests call all functions which implement algorithm this is appropriate way to check memory management by using valgrind during performing unit tests.
+# Running the memory profiler:
+
+Since the unit tests call all functions which implement the algorithm, using valgrind on the unit test runner is an appropriate way to check memory management.
 ```
 $ <build unit tests>
 $ valgrind tests/munkrestest
 ```
 
 
-Lunch microbenchmarks.
-Buildning microbenchmarks:
+# Running the microbenchmarks:
+
+First, build them:
 ```
 $ git clone https://github.com/saebyn/munkres-cpp.git
 $ cd munkres-cpp
 $ mkdir build && cd build
 $ cmake -DCMAKE_BUILD_TYPE=Release -DMUNKRESCPP_DEVEL_MODE=ON ..
 $ make benchmarks
 ```
+
 To get comparable results it's required to generate data set wich will be used for all benchmarks:
 ```
 $ benchmarks/tools/generator/matrixgenerator.bin {dim_1 dim_2 ... dim_n}
 ```
-Where every ```dim_x``` parameter generate square matrix dith ```dim_x``` dimension.
-To launch microbenchmark performs any following command:
+Where every ```dim_x``` parameter generates a square matrix with ```dim_x``` dimension.
+To launch microbenchmarks, perform the following commands:
 ```
 $ benchmarks/tests/munkresbenchmark_celero.bin
 $ benchmarks/tests/munkresbenchmark_google.bin
@@ -119,21 +124,24 @@ $ benchmarks/tests/munkresbenchmark_rdtsc.bin
 ```
 
 
-Lunch performance analyze.
+# Getting performance profiling:
+
 ```
 $ <build microbenchmarks and generate data set>
 $ benchmarks/tests/munkresbenchmark_gprof.bin
 $ gprof benchmarks/tests/munkresbenchmark_gprof.bin gmon.out -p -b
 ```
 
 
-Lunch static code analyze.
+# Running the static code analyzer:
+
 ```
 $ make cppcheck
 ```
 
 
-Lunch code formatter:
+# Running the code formatter:
+
 TBD