diff --git a/notes.odt b/notes.odt
index d59fe46..75318e8 100644
Binary files a/notes.odt and b/notes.odt differ
diff --git a/readme.md b/readme.md
index 6aa3b1a..db030d8 100644
--- a/readme.md
+++ b/readme.md
@@ -1,16 +1,16 @@
 ## Testing of differeng cloning methods 
 Our objective is to find the least-consuming method in terms of memory and bandwidth resources.
-We are interested in cloning one specific state of the repository. We are not interested in its history or the possibility to change it from the server where it has been cloned. The first step is done by the script creation_repo.sh which creates an adequate repository to test on. The testing in itself is done by performance_tests.sh.
+We are interested in cloning one specific state of the repository. We are not interested in its history or the possibility to change it from the server where it has been cloned. The first step is done by the script creation_repo.sh which creates an adequate repository to act as a local remote. The testing in itself is done by performance_tests.sh.
+NB:The large file storage is not tested by this script because it relies on additional remote stockage and we are interested in reducing the overall stockage for environmental purposes.
 
 ## Creation of the test repository
 The script creation_repo.sh creates a performance_testing repository. 
 NAME
     creation_repo.sh
 SYNOPSIS
-    creation_repo.sh [SSH LINK to en empty remote git repository] 
+    creation_repo.sh [-h]
 DESCRIPTION
-    This script is in writing.
-    It creates a git repository in the current directory, linked to a remote passed as argument. Everything is up-to-date between the remote and the local versions. The data stored is generated randomly in binary.
+    It creates a remote directory in the current directory, then create a remote/performance_testing git repository. This git repository is filled with randomly generated binary.
 OPTIONS
     -h prints the help. 
 
@@ -45,17 +45,23 @@ sample1 1M
 sample2 500K
 
 ## Testing
-The script performance_tests.sh measures memory and bandwidth usage of different git cloning scenarii.
+The script performance_tests.sh measures memory and bandwidth usage for different git commands. It sources creation_repo.sh in order to have an adequate repository to test on. It also sources the script driglibash-base.
 NAME
     performance_tests.sh
 SYNOPSIS
-    performance_tests.sh [SSH LINK to en empty remote git repository] [number]
+    performance_tests.sh [-a] [-h] [-n number]
 OPTIONS
     -a excutes all the tests.
-    -n [number] executes test [number]
+    -n number executes test number
     -h prints the help. 
 DESCRIPTION
-    This script is in writing. It allows you to measure memory and bandwidth usage for different method of cloning on the remote repository given.
+    This script is in writing. It allows you to measure memory and bandwidth usage. The first four test different cloning methods. Te following change the local remote by adding a 1M "sample5" file before testing fetching and merging commands.
     TEST0: classic cloning 
     TEST1: --single-branch 
+    TEST2: --depth=1 --no-single-branch
+    TEST3: --depth=1
+    TEST4: sparse-checking 1M sample0 only 
+    _________________________________________
+    TEST5: classic fetching and merging
+    TEST6: 
     
\ No newline at end of file