managed scanning to scans (#2415)

Co-authored-by: Abhijna Parigi <Abhijna@MacBook-Pro.local>

Author: abhijna

docs/deployment/connect-scm.md

@@ -208,7 +208,7 @@ You have successfully connected an org in Semgrep AppSec Platform with an organi
 1. Click **Connect** to save and proceed.
 1. The Bitbucket project is now listed under **Source code managers**. Click **Test** to verify that the new connection was installed correctly.
 1. To enable merge request comments, click **<i class="fa-solid fa-toggle-large-on"></i> Incoming webhooks**.
-1. Optional: Click **Auto scan** to onboard all current and future repositories under your project to Semgrep Managed Scanning.
+1. Optional: Click **Auto scan** to onboard all current and future repositories under your project to Semgrep Managed Scans.
 
 </TabItem>
 <TabItem value='github-enterprise'>

docs/deployment/core-deployment.md

@@ -82,7 +82,7 @@ These are the absolute minimum Semgrep features for any deployment.
             <td>Semgrep fully supports many popular CI providers. See <a href="/docs/deployment/add-semgrep-to-ci"><i class="fa-regular fa-file-lines"></i> Add Semgrep to CI</a>.</td>
         </tr>
         <tr>
-            <td>Managed scanning: scanning remote repositories in bulk without CI changes</td>
+            <td>Managed Scans: scanning remote repositories in bulk without CI changes</td>
             <td>An alternative method of scanning many repositories with Semgrep that doesn't require integration with your CI. Requires read access to user-selected repositories. See <a href="/docs/deployment/managed-scanning/overview"><i class="fa-regular fa-file-lines"></i> Add repositories to Semgrep in bulk</a>.</td>
         </tr>
         <tr>

docs/deployment/deployment-checklist.md

@@ -253,7 +253,7 @@ The public GitHub integration app is called [`semgrep-app`](https://github.com/a
 </details>
 
 
-##### Permissions when adding repositories into Semgrep AppSec Platform through managed scanning or using AI features
+##### Permissions when adding repositories into Semgrep AppSec Platform through Semgrep Managed Scans or using AI features
 
 You can optionally create a private GitHub app, which follows the naming convention **Semgrep Code - <span className="placeholder">YOUR_ORG_NAME</span>**. This private app is used for the following features:
 
@@ -266,7 +266,7 @@ These features require **read access** to your code.
 
 <details>
 
-<summary>Click to review how Semgrep AppSec Platform uses permissions when adding repositories through <strong>managed scanning</strong>.</summary>
+<summary>Click to review how Semgrep AppSec Platform uses permissions when adding repositories through <strong>Semgrep Managed Scans</strong>.</summary>
 
 <dl>
 <dt>Reading metadata of the repositories you select</dt>

docs/deployment/managed-scanning/azure.md

@@ -20,10 +20,10 @@ Add Azure DevOps repositories to your Semgrep organization in bulk without addin
 
 ## Prerequisites and permissions
 
-- Semgrep Managed Scanning requires repositories hosted by Azure DevOps Services. It doesn't support Azure DevOps Server.
-- Semgrep recommends setting up and configuring Semgrep Managed Scanning with an Azure DevOps service account, not a personal account. Regardless of whether you use a personal or service account, the account must be assigned the **Owner** or **Project Collection Administrator** role for the organization.
+- Semgrep Managed Scans require repositories hosted by Azure DevOps Services. Azure DevOps Server is not supported.
+- Semgrep recommends setting up and configuring Semgrep Managed Scans with an Azure DevOps service account, not a personal account. Regardless of whether you use a personal or service account, the account must be assigned the **Owner** or **Project Collection Administrator** role for the organization.
 - During setup and configuration, you must provide a personal access token generated by the account. This token must be authorized with **Full access**.
-  - Once you have Managed Scanning fully configured, you can update the token provided to Semgrep to one that's more restrictive. The scopes you must assign to the token include:
+  - Once you have Managed Scans fully configured, you can add restrictions to the token provided to Semgrep. The scopes you must assign to the token include:
     - `Code: Read`
     - `Code: Status`
     - `Member Entitlement Management: Read`
@@ -50,7 +50,7 @@ You have finished setting up a Semgrep managed scan. Click **Back to Managed Sca
 
 ## Add additional Azure DevOps projects
 
-You can enable managed scanning for additional repositories after onboarding using the following steps:
+You can enable Semgrep Managed Scans for additional repositories after onboarding using the following steps:
 
 <!-- vale off -->
 1. In Semgrep AppSec Platform, click **<i class="fa-solid fa-folder-open"></i> Projects**.
@@ -89,7 +89,7 @@ Semgrep preserves your findings, scans, and triage history.
 
 ## Disable webhooks
 
-Managed scanning of Azure DevOps projects requires webhooks. The webhooks are enabled by default when you add Azure DevOps as a source code manager when setting up Managed Scanning. Webhooks are required for diff-aware scans and triaging by PR or MR comments.
+Managed Scans of Azure DevOps projects require webhooks. The webhooks are enabled by default when you add Azure DevOps as a source code manager when setting up Managed Scans. Webhooks are required for diff-aware scans and triaging by PR or MR comments.
 
 You can turn off webhooks at any time by following these steps:
 
@@ -140,7 +140,7 @@ See [Configure a branch policy for an external service](https://learn.microsoft.
 
 ## Troubleshooting: multiple projects
 
-If you currently scan Azure DevOps repositories in your CI pipeline, you may see findings assigned to two separate projects once you enable Semgrep Managed Scanning. For example, findings from Managed Scanning go to the `semgrep/frontend/webpage` project, while findings from CI scans go to the `frontend/webpage` project. If this is the case, Semgrep AppSec Platform flags these findings with **Possible duplicate**. Please [contact support](/support) for addition assistance.
+If you currently scan Azure DevOps repositories in your CI pipeline, you may see findings assigned to two separate projects once you enable Semgrep Managed Scans. For example, findings from Managed Scans go to the `semgrep/frontend/webpage` project, while findings from CI scans go to the `frontend/webpage` project. If this is the case, Semgrep AppSec Platform flags these findings with **Possible duplicate**. Please [contact support](/support) for addition assistance.
 
 ## Appendices
 

docs/deployment/managed-scanning/bitbucket.md

@@ -19,14 +19,14 @@ Add Bitbucket repositories to your Semgrep organization in bulk without adding o
 
 ## Prerequisites and permissions
 
-Semgrep Managed Scanning requires one of the following plans:
+Semgrep Managed Scans require one of the following plans:
 
 - Bitbucket Cloud Premium
 - Bitbucket Data Center (v8.8 or above for diff-aware scans)
 
 ### Bitbucket Cloud
 
-You must provide a Bitbucket [workspace access token](https://support.atlassian.com/bitbucket-cloud/docs/workspace-access-tokens/) to Semgrep, which can be created by a user with the `Product Admin` role. Once you have Managed Scanning fully configured, you can update the token provided to Semgrep to one that's more restrictive. The scopes you must assign to the token include:
+You must provide a Bitbucket [workspace access token](https://support.atlassian.com/bitbucket-cloud/docs/workspace-access-tokens/) to Semgrep, which can be created by a user with the `Product Admin` role. Once you have Semgrep Managed Scans fully configured, you can update the token provided to Semgrep to one that's more restrictive. The scopes you must assign to the token include:
 
 - `webhook (read and write)`
 - `repository (read and write)`
@@ -38,11 +38,11 @@ Webhook permissions are required to support diff-aware scans.
 
 ### Bitbucket Data Center
 
-You must provide a Bitbucket [HTTP access token](https://confluence.atlassian.com/bitbucketserver/http-access-tokens-939515499.html) to Semgrep, which can be created by a user with the `Project Admin` role. This access token must be created with with `PROJECT_ADMIN` permissions.
+You must provide a Bitbucket [HTTP access token](https://confluence.atlassian.com/bitbucketserver/http-access-tokens-939515499.html) to Semgrep, which can be created by a user with the `Project Admin` role. This access token must be created with `PROJECT_ADMIN` permissions.
 
 Project-level webhooks are required to support diff-aware scans.
 
-## Enable Managed Scanning and scan your first repository
+## Enable Semgrep Managed Scans and scan your first repository
 
 <!-- vale off -->
 1. In Semgrep AppSec Platform, click **<i class="fa-solid fa-folder-open"></i> Projects**.
@@ -92,7 +92,7 @@ You can enable Managed Scans for additional repositories after onboarding using
 
 You can immediately add any existing project to Managed Scans.
 
-1. Follow the steps in [Enable managed scanning](#enable-managed-scanning-and-scan-your-first-repository).
+1. Follow the steps in [Enable Semgrep Managed Scans](#enable-managed-scanning-and-scan-your-first-repository).
 1. Delete the `bitbucket-pipelines.yml` file in your Bitbucket repository if appropriate.
 
 If you plan to continue running some scans in Bitbucket CI/CD Pipelines (for example, using Managed Scans to run weekly full scans but Bitbucket CI/CD Pipelines for diff-aware scans) you can leave the workflow file in place, and edit it to reflect your desired configuration.
@@ -107,7 +107,7 @@ Semgrep preserves your findings, scans, and triage history.
 
 ## Disable webhooks
 
-Performing diff-aware Managed Scans of Bitbucket projects requires webhooks to be enabled. Webhooks are enabled by default when you add Bitbucket as a source code manager when setting up Managed Scanning. You can disable webhooks at any time by following these steps:
+Performing diff-aware Managed Scans of Bitbucket projects requires webhooks to be enabled. Webhooks are enabled by default when you add Bitbucket as a source code manager when setting up Semgrep Managed Scans. You can disable webhooks at any time by following these steps:
 
 1. In Semgrep AppSec Platform, go to [Settings > Source code managers](https://semgrep.dev/orgs/-/settings/source-code).
 2. Find your Bitbucket connection, and click the <i class="fa-solid fa-toggle-large-on"></i> toggle to disable **Incoming webhooks**.

docs/deployment/managed-scanning/gitlab.md

@@ -24,7 +24,7 @@ Add GitLab repositories to your Semgrep organization in bulk without adding or c
 
 See [Pre-deployment checklist > Permissions](/deployment/checklist#permissions) for more information about the permissions used by Semgrep.
 
-## Enable Managed Scanning and scan your first repository
+## Enable Semgrep Managed Scans and scan your first repository
 
 <!-- vale off -->
 1. In Semgrep AppSec Platform, click **<i class="fa-solid fa-folder-open"></i> Projects**.
@@ -50,7 +50,7 @@ You have finished setting up a Semgrep managed scan.
 
 ## Add additional GitLab projects
 
-You can enabled managed scanning for additional repositories after onboarding using the following steps:
+You can enable Semgrep Managed Scans for additional repositories after onboarding using the following steps:
 
 <!-- vale off -->
 1. In Semgrep AppSec Platform, click **<i class="fa-solid fa-folder-open"></i> Projects**.
@@ -77,7 +77,7 @@ You can enabled managed scanning for additional repositories after onboarding us
 
 You can immediately add any existing project to Managed Scans.
 
-1. Follow the steps in [Enable managed scanning](#enable-managed-scanning-and-scan-your-first-repository).
+1. Follow the steps in [Enable Semgrep Managed Scans](#enable-managed-scanning-and-scan-your-first-repository).
 1. Delete the `.gitlab-ci.yml` file in your GitLab repository if appropriate.
 
 If you plan to continue running some scans in GitLab CI/CD Pipelines (for example, using Managed Scans to run weekly full scans but GitLab CI/CD Pipelines for diff-aware scans) you can leave the workflow file in place, and edit it to reflect your desired configuration.
@@ -92,7 +92,7 @@ Semgrep preserves your findings, scans, and triage history.
 
 ## Disable webhooks
 
-Managed scanning of GitLab projects require webhooks. The webhooks are enabled by default when you add GitLab as a source code manager when setting up Managed Scanning. You can disable webhooks at any time by following these steps:
+Semgrep Managed Scans of GitLab projects require webhooks. The webhooks are enabled by default when you add GitLab as a source code manager when setting up Managed Scans. You can disable webhooks at any time by following these steps:
 
 1. In Semgrep AppSec Platform, go to [Settings > Source code managers](https://semgrep.dev/orgs/-/settings/source-code).
 2. Find your GitLab connection, and click the <i class="fa-solid fa-toggle-large-on"></i> toggle to disable **Incoming webhooks**.

docs/getting-started/introduction.md

@@ -23,7 +23,7 @@ Scan results can be triaged and remediated in the Semgrep AppSec Platform. The p
 
 * **Community Edition** (CE): is an open source static analysis tool that can find insecure coding patterns and security vulnerabilities in source code. Semgrep CE encompasses a SAST scanning engine, community rules, and integrated development environment plugins. The core scanner supports over 30 programming languages. [Get started with CE](/docs/getting-started/quickstart-ce).
 
-* **Semgrep AppSec Platform** (Pro): is a commercial offering recommended for enterprise use cases. It shares the command-line interface with CE and adds additional capabilities. Semgrep AppSec Platform Pro offers managed scanning at org scale, advanced (pro) rules, supply chain analysis, secrets detection, PR comments, and AI-assisted triage/fixes, and more. It supports over 35 programming languages, with new ones added regularly.
+* **Semgrep AppSec Platform** (Pro): is a commercial offering recommended for enterprise use cases. It shares the command-line interface with CE and adds additional capabilities. Semgrep AppSec Platform Pro offers Managed Scans at org scale, advanced (pro) rules, supply chain analysis, secrets detection, PR comments, and AI-assisted triage/fixes, and more. It supports over 35 programming languages, with new ones added regularly.
 
 ![](/img/appsecplatform-intro.png)
 

docs/getting-started/quickstart-sms.md

@@ -48,7 +48,7 @@ You must have admin access to your Azure DevOps organization.
 
 Read access is granted through an access token you generate on Azure DevOps. You can provide this token by [adding Azure DevOps as a source code manager](/deployment/connect-scm#connect-to-cloud-hosted-orgs).
 
-Semgrep recommends setting up and configuring Semgrep with an Azure DevOps service account, not a personal account. Regardless of whether you use a personal or service account, the account must be assigned the **Owner** or **Project Collection Administrator** role for the organization. During setup and configuration, you must provide a personal access token generated by this account. This token must be authorized with **Full access**. Once you have Managed Scanning fully configured, you can update the token provided to Semgrep to one that's more restrictive. The scopes you must assign to the token include:
+Semgrep recommends setting up and configuring Semgrep with an Azure DevOps service account, not a personal account. Regardless of whether you use a personal or service account, the account must be assigned the **Owner** or **Project Collection Administrator** role for the organization. During setup and configuration, you must provide a personal access token generated by this account. This token must be authorized with **Full access**. Once you have Semgrep Managed Scans fully configured, you can update the token provided to Semgrep to one that's more restrictive. The scopes you must assign to the token include:
 
 - `Code: Read`
 - `Code: Status`

docs/index.md

@@ -131,7 +131,7 @@ See the [Supported languages](/supported-languages#language-maturity-summary) do
 <h3>October 2025 release notes summary</h3>
 <!-- 5-7 bullets across the product suite -->
 
-- Semgrep Managed Scanning is now generally available. With Managed Scans, you can add repositories to your Semgrep organization in bulk without changing your existing CI workflows, and integrate Semgrep into developer workflows through PR or MR comments.
+- Semgrep Managed Scans are now generally available. With Managed Scans, you can add repositories to your Semgrep organization in bulk without changing your existing CI workflows, and integrate Semgrep into developer workflows through PR or MR comments.
 - Semgrep Code findings now show Assistant's true or false positive analyses more prominently, along with the memories Assistant used during analysis. The findings also present the threat model for specific security issues in the context of the code, along with a summary of each issue.
 - The `/setup_semgrep_mcp` command now supports Claude Code.
 - Supply Chain's reachability analysis now covers all high-severity CVEs from supported sources starting from 2017 for Go packages.

docs/semgrep-supply-chain/getting-started.md

@@ -107,7 +107,7 @@ Semgrep Supply Chain can scan projects without the need for lockfiles. This simp
     Semgrep builds the project, using the build information included in the `pom.xml` or `build.gradle` file to determine the set of dependencies used by the project. 
 
 :::info
-- Semgrep Managed Scanning can't determine the dependencies in a project when there is no manifest file or lockfile, so Supply Chain scans don't return any findings.
+- Semgrep Managed Scans can't determine the dependencies in a project when there is no manifest file or lockfile, so Supply Chain scans don't return any findings.
 - By default, Semgrep doesn't surface errors generated during a scan. To view errors in the CLI output, include the `--verbose` when initiating your scan:
     ```console
     semgrep ci --allow-local-builds --verbose