Merge pull request #1072 from blackducksoftware/cp_IDETECT-4273_doc

company_name fix

Author: cpottsbd

documentation/src/main/markdown/currentreleasenotes.md

@@ -4,11 +4,11 @@
 
 ### New features
 
-* [company_name] [solution_name] now includes the maven embedded or shaded dependencies as part of the Bill of Materials (BOM) via the property --detect.maven.include.shaded.dependencies. See the [detect.maven.include.shaded.dependencies](properties/detectors/maven.md#maven-include-shaded-dependencies) property for more information.
-* [company_name] [solution_name] Maven Project Inspector now supports the exclusion of maven dependencies having "\<exclude\>" tags in the pom file.
+* [company_name] [solution_name] now includes the Maven embedded or shaded dependencies as part of the Bill of Materials (BOM) via the property --detect.maven.include.shaded.dependencies. See the [detect.maven.include.shaded.dependencies](properties/detectors/maven.md#maven-include-shaded-dependencies) property for more information.
+* [company_name] [solution_name] Maven Project Inspector now supports the exclusion of Maven dependencies having "\<exclude\>" tags in the pom file.
 * [company_name] [solution_name] Maven Project Inspector and Gradle Project Inspector honours effects of dependency scopes during dependency resolution.
 
 ### Dependency updates
 
 * Upgraded Project Inspector to version 2024.2.0. Please refer to [Maven](packagemgrs/maven.md), [Gradle](packagemgrs/gradle.md) and [Nuget](packagemgrs/nuget.md) documentation for more information on the changes.
-  As of version 9.5.0 [company_name][solution_name] will only be compatible with, and support, Project Inspector 2024.2.0 or later.
+  As of version 9.5.0 [company_name] [solution_name] will only be compatible with, and support, Project Inspector 2024.2.0 or later.

documentation/src/main/markdown/integrations/acr/azurecontainerregistry.md

@@ -94,7 +94,7 @@ Start in **Pipelines > Library** inside Azure DevOps.
 #/bin/bash
 #Log in to ACR using the configured Variable Group
 docker login <registryname>.azurecr.io -u $(acr.username) -p $(acr.password)
-#Call [company_name] [solution_name], passing the Docker Image location
+#Call Detect, passing the Docker Image location
 bash <(curl -s -L https:‎ //detect.synopsys.com/detect9.sh) \
 --blackduck.url=$(blackduck.url) \
 --blackduck.api.token=$(blackduck.api.token) \ 

documentation/src/main/markdown/packagemgrs/docker/advanced.md

@@ -138,10 +138,10 @@ the top layer ID for ubuntu:latest changes over time.)
 Set the value of the [company_name] [solution_name] property *detect.docker.platform.top.layer.id* to the platform top layer ID.
 For example:
 
-    {[company_name] [solution_name] command} ... --docker.platform.top.layer.id=sha256:b079b3fa8d1b4b30a71a6e81763ed3da1327abaf0680ed3ed9f00ad1d5de5e7c
+    {Detect command} ... --docker.platform.top.layer.id=sha256:b079b3fa8d1b4b30a71a6e81763ed3da1327abaf0680ed3ed9f00ad1d5de5e7c
 
 In this mode, the container file system and/or container file system squashed image produced by [docker_inspector_name]
- only contains files added to the image by application layers. If the Black Duck signature scanner is run on this file,
+ only contains files added to the image by application layers. If the [blackduck_product_name] signature scanner is run on this file,
 it generates results based only on files found on application layers. This provides the benefit of isolating
 application components by excluding platform components. However, there may be some loss in match accuracy from the
 signature scanner because in this scenario, the signature scanner may be deprived of some contextual

documentation/src/main/markdown/packagemgrs/gradle.md

@@ -46,4 +46,4 @@ The buildless gradle detector uses Project Inspector to find dependencies and do
 It currently supports "build.gradle" and does not support Kotlin build files.
 
 As of [company_name] [solution_name] 9.5.0 the version of Project Inspector in use supports the `--build-system GRADLE` argument in place of `--strategy GRADLE`.
-The `--force-gradle-repos "url"` argument will be removed from support in the next [company_name][solution_name] major release and replaced with the `--conf "maven.repo:url"` argument.
+The `--force-gradle-repos "url"` argument will be removed from support in the next [company_name] [solution_name] major release and replaced with the `--conf "maven.repo:url"` argument.

documentation/src/main/markdown/packagemgrs/maven.md

@@ -73,4 +73,4 @@ The Maven Project Inspector detector uses Project Inspector, which currently doe
 The Maven Project Inspector includes the shaded dependencies as part of the BOM.
 
 As of [company_name] [solution_name] 9.5.0 the version of Project Inspector in use supports the `--build-system MAVEN` argument in place of `--strategy MAVEN`.
-The `--force-maven-repos "url"` argument will be removed from support in the next [company_name][solution_name] major release and replaced with the `--conf "maven.repo:url"` argument.
+The `--force-maven-repos "url"` argument will be removed from support in the next [company_name] [solution_name] major release and replaced with the `--conf "maven.repo:url"` argument.

documentation/src/main/markdown/packagemgrs/nuget.md

@@ -78,7 +78,7 @@ After discovering dependencies, NuGet client libraries are used to collect furth
 In buildless mode, [company_name] [solution_name] uses Project Inspector to find dependencies and only supports `.csproj` and `.sln` files.
 
 As of [company_name] [solution_name] 9.5.0 the version of Project Inspector in use supports the `--build-system MSBUILD` argument in place of `--strategy MSBUILD`.
-The `--force-nuget-repos "url"` argument will be removed from support in the next [company_name][solution_name] major release and replaced with the `--conf "nuget.repo:url"` argument.
+The `--force-nuget-repos "url"` argument will be removed from support in the next [company_name] [solution_name] major release and replaced with the `--conf "nuget.repo:url"` argument.
 
 ### [company_name] [solution_name] NuGet Inspector on Alpine