style(help): updated common problems page
- For issues related to tools invoked by [solution_name] ([blackduck_signature_scanner_name], Docker Inspector, etc.), please check that tool's documentation.
- For issues related to incorrect components in the [blackduck_product_name] BOM: [solution_name] has a great deal of control over matches produced by detectors (that are written to BDIO files), but no control over matches produced by the [blackduck_signature_scanner_name] / [blackduck_product_name]. When investigating an incorrect component in a [blackduck_product_name] BOM, you need to determine whether the component was contributed by a detector, or by the [blackduck_signature_scanner_name]: On the [blackduck_product_name] Components tab for the project/version: Click on the "N Matches" link next to the component. The next screen lists the matches on the right side. Matches from the [blackduck_signature_scanner_name] have a filename in the Name column. Matches from detectors have an external ID (such as "org.hamcrest:hamcrest-core:1.3") in the Name column.
-- For issues related to components missing from or or incorrectly categorized in the [blackduck_product_name] BOM: [solution_name] has a great deal of control over the production of BDIO files (use [--detect.diagnostic.extended](../properties/configuration/debug.md#diagnostic-mode-extended) to save these), but no control over how they are converted into a BOM by [blackduck_product_name]. A good first step is to determine whether the BDIO files produced are correct. If they are incorrect, the problem is related to what [solution_name] is doing. If they are correct, but the BOM is incorrect, the problem is related to what [blackduck_product_name] is doing. Similarly, [solution_name] is responsible for passing the correct arguments to the [blackduck_signature_scanner_name], but beyond that has no control over the results it produces.
+- For issues related to components missing from or or incorrectly categorized in the [blackduck_product_name] BOM: [solution_name] has a great deal of control over the production of BDIO files (use [--detect.diagnostic](../properties/configuration/debug.md#diagnostic-mode) to save these), but no control over how they are converted into a BOM by [blackduck_product_name]. A good first step is to determine whether the BDIO files produced are correct. If they are incorrect, the problem is related to what [solution_name] is doing. If they are correct, but the BOM is incorrect, the problem is related to what [blackduck_product_name] is doing. Similarly, [solution_name] is responsible for passing the correct arguments to the [blackduck_signature_scanner_name], but beyond that has no control over the results it produces.
## Spring Boot related issues
