From 596496e5fcc1f599937f2ac1a9801b7396e10b82 Mon Sep 17 00:00:00 2001 From: yogesh-gogia1 Date: Mon, 22 Jul 2024 16:39:12 +0530 Subject: [PATCH] typos --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d779597..1364cd6 100644 --- a/README.md +++ b/README.md @@ -167,7 +167,7 @@ jobs: ``` 2. As you can see in the above workflow, we have initiated the scan with initiate scan action step which takes client_scan_token, traffic_env, and traceable_server as input. You can configure other parameters as well as mentioned in the documentation. 3. Alternatively you can create a scan-suite on the Traceable.AI Platform and configure assets, attacks, evaluation criteria etc. on the platform itself. You can spawn a scan from the suite configuration by specifying just the `scan_suite` parameter with value as suite name. -3. In the next step we are executing functional tests and then running the scan in the step after that which take client_scan_token,traffic_env, and cli_version as input. +4. In the next step we are executing functional tests and then running the scan in the step after that which take client_scan_token,traffic_env, and cli_version as input.