Update documentation

Author: rubenmromero

README.md

@@ -32,13 +32,15 @@ If you have several initialized submodules in your project, and you handle sever
 
 The `git_matrix.sh` script works in the following way:
 
-* You directly move across the project environment branches using the usual Git commands such as `git checkout <branch>` or any other similar.
-* Being positioned at the branch you want to update, you can directly run the `./bin/git_matrix.sh` script from the project root folder, which performs the following tasks:
- * Updates the active local branch (`git pull`) and submodules status (`git submodule init` & `git submodule update`).
- * Updates all environment branches of each submodule.
- * If the active branch is the first environment branch (the branch defined in the first position), the script directly does the following actions:
- * Positions each submodule in the last commit (HEAD) of its first environment branch.
- * Commits the produced changes by the previous action, in the event that there are, including as commit message the list of updates done by the script.
- * If the active branch is any other different from the first, there are the following execution alternatives:
- * If the script has been executed with the `[-k|--keep]` optional parameter,it directly perfoms the following actions:
- * Merges the previous environment branch in order to propagate the commited and pushed changes made in the previous environment/s of the project.
+You directly move across the project environment branches using the usual Git commands such as `git checkout <branch>` or any other similar.
+
+Being positioned at the branch you want to update, you can directly run the `./bin/git_matrix.sh` script from the project root folder, which performs the following tasks:
+
+* Updates the active local branch (`git pull`) and submodules status (`git submodule init` & `git submodule update`).
+* Updates all environment branches of each submodule.
+* If the active branch is the first environment branch (the branch defined in the first position), the script directly does the following actions:
+ * Positions each submodule in the last commit (HEAD) of its first environment branch.
+ * Commits the produced changes by the previous action, in the event that there are, including as commit message the list of updates done by the script.
+* If the active branch is any other different from the first, there are the following execution alternatives:
+ * If the script has been executed with the `[-k|--keep]` optional parameter,it directly perfoms the following actions:
+ * Merges the previous environment branch in order to propagate the commited and pushed changes made in the previous environment/s of the project.