update doc

Author: senacra

README.md

@@ -20,9 +20,10 @@ In any cases the following 2 steps should be done before using project :
 1. Generate an access token on your GitHub account to be able to run [Komac](https://github.com/russellbanks/Komac).
 2. Create a fork from [winget-pkgs](https://github.com/microsoft/winget-pkgs) to handle your pull requests for manifests - Also take care to validate all requirements to be able to contribute to Microsoft repositories. 
 
-If you want to use the existing docker image (**<span style="color: green">recommended</span>**) or use the dockerfile to build  image  then you can skip the other depedencies. 
+If you want to use the existing docker image (recommended) or use the dockerfile to build  image  then you can skip the other depedencies. 
 
-If you want to test the script localy then you need to be on Linux or WSL if using Windows (as this is an sh script) and to install the following distribution dependencies :
+
+If you want to test the script localy (useful for debug) then you need to be on Linux or WSL if using Windows (as this is an sh script) and to install the following distribution dependencies :
 * Basic dependencies (Example on Ubuntu)
   ```sh
   apt-get update && apt-get install -y --no-install-recommends --no-install-suggests git wget curl jq ca-certificates
@@ -33,7 +34,7 @@ If you want to test the script localy then you need to be on Linux or WSL if usi
   dpkg -i komac_2.10.1-1_amd64.deb
   ```
 
-### Usage (Docker)
+### Usage (Docker) - ${\textsf{\color{lightgreen}Recommended}}$
 For a lot of reasons, it is more convient (at least for me) to "containerize" a script rather than running it as it is.
 The docker image can be run using 5 parameters (passed as runtime  `ENV` settings) :
 - `<MAINTAINER_REPO>` : The GitHub project where your winget-pkgs fork is located, in the format *githubName/winget-pkgs-fork*.
@@ -57,17 +58,12 @@ The docker image can be run using 5 parameters (passed as runtime  `ENV` setting
    sudo docker run -e MAINTAINER_REPO=... -e PUBLISHER_REPO=... -e WINGET_PACKAGE=... -e GIT_TOKEN=... -e MODE=latest senacra/wingetmus:v0.1.0
    ```
 
-### Usage (Localy) - <span style="color: red"> not recommended </span>
+### Usage (Localy) - ${\textsf{\color{orange}Not Recommended}}$
 The update_manifest.sh basically takes the exact same parameters as the docker.
-- `<MAINTAINER_REPO>` : The GitHub project where your winget-pkgs fork is located, in the format *githubName/winget-pkgs-fork*.
-- `<PUBLISHER_REPO>` : The GitHub project where the package releases are located, in the format *githubName/project_name*.
-- `<WINGET_PACKAGE>`: The name of the package (as declared in winget manifest) that you want to track and update, in the format *Publisher.PackageName*.
-- `<GIT_TOKEN>`: Your PAT for your GitHub account with the winget-pkgs fork.
-- (opt) `<MODE>` : a mode string to know if you want to track only for upcomming releases (default) or if you want to also create manifest for all past releases (use value *full*).
 
 For example :
    ```sh
-   ./update_manifest.sh myName/winget-pkgs-fork AwesomePublisher/TopPackage AwesomePublisher.TopPackage this_should_look_random
+   ./update_manifest.sh myName/winget-pkgs-fork AwesomePublisher/TopPackage AwesomePublisher.TopPackage this_should_look_random latest
    ```