README update

README

@@ -62,7 +62,7 @@ memory partition. This feature provides the option of having an adjustable
 mixture of generalisation and specialisation of system services at the same
 run-time, by using a combination of Codezero's abstract posix-like page/file
 management services and an application-specific pager that depends on its own
-paging abilities. For example a critical task could both use mm0/fs0's
+paging abilities. For example a critical task could both use mm0 and fs0's
 posix-like files benefiting from the abstraction and simplification that it
 brings, but at the same time rely on its own page-fault handling for its
 critical data so that even though it handles its memory in a specialised way,
@@ -92,13 +92,13 @@ as BSD versions and Linux. However, neither of these were originally designed
 for embedded systems. Multiple problems arise due to this fact.
 
 Unix itself and all the tools built upon weren't meant for using on small
-devices. Accordingly, these operating systems contain a lot of historical code.
-Their code base is so big, that it gets more and more difficult to understand
-how their internals work. On these systems usually much of the existing code
-base is irrelevant to newly developed software, and embedded systems need new
-software often. Codezero is written from scratch to solely target embedded
-systems and as such the source code is %100 relevant. It is small and free from
-legacy code.
+devices. Accordingly, existing Unix operating systems contain a lot of
+historical code. Their code base is so big, that it gets more and more difficult
+to understand how their internals work. On these systems usually much of the
+existing code base is irrelevant to newly developed software, and embedded
+systems need new software often. Codezero is written from scratch to solely
+target embedded systems and as such the source code is %100 relevant. It is
+small and free from legacy code.
 
 From a design perspective, these kernels have a monolithic design, and as such
 they may have issues with dependability due to much of the code sharing the same
@@ -106,7 +106,7 @@ address space. This is an important issue on embedded systems since their
 operation is more sensitive to disruptions. Being a microkernel design, Codezero
 aims to defeat this problem and increase dependability.
 
-From a support perspective, most unix operating systems like BSD and linux have
+From a support perspective, most Unix operating systems like BSD and linux have
 a highly saturated user base. The developers focus on these existing users and
 often the systems they support are servers and not embedded computers. Codezero
 will focus completely on embedded systems, aiming to meet the support need for
@@ -116,10 +116,9 @@ Other than modern unix kernels, there are existing operating systems targeting
 embedded devices. Most of them are proprietary, with their own users. Some of
 them are structurally too simplistic, and lack modern features such as paging.
 There ones that are well established, but Codezero will contrast them by
-being a more open-source friendly alternative. Many embedded software projects
-still use older or closed development methods and the right open source
-methodology would prove favorable in the fast-paced nature of embedded software
-development.
+being a more open alternative. Many embedded software projects still use older
+or closed development methods and the right open source methodology would prove
+favorable in the fast-paced nature of embedded software development.
 
 Finally, POSIX compliance is only a step, or a partial aim for the Codezero
 microkernel. It is not limited to the goal of just complying with POSIX, which