style(help): remove polaris from the introduction
<#-- kk edited 1.8.20 -->
# Introduction
-${solution_name} analyzes your software project to identify open source component dependencies.
+${solution_name} analyzes your software project to identify open source component dependencies,
+and uploads the identities of those components to ${blackduck_product_name}(tm) for use in
+constructing a open source software Bill Of Materials (BOM) for your project.
+
+${solution_name} discovers components by utilizing both the ${blackduck_product_name} signature scanner
+and the package manager(s) your project uses to manage dependencies.
-${solution_name} consolidates the functionality of ${blackduck_product_name}(tm) and Coverity(tm) on Polaris(tm) to support
-Software Composition Analysis (SCA: open source software detection) and Static Application Security Testing (SAST: static code analysis).
${solution_name} makes it easier to set up and scan code bases for a variety of languages and package managers.
${solution_name} leverages multi-factor discovery techniques to scan software projects and directories.
${solution_name} runs on Windows, Linux, and MacOS. It is available through GitHub, under a permissive
Apache license and does not require pre-installation or configuration.
For more information, refer to [Requirements](../10-requirements/).
-${solution_name} can be used either for ${blackduck_product_name} SCA (open source software detection), or for Coverity on Polaris SAST (static code) analysis, or both simultaneously.
Although ${solution_name} can support large projects, care should be taken to ensure that scans are performed to optimize platform performance and produce manageable and meaningful results.
For applications containing multiple sub-projects, it may be advantageous to scan sub-projects separately and combine results as a project of projects, or other techniques.
