Fix lint

Author: bhou-crto

gh-pages/content/en/docs/overview/built-in-commands.md

@@ -84,4 +84,3 @@ Remove a dropin package from the package name defined in manifest
 ```shell
 cola delete command-launcher-example-package
 ```
-

gh-pages/content/en/docs/overview/dropin.md

@@ -51,7 +51,6 @@ If you uploaded your package to an http server as a zip file, you can install it
 cola install --file https://github.com/criteo/command-launcher/raw/main/examples/remote-repo/command-launcher-demo-1.0.0.pkg
 ```
 
-
 ## How to update dropin package?
 
 For now, the command launcher does not update the dropin folder automatically, it is up to developers themselve to keep these dropin package up-to-date.

gh-pages/content/en/docs/overview/system-package.md

@@ -60,7 +60,6 @@ To extend command launcher, you need to specify `system` type command in a syste
 | \_\_login\_\_       | calling your IAM system to return `login_token` |
 | \_\_metrics\_\_     | collect metrics                                 |
 
-
 ### System command \_\_login\_\_
 
 The built-in `login` command will trigger the `__login__` system command. It takes two arguments:
@@ -69,7 +68,7 @@ The built-in `login` command will trigger the `__login__` system command. It tak
 - password
 
 ```shell
-$ __login__ [username] [password]
+__login__ [username] [password]
 ```
 
 The `__login__` system command outputs the credentials to be stored by command launcher in a JSON format. The credentials could be one or many of following items:

gh-pages/content/en/docs/quickstart/build-from-source.md

@@ -61,5 +61,3 @@ You can run one integration test by specify the name of the integration test fil
 ```shell
 ./test/integration.sh test-remote
 ```
-
-