end of winter instead of spring

0_before_to_go_on.md

@@ -71,7 +71,7 @@ No need to read the following paragraphs ; go directly [there](https://git.unist
 Updating your OSM
 -----------------
 
-You should update with new data every year, say in spring, and at every new OSM version.
+You should update with new data every year, say at the end of winter, and at every new OSM version.
 
 
 Warning

1_doi_wos.md

@@ -33,7 +33,7 @@ Click on "Search" button.
 
 Note the number of records ; it will be usefull later to verify if the exported file is complete.
 
-I recommend you to save your search request with "copy query link" for future updates (every year, say in Spring, or in case of a new OSM version)
+I recommend you to save your search request with "copy query link" for future updates (every year, say at the end of winter, or in case of a new OSM version)
 
 Finally, from the results list, export by clicking on "Export" then choose "Excel" (if less than 1001 records)
 

7_and_then.md

@@ -76,7 +76,7 @@ Publishing your lab OSM, don't forget to mention at least :
 
 (First and last observation years are optional since they appear in the figures)
 
-Don't forget to update your lab OSM **every year** (say in Spring)
+Don't forget to update your lab OSM **every year** (say at the end of winter)
 
 **Caution :** It is advisable to repeat all exports (Don't add simply the last year) as the databases are regularly updated even for past years.
 

halok.md

@@ -50,7 +50,7 @@ Publishing your lab OSM, don't forget to mention at least :
 
 (First and last observation years are optional since they appear in the figures)
 
-Don't forget to update your lab OSM **every year** (say in Spring and at every new OSM version)
+Don't forget to update your lab OSM **every year** (say at the end of winter and at every new OSM version)
 
 
 Link to the following step