continue cleanup

semgrep · Nov 8, 2024 · a9885fa · a9885fa
1 parent d60b26e
commit a9885fa
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 8 deletions.
diff --git a/docs/deployment/add-semgrep-to-ci.md b/docs/deployment/add-semgrep-to-ci.md
@@ -53,7 +53,7 @@ If your provider is **not** on this list, you can still integrate Semgrep into y
 
 ## Projects
 
-Adding a Semgrep job to your CI provider also adds the repository's records, including findings, as a **project** in Semgrep AppSec Platform. Each Project can be individually configured to send notifications or tickets.
+Adding a Semgrep job to your CI provider creates a project with that repository's name. Projects in Semgrep encapsulate all findings and settings for that repository. Each Project can be individually configured to send notifications or tickets.
 
 ![Semgrep Projects page](/img/projects-page.png)
 _**Figure.** Semgrep **Projects** page. This displays all the repositories you have successfully added a Semgrep job to._

diff --git a/docs/semgrep-assistant/getting-started.md b/docs/semgrep-assistant/getting-started.md
@@ -111,8 +111,8 @@ If [auto-triage](/semgrep-assistant/overview/#auto-triage), which allows you to
 ![MR comment from Semgrep Assistant in GitLab](/img/assistant-gl-comment.png#md-width)
 *Figure*. MR comment from Semgrep Assistant in GitLab.
 
-#### Missing PR and comments
-Semgrep Assistant messages only appear in your PR comments for rules that are set to Comment or Block mode on the Rule Management page. Ensure that:
+#### Missing PR comments
+Semgrep Assistant messages only appear in PR comments for rules that are set to **Comment** or **Block** mode in the Policies page. Ensure that:
 
 * You have set rules to Comment or Block mode.
   ![ Policies modes](/img/semgrep-assistant-comment.png#md-width)

diff --git a/docs/semgrep-code/triage-remediation.md b/docs/semgrep-code/triage-remediation.md
@@ -48,8 +48,8 @@ The following sections show you have to manage your findings by:
 
 Note that some actions, such as ignoring and reopening findings, require different steps based on whether you have chosen **Group by Rule** or **No Grouping** when viewing your results on the **Findings** page.
 
-![Screenshot of Semgrep AppSec Platform triage menu](/img/app-findings-triage.png#md-width)
-
+![Screenshot of Semgrep AppSec Platform triage menu.](/img/app-findings-triage.png)
+_**Figure**. Screenshot of Semgrep AppSec Platform triage menu._
 ### Fix a finding
 
 To **fix a finding**, update or refactor the code such that the Semgrep rule pattern no longer matches the code.

diff --git a/src/components/reference/_extensions-ides.md b/src/components/reference/_extensions-ides.md
@@ -1,3 +1,3 @@
-- Microsoft Visual Studio Code: [`semgrep-vscode`](https://marketplace.visualstudio.com/items?itemName=semgrep.semgrep)
-- IntelliJ Ultimate Idea (and most other IntelliJ products) [`semgrep-intellij`](https://plugins.jetbrains.com/plugin/22622-semgrep)
-- Emacs: [`lsp-mode`](https://github.com/emacs-lsp/lsp-mode)
+- Microsoft Visual Studio Code: [**<i class="fas fa-external-link fa-xs"></i> semgrep-vscode**](https://marketplace.visualstudio.com/items?itemName=semgrep.semgrep)
+- IntelliJ Ultimate Idea (and most other IntelliJ products): [**<i class="fas fa-external-link fa-xs"></i> semgrep-intellij**](https://plugins.jetbrains.com/plugin/22622-semgrep)
+- Emacs: [**<i class="fas fa-external-link fa-xs"></i> lsp-mode**](https://github.com/emacs-lsp/lsp-mode)