diff --git a/assets/images/hyperexecute/cli/analyze.png b/assets/images/hyperexecute/cli/analyze.png
new file mode 100644
index 000000000..e2247c0eb
Binary files /dev/null and b/assets/images/hyperexecute/cli/analyze.png differ
diff --git a/assets/images/hyperexecute/cli/completion.png b/assets/images/hyperexecute/cli/completion.png
new file mode 100644
index 000000000..f1159be16
Binary files /dev/null and b/assets/images/hyperexecute/cli/completion.png differ
diff --git a/docs/deep-dive-into-hyperexecute-yaml.md b/docs/deep-dive-into-hyperexecute-yaml.md
index e686cc065..fe3c101f7 100644
--- a/docs/deep-dive-into-hyperexecute-yaml.md
+++ b/docs/deep-dive-into-hyperexecute-yaml.md
@@ -1363,6 +1363,7 @@ if your test loads jquery static library multiple times and for some reason it i
 
 ### `afterAll`
 > This flag is deprecated, instead use [`globalPost`](/support/docs/deep-dive-into-hyperexecute-yaml/#globalpost)
+
 It is used to run commands after the job has finished. Currently only local directive is allowed, means that all the commands would be run on the same host on which HyperExecute CLI was run. Running commands in `afterAll` on HyperExecute VMs(remote commands) is not yet supported. Users will have access to all the artifacts when these commands would be run.
 ```yaml
 afterAll:
@@ -1379,6 +1380,7 @@ For instance you want to further process the artifacts and create a custom PDF.
 
 ## `beforeAll`
 > This flag is deprecated, instead use [`globalPre`](/support/docs/deep-dive-into-hyperexecute-yaml/#globalpre)
+
 BeforeAll is used for running pre operations like discovery and payload_update. It can be executed either on local system or on hyperexecute beforeAll VM. 
 ```yaml
 beforeAll:
diff --git a/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md b/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md
index 23f8d9257..50c689ac5 100644
--- a/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md
+++ b/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md
@@ -74,6 +74,8 @@ The various flags that are supported are listed below.
 
 | Flags | Type | Description|
 |-------|------|------------|
+| [analyze](#analyze) | NA | Analyzes the language and environment supported in your project.| 
+| [completion](#completion) | NA | Generates the autocompletion script for HyperExecute for the specified shell. |
 | [--concurrency](#--concurrency) | Numerical | Indicates the number of concurrent sessions on HyperExecute. | 
 | [--config](#--config) | string | Custom location for hyperexecute.yaml. |
 | [--download-artifacts](#--download-artifacts) | NA | Download the artifacts for a job. |
@@ -100,6 +102,28 @@ The various flags that are supported are listed below.
 | [--verbose](#--verbose) | NA | Logging of every proxy request to stdout. |
 | [--version](#--version) | NA | Version of the HyperExecute CLI. |
 
+### `analyze`
+This flag runs **HyperExecute Analyze**, which is a language and environment detection tool used to render every language and framework detail the user has in his project, which includes finding private dependencies.
+
+```bash
+hyperexecute analyze
+```
+
+<img loading="lazy" src={require('../assets/images/hyperexecute/cli/analyze.png').default} alt="Image"  className="doc_img"/>
+
+***
+
+### `completion`
+This flag generates the autocompletion script for HyperExecute for the specified shell.
+
+```bash
+hyperexecute completion
+```
+
+<img loading="lazy" src={require('../assets/images/hyperexecute/cli/completion.png').default} alt="Image"  className="doc_img"/>
+
+***
+
 ### `--concurrency`
 This flag allows you to define the number of concurrent sessions running on HyperExecute. For more information on concurrency, go to [this page](/support/docs/hyperexecute-auto-split-strategy/).
 ```bash
@@ -350,14 +374,6 @@ This flag indicates the version of HyperExecute CLI binary that you are running
 ```
 ***
 
-### `analyze`
-This flag runs **HyperExecute Analyze**, which is a language and environment detection tool used to render every language and framework detail the user has in his project, which includes finding private dependencies.
-
-```bash
-hyperexecute analyze
-```
-***
-
 ## Trigger your Test from HyperExecute CLI 
 
 In order to trigger your job on HyperExecute, execute the following command in your terminal. You will need to insert the name of your YAML file in place of the `RELATIVE_PATH_OF_YOUR_YAML_FILE` before running this command.