docs: fix typos. (#34)

CMakeLists.txt

@@ -47,7 +47,7 @@ add_library(Greeter ${headers} ${sources})
 
 set_target_properties(Greeter PROPERTIES CXX_STANDARD 17)
 
-# beeing a cross-platform target, we enforce enforce standards conformance on MSVC
+# beeing a cross-platform target, we enforce standards conformance on MSVC
 target_compile_options(Greeter PUBLIC "$<$<BOOL:${MSVC}>:/permissive->")
 
 # Link dependencies (if required)

README.md

@@ -107,7 +107,7 @@ Glob is considered bad because any changes to the source file structure [might n
 
 > I want create additional targets that depend on my library. Should I modify the main CMakeLists to include them?
 
-Always avoid including derived projects from the from the libraries CMakeLists (even though it is a common sight in the C++ world), as this effectively inverts the dependency tree and makes the build system hard to reason about.
+Always avoid including derived projects from the libraries CMakeLists (even though it is a common sight in the C++ world), as this effectively inverts the dependency tree and makes the build system hard to reason about.
 Instead, create a new directory or project with a CMakeLists that adds the library as a dependency (e.g. like the [standalone](standalone/CMakeLists.txt) directory).
 Depending type it might make sense move these components into a separate repositories and reference a specific commit or version of the library.
 This has the advantage that individual libraries and components can be improved and updated independently.