Doc

README.md

@@ -20,7 +20,7 @@ So, for example, even though STL containers were not meant to be derived from (i
 are not virtual), `zen::string` derives from `std::string` in order to quickly, without having to implement all
 the conversion operators and delegate functions that a composition-based approach would require, provide the ability
 to convert to and from `std::string` at any point in the codebase whenever there's need for the richer interface
-of working with strings that `zen::string` provides. Although `zen::string` and similarly derived types in `zen`
+of working with strings that `zen::string` provides. Nevertheless, `zen::string` and similarly derived types in `zen`
 do have all the necessary restrictions in place to prevent such dynamic allocations just in case.
 
 This approach is rooted in the philosophy that in the vast majority of cases and projects, the benefits from these