Merge pull request #8 from fortify/auto-doc-updates

Update documentation resources

LICENSE.txt

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright 2020-2023 Open Text or one of its affiliates
+Copyright 2020-2024 Open Text or one of its affiliates
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -42,6 +42,9 @@ Clair 2.x `/v1/layers/{layerId}?features&vulnerabilities` REST API call
 <!-- END-INCLUDE:repo-resources.md -->
 
 
+
+<!-- START-INCLUDE:h2.support.md -->
+
 ## Support
 
 The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
@@ -52,6 +55,9 @@ Support requests created through the GitHub Issues page may include bug reports,
 
 Support requests on the GitHub Issues page are handled on a best-effort basis; there is no guaranteed response time, no guarantee that reported bugs will be fixed, and no guarantee that enhancement requests will be implemented. If you require dedicated support for this and other Fortify software, please consider purchasing OpenText Fortify Professional Services. OpenText Fortify Professional Services can assist with general usage questions, integration of the software into your processes, and implementing customizations, bug fixes, and feature requests (subject to feasibility analysis). Please contact your OpenText Sales representative or fill in the [Professional Services Contact Form](https://www.microfocus.com/en-us/cyberres/contact/professional-services) to obtain more information on pricing and the services that OpenText Fortify Professional Services can provide.
 
+<!-- END-INCLUDE:h2.support.md -->
+
+
 ---
 
 *[This document was auto-generated from README.template.md; do not edit by hand](https://github.com/fortify/shared-doc-resources/blob/main/USAGE.md)*

USAGE.md

@@ -128,7 +128,7 @@ To upload results through the SSC web interface or most clients:
 
 Both SSC REST API and fcli provide options for specifying the engine type directly, and as such it is not necessary to package the raw results into a zip-file with accompanying `scan.info` file. For example, fcli allows for uploading raw scan results using a command like the following:
 
-`fcli ssc appversion-artifact upload <raw-results-file> --appversion MyApp:MyVersion --engine-type CLAIR_REST_V1`
+`fcli ssc artifact upload -f <raw-results-file> --appversion MyApp:MyVersion --engine-type CLAIR_REST_V1`
 
 <!-- END-INCLUDE:usage/h1.standard-parser-usage.md -->