diff --git a/mintlify-docs/cheat-sheets/java-jsp-xss.mdx b/mintlify-docs/cheat-sheets/java-jsp-xss.mdx
index d2140d073..192941b29 100644
--- a/mintlify-docs/cheat-sheets/java-jsp-xss.mdx
+++ b/mintlify-docs/cheat-sheets/java-jsp-xss.mdx
@@ -27,7 +27,7 @@ semgrep --config p/minusworld.java-httpservlet-jsp-xss
 ### 1.A Using the **PrintWriter** from **HttpServletResponse**
 
 
-The `PrintWriter from `HttpServletResponse` permits writing data directly to the response that will be returned to the user. This bypasses any safety mechanisms built into any frameworks in use.
+The `PrintWriter` from `HttpServletResponse` permits writing data directly to the response that will be returned to the user. This bypasses any safety mechanisms built into any frameworks in use.
 
 Example:
 
diff --git a/mintlify-docs/customize-semgrep-ce.mdx b/mintlify-docs/customize-semgrep-ce.mdx
index 0e5bf1b49..f4e455c69 100644
--- a/mintlify-docs/customize-semgrep-ce.mdx
+++ b/mintlify-docs/customize-semgrep-ce.mdx
@@ -69,7 +69,7 @@ Semgrep collects pseudonymous metrics when you use rules from the Registry. You
 To scan your codebase with a specific ruleset, either one that you write or one that you obtain from the [ Semgrep Registry](https://semgrep.dev/explore), use the `--config` flag.
 
 ```bash
-# Scan with the the JavaScript rules from Semgrep Registry
+# Scan with the JavaScript rules from Semgrep Registry
 semgrep scan --config p/javascript
 ```
 
diff --git a/mintlify-docs/deployment/teams/overview.mdx b/mintlify-docs/deployment/teams/overview.mdx
index f7de928a5..5368bc473 100644
--- a/mintlify-docs/deployment/teams/overview.mdx
+++ b/mintlify-docs/deployment/teams/overview.mdx
@@ -101,7 +101,7 @@ Members and managers can create projects by scanning a repository using the Semg
 ## How team access works
 
 - Members of a top-level team gain access to the projects of its subteams. They are indirect members of a subteam.
-- Members of a subteam do not have access to the projects of teams or subteams above it.`
+- Members of a subteam do not have access to the projects of teams or subteams above it.
 
 In the following diagram, team 1 gains access to subteam 1b's projects, but team 1b does not gain access to projects from team 1.
 
diff --git a/mintlify-docs/kb/integrations/defect-dojo-integration.mdx b/mintlify-docs/kb/integrations/defect-dojo-integration.mdx
index 0d829b164..b46b6ee8b 100644
--- a/mintlify-docs/kb/integrations/defect-dojo-integration.mdx
+++ b/mintlify-docs/kb/integrations/defect-dojo-integration.mdx
@@ -35,7 +35,7 @@ The DefectDojo API uses the `/api/v2/import-scan/` endpoint for the first import
 These endpoints take the following parameters:
 
 - `file`: The Semgrep scan findings report or export in JSON format.
-- `scan_type`: A descriptive name for the scan type. In this example, the scan type is "Semgrep JSON Report`".
+- `scan_type`: A descriptive name for the scan type. In this example, the scan type is "Semgrep JSON Report".
 - `product_name`: The name of the product in DefectDojo to send the Semgrep findings report to.
 - `engagement_name`: The name of the engagement you created the preceding "Integration" section. In this example, `semgrep`.
 
diff --git a/mintlify-docs/kb/semgrep-appsec-platform/semgrep-login-cli-tenant.mdx b/mintlify-docs/kb/semgrep-appsec-platform/semgrep-login-cli-tenant.mdx
index 8422e04f5..2d839112c 100644
--- a/mintlify-docs/kb/semgrep-appsec-platform/semgrep-login-cli-tenant.mdx
+++ b/mintlify-docs/kb/semgrep-appsec-platform/semgrep-login-cli-tenant.mdx
@@ -1,5 +1,5 @@
 ---
-title: The semgrep login command doesn't redirect to my Semgrep tenant site"
+title: The semgrep login command doesn't redirect to my Semgrep tenant site
 ---
 
 When executing the command: 
diff --git a/mintlify-docs/learn/vulnerabilities/open-redirect.mdx b/mintlify-docs/learn/vulnerabilities/open-redirect.mdx
index 7c692af27..26d8425ed 100644
--- a/mintlify-docs/learn/vulnerabilities/open-redirect.mdx
+++ b/mintlify-docs/learn/vulnerabilities/open-redirect.mdx
@@ -63,7 +63,7 @@ In this fictional example, we notice an open redirect in the `redirect_view` . A
 
 ### Chaining with SSRF
 
-Even if an application tries to restrict which hosts it can fetch from, an open redirect can bypass those defenses. Suppose `semgrep.dev` has an image loader that only allows fetching from `*.semgrep.dev` , the implementation might look something like the Python code snippet below.
+Even if an application tries to restrict which hosts it can fetch from, an open redirect can bypass those defenses. Suppose `semgrep.dev` has an image loader that only allows fetching from `*.semgrep.dev`, the implementation might look something like the Python code snippet below.
 
 ```python
 import requests
diff --git a/mintlify-docs/snippets/semgrep-supply-chain/ignoring-dependencies.mdx b/mintlify-docs/snippets/semgrep-supply-chain/ignoring-dependencies.mdx
index 83e0c6ba8..ec6ed4113 100644
--- a/mintlify-docs/snippets/semgrep-supply-chain/ignoring-dependencies.mdx
+++ b/mintlify-docs/snippets/semgrep-supply-chain/ignoring-dependencies.mdx
@@ -26,4 +26,4 @@ If you add `package-lock.json` to the `.semgrepignore` file, Semgrep will not sc
 ```
 # .semgrepignore
 package-lock.json
-````
+```