The below changes have been triggered by this slack thread and advised by jleflete@redhat.com

1) Add this requirement in the UI & CLI guides:
If the application being analyzed requires any sort of credentials to access private , these should be provided using the Administration/Credentials section. Otherwise, there might be an impact on the quality of the analysis, the issues yielded, and/or the performance.

2) At the end of the UI guide, section 4.2.2. Configuring Maven credentials, add:
When you create a credential, you have the option of making it a default credential, which will be used by default, if an application is not assigned one.
Otherwise, you need to assign the credential manually before analyzing
Otherwise it won't be picked up.

• Need to check if the option of making credential the default exists for CLI, and if yes document it there too.

3) Add a known issue: When maven credentials are missing it might cause analysis to take longer, and the Analyzer and Tech Discovery steps complete with error: 'unable to ask for Konveyor rule entry'

4) Add in the UI guide a section for Disconnected environment with:
A. Details on how to install the MTA operator Cancelled as there is no need to document this for MTA, as it is considered a common knowledge for Openshift operators in general, and there's nothing MTA specific here.
B. A note on the different number of incidents due to not having access to maven central (same note that is in the CLI guide, Disconnection section).
C. A note that if there is no access to the internet, BUT there is access to a Maven proxy then analysis should work fine. Otherwise Maven can't build the application, without accessing all the dependencies.