diff --git a/docs/user-guides/cmake-user.rst b/docs/user-guides/cmake-user.rst
index 0f859325b2..e93ee33dd9 100644
--- a/docs/user-guides/cmake-user.rst
+++ b/docs/user-guides/cmake-user.rst
@@ -5,19 +5,20 @@ CMake user
 ----------
 
 This kind of developer can **read** CMake code that was written by more
-experienced CMake developer. He understand some simple features like that
-executable added by ``add_executable`` command and this command contains list
-of sources files.  But probably will not be able to tell why in some cases
-``include_directories`` command called but ``target_include_directories`` in
-other cases. The main target of modifications is C++ code.
+experienced CMake developers. They understand some simple features such as
+adding an executable with the ``add_executable`` command, and that this
+command contains a list of source files associated with the executable.
+They will probably have difficulty understanding why, in some cases, the
+``include_directories`` command is called, but in others, ``target_include_directories``
+is called instead. The main target of modifications is C++ code.
 
-Such developers can do:
+Such developers can:
 
-* Add more targets to project
+* Add more targets to projects
 * Add more sources to targets
-* Add C++ flags that does not break compatibility (e.g. warnings/optimization)
+* Add C++ flags that don't break compatibility (e.g. warnings/optimization)
 
-Such developers can't do:
+Such developers can't:
 
 * Add more external dependencies to project
 * Adding flags that can break compatibility (e.g. ``-std=c++11`` or ``/MT``)