diff --git a/doc/Release_Notes_M10a.02.pdf b/doc/Release_Notes_M10a.03.pdf
similarity index 95%
rename from doc/Release_Notes_M10a.02.pdf
rename to doc/Release_Notes_M10a.03.pdf
index 0882994ed3ad23bd1e5ff124d669714647f13705..9b67ba04ea388ad1b767f3106eb7973e6e5e0c11 100644
Binary files a/doc/Release_Notes_M10a.02.pdf and b/doc/Release_Notes_M10a.03.pdf differ
diff --git a/src/scripts/README.md b/src/scripts/README.md
index 906c8647a41c1c3c63a772366d62d199329b54c5..4548b48f2f368ca7baf7f67d70befb0b8d887116 100644
--- a/src/scripts/README.md
+++ b/src/scripts/README.md
@@ -11,7 +11,7 @@ The code migration stage can be considered successfully fulfilled with the solut
 1. Follow the instructions to build and run the *FORTRAN* and *C++* versions of the code.
 2. Run the `pycompare.py` script providing the following minimal arguments:
 
-   > $PATH_TO_SCRIPT/pycompare.py --ffile=FORTRAN_OUTPUT --cfile=C++_OUTPUT
+   > $PATH_TO_SCRIPT/pycompare.py --ffile FORTRAN_OUTPUT --cfile C++_OUTPUT
 
 (The above assumes that `PATH_TO_SCRIPT` is a variable that expands to the path were the script is located). The required output files are called by default `OSPH` and `OCLU` by *FORTRAN* and `c_OSPH` and `c_OCLU` by *C++*, depending on whether the sphere or the cluster case was executed.