chore: message file updates - update command references (#466)

* chore: update scan import description

* chore: update help messages

* update help messages

* chore: update help messages

* chore: update message file command references

fcli-core/fcli-common/src/main/resources/com/fortify/cli/common/i18n/FortifyCLIMessages.properties

@@ -35,7 +35,7 @@ output = Specify output format and options. Available output formats: ${COMPLETI
   '-o json-properties' on the current command to see available properties.
 to-file = Write command output to the specified file instead of stdout.
 store = Store the JSON results of this command in a variable. Variables can be managed through \
-  the 'fcli config variable' command, and can be referenced using ::variable::[property] on any \
+  the 'fcli util variable' command, and can be referenced using ::variable::[property] on any \
   subsequent command. 
 query = Only display records for which the given Spring Expression Language (SpEL) expression returns true. 
 

fcli-core/fcli-fod/src/main/resources/com/fortify/cli/fod/i18n/FoDMessages.properties

@@ -229,7 +229,7 @@ fcli.fod.app.update.usage.header = Update an existing application.
 fcli.fod.app.update.usage.description = This command updates the details of an application. \
   To create, update or delete any releases on the application use the 'fcli fod release' subcommands. \
   To create, update or delete any microservices on the application use the 'fcli fod microservice' subcommands. \
-  To update user and group access for the application use the 'fcli fod user' and 'fcli fod user-group' subcommands.
+  To update user and group access for the application use the 'fcli fod access-control' subcommands.
 fcli.fod.app.update.app = The id or name of the application to update.
 fcli.fod.app.update.name = The updated name for the application.
 fcli.fod.app.update.description = The updated description for the application.

fcli-core/fcli-license/src/main/resources/com/fortify/cli/license/i18n/LicenseMessages.properties

@@ -11,7 +11,7 @@ fcli.license.usage.description = This module provides various commands related t
 # fcli util msp-report
 fcli.license.msp-report.usage.header = Configure and generate 'Managed Service Provider' (MSP) reports.
 fcli.license.msp-report.create.usage.header = Generate a 'Managed Service Provider' (MSP) report.
-fcli.license.msp-report.create.usage.description.0 = This command generates a 'Managed Service Provider' (MSP) report based on configuration settings defined in a configuration file. A sample configuration file can be generated using the 'fcli util msp-report create-config' command.
+fcli.license.msp-report.create.usage.description.0 = This command generates a 'Managed Service Provider' (MSP) report based on configuration settings defined in a configuration file. A sample configuration file can be generated using the 'fcli license msp-report create-config' command.
 fcli.license.msp-report.create.usage.description.1 = \nThe configuration file includes settings for specifying one or more SSC instances from which to load MSP reporting data, and for specifying MSP (contract) information.
 fcli.license.msp-report.create.usage.description.2 = \nThe generated report consists of multiple files, written to either a directory or zip-file. The primary output file is 'summary.txt' that contains various statistics, including the number of application and scan entitlements consumed during the reporting period. Various CSV files providing proof, like the number of entitlements consumed per application, what artifacts were processed, and which artifacts contributed to the entitlement consumption, are generated in the details directory of the report.
 fcli.license.msp-report.create.usage.description.3 = \nThe generated 'checksums.sha256' file can be used to verify integrity of all generated files, using a command like 'sha256sum -c checksums.sha256'.
@@ -35,7 +35,7 @@ fcli.license.msp-report.create-config.confirm = Confirm overwrite of existing co
 # fcli util ncd-report
 fcli.license.ncd-report.usage.header = Configure and generate 'Number of Contributing Developers' (NCD) reports.
 fcli.license.ncd-report.create.usage.header = Generate a 'Number of Contributing Developers' (NCD) report.
-fcli.license.ncd-report.create.usage.description.0 = This command generates a 'Number of Contributing Developers' (NCD) report based on configuration settings defined in a configuration file. A sample configuration file can be generated using the 'fcli util ncd-report create-config' command.\n
+fcli.license.ncd-report.create.usage.description.0 = This command generates a 'Number of Contributing Developers' (NCD) report based on configuration settings defined in a configuration file. A sample configuration file can be generated using the 'fcli license ncd-report create-config' command.\n
 fcli.license.ncd-report.create.usage.description.1 = The configuration file includes rich settings for specifying the source code repositories from which to load contributing developer data (supporting multiple Source Code Management (SCM) systems), and for ignoring and de-duplicating contributing authors. \n
 fcli.license.ncd-report.create.usage.description.2 = The generated report consists of multiple files, written to either a directory or zip-file. The primary output file is 'summary.txt' that contains various statistics, including the de-duplicated count of contributing developers. Various CSV files are generated with supporting proof, like the list of contributing authors, the list of commits that have been processed, and the list of repositories that have been processed.\n 
 fcli.license.ncd-report.create.usage.description.3 = The generated 'checksums.sha256' file can be used to verify integrity of all generated files, using a command like 'sha256sum -c checksums.sha256'.

fcli-core/fcli-sc-dast/src/main/resources/com/fortify/cli/sc_dast/i18n/SCDastMessages.properties

@@ -91,7 +91,7 @@ fcli.sc-dast.session.list.usage.description.1 = For sessions created using user
   of this command will show session expiry date and status, based on the data provided by SSC at the time \
   the login command was issued. Any changes to the generated token will not be reflected in the output of \
   this command. Even if a session is no longer valid because the generated token was revoked (through SSC \
-  UI or 'fcli ssc token revoke' command), the output of this command may still show the session as not having \
+  UI or 'fcli ssc access-control revoke-token' command), the output of this command may still show the session as not having \
   expired. Similarly, any changes to token validity will not be reflected in the output of this command. %n
 fcli.sc-dast.session.list.usage.description.2 = For sessions created using a pre-generated token, fcli cannot \
   display session expiration date or status, as SSC doesn't allow for obtaining this information.

fcli-core/fcli-sc-sast/src/main/resources/com/fortify/cli/sc_sast/i18n/SCSastMessages.properties

@@ -96,7 +96,7 @@ fcli.sc-sast.session.list.usage.description.1 = For sessions created using user
   of this command will show session expiry date and status, based on the data provided by SSC at the time \
   the login command was issued. Any changes to the generated token will not be reflected in the output of \
   this command. Even if a session is no longer valid because the generated token was revoked (through SSC \
-  UI or 'fcli ssc token revoke' command), the output of this command may still show the session as not having \
+  UI or 'fcli ssc access-control revoke-token' command), the output of this command may still show the session as not having \
   expired. Similarly, any changes to token validity will not be reflected in the output of this command. %n
 fcli.sc-sast.session.list.usage.description.2 = For sessions created using a pre-generated token, fcli cannot \
   display session expiration date or status, as SSC doesn't allow for obtaining this information.

fcli-core/fcli-util/src/main/resources/com/fortify/cli/util/i18n/UtilMessages.properties

@@ -41,7 +41,7 @@ fcli.util.auto-complete.generate.usage.description.2 = \u0020\u0020source <(${PA
 # fcli util crypto
 fcli.util.crypto.usage.header = Encrypt and decrypt data.
 fcli.util.crypto.usage.description.0 = These commands allow for encrypting and decrypting string values using fcli built-in encryption mechanism and password. The password can be customized through the FCLI_ENCRYPT_KEY environment variable, obviously the same password should be configured during encryption and decryption.
-fcli.util.crypto.usage.description.1 = Note that for now, encryption and decryption is not compatible with Fortify's pwtool utility. These commands are mainly meant to allow encrypted passwords to be stored in fcli configuration files, for example as used by the 'fcli util msp-report' and 'fcli util ncd-report' commands.
+fcli.util.crypto.usage.description.1 = Note that for now, encryption and decryption is not compatible with Fortify's pwtool utility. These commands are mainly meant to allow encrypted passwords to be stored in fcli configuration files, for example as used by the 'fcli license msp-report' and 'fcli license ncd-report' commands.
 fcli.util.crypto.encrypt.usage.header = Encrypt a value.
 fcli.util.crypto.encrypt.prompt = Value to encrypt:
 fcli.util.crypto.decrypt.usage.header = Decrypt a value.