From 16b4a6ed84cedd3765de51fe6a1d21de8d44e11c Mon Sep 17 00:00:00 2001
From: CarlTern <35721844+CarlTern@users.noreply.github.com>
Date: Fri, 17 May 2024 15:36:30 +0200
Subject: [PATCH] docs: Update Automated import section with fcli 2.x commands

---
 doc-resources/parser-obtain-results.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc-resources/parser-obtain-results.md b/doc-resources/parser-obtain-results.md
index 8759f2b..f1a4857 100644
--- a/doc-resources/parser-obtain-results.md
+++ b/doc-resources/parser-obtain-results.md
@@ -1,6 +1,6 @@
 ### Automated import
 
-The easiest approach for importing Debricked results into SSC is through [fcli](https://github.com/fortify-ps/fcli), using the `fcli ssc appversion-artifact import debricked command`. This command will download the Debricked CycloneDX SBOM file using the Debricked REST API, and then upload the SBOM file to SSC for processing by this parser plugin. 
+The easiest approach for importing Debricked results into SSC is through [fcli](https://github.com/fortify-ps/fcli), using the `fcli ssc artifact import-debricked` command. This command will download the Debricked CycloneDX SBOM file using the Debricked REST API, and then upload the SBOM file to SSC for processing by this parser plugin. 
 
 When using fcli, there is no need to manually obtain the SBOM file, preparing a proper SSC third-party results zip-file, and uploading this zip-file to SSC. With this approach, the information in the [Manual import](#manual-import) and [Upload results](#upload-results) sections can be ignored.