--- a/doc/book/devrepo/repo/hooks.rst	Tue May 21 10:18:54 2019 +0200
+++ b/doc/book/devrepo/repo/hooks.rst	Wed May 22 11:29:49 2019 +0200
@@ -19,7 +19,7 @@
        age = Int(required=True)
 
 We would like to add a range constraint over a person's age. Let's write an hook
-(supposing yams can not handle this nativly, which is wrong). It shall be placed
+(supposing yams can not handle this natively, which is wrong). It shall be placed
 into `mycube/hooks.py`. If this file were to grow too much, we can easily have a
 `mycube/hooks/... package` containing hooks in various modules.
 
@@ -44,7 +44,7 @@
 In our example the base `__select__` is augmented with an `is_instance` selector
 matching the desired entity type.
 
-The `events` tuple is used specify that our hook should be called before the
+The `events` tuple is used to specify that our hook should be called before the
 entity is added or updated.
 
 Then in the hook's `__call__` method, we:
@@ -53,7 +53,7 @@
 * if so, check the value is in the range
 * if not, raise a validation error properly
 
-Now Let's augment our schema with new `Company` entity type with some relation to
+Now let's augment our schema with a new `Company` entity type with some relation to
 `Person` (in 'mycube/schema.py').
 
 .. sourcecode:: python
@@ -154,7 +154,7 @@
 
 Here, we call :func:`set_operation` so that we will simply accumulate eids of
 entities to check at the end in a single `CheckSubsidiaryCycleOp`
-operation. Value are stored in a set associated to the
+operation. Values are stored in a set associated to the
 'subsidiary_cycle_detection' transaction data key. The set initialization and
 operation creation are handled nicely by :func:`set_operation`.