# HG changeset patch
# User Noe Gaumont <ngaumont@logilab.fr>
# Date 1558517389 -7200
# Node ID 092d201a7c17cfbb2be6e3a6cedee73e68fbed70
# Parent  8241058763524c3306cddf7f2b52b2bca8211fa0
[doc] fix several typos

diff -r 824105876352 -r 092d201a7c17 cubicweb/server/hook.py
--- a/cubicweb/server/hook.py	Tue May 21 10:18:54 2019 +0200
+++ b/cubicweb/server/hook.py	Wed May 22 11:29:49 2019 +0200
@@ -75,7 +75,7 @@
 
 Hooks are being fired immediately on data operations, and it is sometime
 necessary to delay the actual work down to a time where we can expect all
-information to be there, or when all other hooks have run (though take case
+information to be there, or when all other hooks have run (though take care
 since operations may themselves trigger hooks). Also while the order of
 execution of hooks is data dependant (and thus hard to predict), it is possible
 to force an order on operations.
@@ -784,7 +784,7 @@
 
 class DataOperationMixIn(object):
     """Mix-in class to ease applying a single operation on a set of data,
-    avoiding to create as many as operation as they are individual modification.
+    avoiding creating as many operations as there are individual modifications.
     The body of the operation must then iterate over the values that have been
     stored in a single operation instance.
 
diff -r 824105876352 -r 092d201a7c17 doc/book/annexes/rql/language.rst
--- a/doc/book/annexes/rql/language.rst	Tue May 21 10:18:54 2019 +0200
+++ b/doc/book/annexes/rql/language.rst	Wed May 22 11:29:49 2019 +0200
@@ -557,7 +557,7 @@
 ~~~~~~~~~~~~~~~~~~~
 
 Below is the list of aggregate and transformation functions that are supported
-nativly by the framework. Notice that cubes may define additional functions.
+natively by the framework. Notice that cubes may define additional functions.
 
 .. _RQLAggregateFunctions:
 
diff -r 824105876352 -r 092d201a7c17 doc/book/devrepo/repo/hooks.rst
--- 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`.