[App-Sec] Various fixes

docs/en/enterprise-edition/content-collections/application-security/familiarize-application-security.adoc

@@ -26,7 +26,7 @@ Real time, ongoing, comprehensive and accurate analysis of your technical stack,
 
 View your software development life cycle (SLDC) as a graphical representation. This visibility allows you to perform an in-depth analysis of security issues across your entire engineering ecosystem. You can digest and understand the assets in your environment, and the relationships between them.
 
-For more see xref:../../search-and-investigate/investigate-appsec/investigate-appsec.adoc[ Application Asset Queries].
+For more see xref:../../search-and-investigate/application-asset-queries/application-asset-queries.adoc[Application Asset Queries]
 
 === Risk Management
 

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/add-private-registries.adoc

@@ -56,7 +56,7 @@ NOTE: NPM requires you to define your repository as *Private*.
 
 === Remediation
 
-You can remediate vulnerabilities detected on private registries through *Application Security > *Home* > *Projects* > *Vulnerabilities*.
+You can remediate vulnerabilities detected on private registries through *Application Security* > *Home* > *Projects* > *Vulnerabilities*.
 
 === Manage Integrations
 

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-runs/add-github-actions.adoc

@@ -34,7 +34,7 @@ NOTE: Access key format: `PRISMA_ACCESS_KEY::PRISMA_SECRET_KEY`.
 . Copy and paste the following code from the *Configure Job* step of the integration wizard into your GitHub Actions job configuration.
 +
 NOTE: Modify the env *prisma-api-url* value according to your environment. 
-
++
 [source.yml]
 ----
 steps:

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-runs/add-jenkins.adoc

@@ -70,8 +70,8 @@ pipeline {
 ----
 +
 NOTE: Replace the placeholder strings in the code with your Prisma Cloud access key ID and secret.
-+
-Select *Done*.
+
+. Select *Done*.
 
 . Verify integration: In *Application Security*, select *Home* > *Settings* > *CI/CD Runs* tab.
 +

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-systems/add-circleci-cicd-system.adoc

@@ -61,7 +61,7 @@ The next scan of your CircleCI systems will include the new integration, and the
 [.task]
 
 [#multi-integrate]
-=== Support for multiple integrations
+=== Support for Multiple Integrations
 
 Prisma Cloud supports multiple integrations for CircleCI instances.
 
@@ -86,7 +86,7 @@ The new integration is displayed on the landing page of the integration wizard.
 
 Manage integrations from the integration wizard.
 
-. Access the CircleCi integration wizard - see *step 1* of <<multi-integrate,Support for multiple integrations>> above > select the menu under *Actions*.
+. Access the CircleCi integration wizard - see *step 1* of <<multi-integrate,Support for Multiple Integrations>> above > select the menu under *Actions*.
 +
 From _Actions_ you can:
 

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-systems/add-jenkins-cicd-system.adoc

@@ -85,7 +85,7 @@ The next scan of your Jenkins servers will include the new integration, and the
 
 [.task]
 [#support-multi-integrate]
-=== Support for multiple integrations
+=== Support for Multiple Integrations
 
 Prisma Cloud supports multiple integrations for Jenkins Server instances.
 
@@ -113,7 +113,7 @@ Manage integrations from the integration wizard.
 
 [.procedure]
 
-. Access the Jenkins integration wizard - see *step 1* of <<support-multi-integrate,Support for multiple integrations>> above > select the menu under *Actions*.
+. Access the Jenkins integration wizard - see *step 1* of <<support-multi-integrate,Support for Multiple Integrations>> above > select the menu under *Actions*.
 
 . From _Actions_ you can:
 

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/code-repositories/add-bitbucket-server.adoc

@@ -17,7 +17,7 @@ NOTE: Integrating with Bitbucket Server extends support for Bitbucket Data Cente
 .. Grant *Administrator* permissions in the relevant Bitbucket organization to the Prisma user integrating Prisma Cloud with Bitbucket.
 
 . On the Prisma Cloud Application Security console.
-.. Select *Settings > *Connect Provider* > *Code & Build Providers*.
+.. Select *Settings* > *Connect Provider* > *Code & Build Providers*.
 +
 image::application-security/connect-provider-menu.png[]
 

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/code-repositories/add-github.adoc

@@ -34,14 +34,14 @@ You are redirected to GitHub to authorize Prisma Cloud access.
 . Authorize Prisma Cloud on GitHub. 
 .. Select *Authorize* to authenticate your account through your SSO provider > complete the required process.
 
-. Select *Authorize Prisma Cloud DevOps*.
+.. Select *Authorize Prisma Cloud DevOps*.
 +
-image::application-security/github-auth-prisma.png[]
+image::application-security/github-auth-prisma1.1.png[]
 
 .. Select the organization on which Prisma Cloud will be installed.
 .. Select the repositories to be authorized:
 +
-image::application-security/github-select-repos.png[]
+image::application-security/github-select-repos1.1.png[]
 +
 * *All repositories* applies to all current and future repositories owned by the resource owner 
 +

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/code-repositories/add-gitlab-selfmanaged.adoc

@@ -76,7 +76,7 @@ NOTE: It may take up to 3 minutes for the integration status to be updated and s
 
 [.task]
 [#multi-integrate]
-=== Support for multiple integrations
+=== Support for Multiple Integrations
 
 Prisma Cloud supports multiple integrations for GitLab Self-Managed. After the initial integration with Prisma Cloud, you can continue to add additional organizations and workspaces using a different or the same user or team token.
 
@@ -85,7 +85,7 @@ Multiple integrations from a single Prisma Cloud account enables you to:
 * View a list of integrations on a single console
 * Add additional integrations.
 * Delete an existing integration
-+
+
 NOTE: Selecting a repository for a specific integration will restrict you from selecting the same repository in another integration.
 
 [.procedure]

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/code-repositories/add-gitlab.adoc

@@ -30,7 +30,7 @@ image::application-security/connect-provider.png[]
 +
 You are redirected to GitLab to authorize Prisma Cloud access.
 +
-image::application-security/gitlab-auth.png[]
+image::application-security/gitlab-auth1.1.png[]
 
 . On GitLab, review the requested permissions > *Authorize*.
 +
@@ -63,7 +63,7 @@ NOTE: It may take up to 3 minutes for the integration status to be updated and s
 [.task]
 
 [#multi-integrate-]
-=== Support for multiple integrations
+=== Support for Multiple Integrations
 
 Prisma Cloud supports multiple integrations for GitLab. After the initial integration with Prisma Cloud, you can continue to add additional organizations and workspaces using a different or a same user or team token.
 
@@ -73,7 +73,7 @@ Multiple integrations from a single Prisma Cloud account enables you to:
 //* Update existing integrations by modifying the selection of workspaces
 * Add additional integrations
 * Delete an existing integration
-+
+
 NOTE: Selecting a repository for a specific integration will restrict you from selecting the same repository in another integration.
 
 [.procedure]

docs/en/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/connect-code-and-build-providers.adoc

@@ -30,8 +30,8 @@ a|
 * xref:code-repositories/add-gitlab.adoc#multi-integrate[Multiple integrations for GitLab]
 * xref:code-repositories/add-gitlab-selfmanaged.adoc#multi-integrate[Multiple integrations for GitLab Self-Managed]
 
-|Add additional Jenkins Plugins integrations
-|xref:ci-cd-systems/add-jenkins-cicd-system.adoc#support-multi-integrate[Multiple Jenkins Plugins integrations]
+|Add additional Jenkins Server integrations
+|xref:ci-cd-systems/add-jenkins-cicd-system.adoc#support-multi-integrate[Multiple Jenkins Server integrations]
 
 |Add additional CircleCI integrations
 |xref:ci-cd-systems/add-circleci-cicd-system.adoc#multi-integrate[Multiple CircleCI integrations]
@@ -66,7 +66,7 @@ image::application-security/connect-provider.png[]
 === Verify Integration
 
 To verify integration, in *Application Security*, select *Home* > *Settings*.
-+
+
 image::verify-integration1.0.png[]
 
 

docs/en/enterprise-edition/content-collections/application-security/get-started/manage-network-tunnel/deploy-transporter-docker.adoc

@@ -53,7 +53,7 @@ image::application-security/transporter-12.png[]
 ** Copy and paste the command from the *Docker-Compose CLI Command* field in your CLI terminal to run the 'docker-compose' command
 +
 Once the connection is established, Transporter will use WebSockets to communicate with each other.
-
++
 NOTE: The `-d` value in the command is used to specify the name of the Docker compose yml file.
 
 . Select *Next* > *Done* to complete the integration.
@@ -62,7 +62,7 @@ Only after the Transporter has run successfully can Prisma Cloud authenticate an
 
 You can view the integrated Transporter in Application Security through *Home* > *Settings > Manage Network Tunnels > Manage Integrations*.
 
-You can add a new Transporter to an VCS integration in Application Security through *Home* >  *Settings* > *Manage Network Tunnels* > *Manage Integrations* > *New Transporter*.
+You can add a new Transporter to an VCS integration in Application Security through *Home* > *Settings* > *Manage Network Tunnels* > *Manage Integrations* > *New Transporter*.
 
 Adding the Transporter to an integration establishes the communication channel between the VCS and Prisma Cloud. In this example, the GitLab Self-managed integration to Prisma Cloud uses the Transporter.
 

docs/en/enterprise-edition/content-collections/application-security/visibility/repositories.adoc

@@ -70,7 +70,7 @@ NOTE: You can also access a repository's graph from *Actions* in the Repository
 * *VCS*: Filter type of version control system detected in the environment
 * *Archived*: Filter by archived/un-archived repositories 
 
-[#appgraph-]
+[#appgraph]
 
 === Application Graph