diff --git a/v1.3.1/README.org b/v1.3.1/README.org
index d8f1fb9..cbbf789 100644
--- a/v1.3.1/README.org
+++ b/v1.3.1/README.org
@@ -98,7 +98,11 @@ are predefined:
 
 * Common rules
 
-Except if stated otherwise, all the scenarios follow these rules.
+Except if stated otherwise, all the scenarios follow these rules (or
+should follow them for future tests). The description of the scenarios
+has precedence over these common rules. Moreover, the report files
+associated with each test should also warn about each noticed mistake,
+and each exception made to these rules or to the scenario description.
 
 ** Devices used
 
@@ -111,9 +115,12 @@ Except if stated otherwise, all the scenarios follow these rules.
 
 ** Environmental parameters:
 
-- The temperature is controlled around 22°C.
+- The temperature is controlled around 22-24°C.
 - The humidity varies from 38% to 55%.
 
+Each test's report file should report the temperature and humidity when
+the test was started.
+
 ** Aggregator
 
 OwlPS Aggregator is run with the default parameters as of the version
@@ -123,10 +130,23 @@ configuration file [[./owlps-config/owlps-aggregator.conf]].
 These parameters are not very important, except for the delay between
 two autocalibration orders. The default value is 1000 ms.
 
+The default aggregation timeout should fit most test cases, but keep in
+mind that for requests as long as one second (including manual
+calibration request with the default parameters), it is too short and
+must be extended in the Aggregator's configuration.
+
+You should also be aware of the fact that for a capture point to
+transmit autocalibration requests, it must be known by the
+Aggregator. Therefore, it is not sufficient to wait for 10 seconds
+(cf. Measurement procedure) after starting the Aggregator to guarantee
+that each capture point transmits autocalibration requests for 10
+seconds. The counter must be started after the Aggregator received an
+Hello message from all the capture points.
+
 At the end of a test, beware of not stopping the Aggregator too early,
 e.g. if requests are sent with long delays, or simply if the aggregate
 timeout is not reached for all the requests in memory (as of August
-2012, OwlPS Aggregator does not flush the non-aggregated requests uppon
+2012, OwlPS Aggregator does not flush the non-aggregated requests upon
 exiting, but simply deletes them).
 
 ** Listeners
@@ -178,9 +198,11 @@ The mobile terminal's antenna is vertical.
 ** Measurement procedure
 
 - The infrastructure (Listeners and Aggregator) must be started first
-  and at least a round of autocalibration request done (i.e. each
-  capture point must have sent at least one autocalibration request)
-  before the mobile terminal is started.
+  and at least two rounds of autocalibration request done (i.e. each
+  capture point must have sent at least two autocalibration request)
+  before the mobile terminal is started. As a best practice, the
+  measurements should start at least 10 seconds after the Aggregator
+  knows all the Listeners (cf. Aggregator for more details).
 - In the scenario in which a human has to move along a path, a metronome
   is set up with the tempo at which the person has to walk. For example,
   60 bpm if the pace is of one metre per second.
@@ -276,15 +298,9 @@ Alternatively, if the experiments are done during only one session, the
 autocalibration process can be run only once, at the beginning, and the
 autocalibration requests stored in a separate file.
 
-Please keep in mind the following points:
-- For requests as long as one second, the aggregation timeout must be
-  extended in the Aggregator's configuration.
-- For a capture point to transmit autocalibration requests, it must be
-  known by the Aggregator. Therefore, it is not sufficient to wait for
-  10 seconds after starting the Aggregator to guarantee that each
-  capture point transmits autocalibration requests for 10 seconds. The
-  10 seconds counter must be started after the Aggregator received an
-  Hello message from all the capture points.
+Please keep in mind that for requests as long as one second, the
+aggregation timeout must be extended in the Aggregator's configuration
+(cf. Common rules for details).
 
 ** Scenario 6
 
@@ -347,7 +363,7 @@ frequency.
 
 The following frequencies are tested:
 - 100 ms (Listeners: -n10 -t8 = 80 ms),
-- 250 ms (Liseners: -n16 -t14 = 224 ms),
+- 250 ms (Listeners: -n16 -t14 = 224 ms),
 - 500 ms (Listeners: -n20 -t24 = 480 ms),
 - 1000 ms (Listeners: -n39 -t25 = 975 ms).
 *** TODO coord
@@ -450,3 +466,6 @@ terminal.
 
 Manual calibration, without autocalibration running. The mobile device
 is carried by a human operator.
+
+Please keep in mind that the default aggregation time is not sufficient
+to aggregate correctly manual calibration requests (cf. Common rules).