From 5fe81ba2f94dc8929cce34ae03e4ab03eede0f63 Mon Sep 17 00:00:00 2001 From: "@mrubens" <2600+mrubens@users.noreply.github.com> Date: Fri, 2 Oct 2026 03:09:51 +0000 Subject: [PATCH] docs: correct copy typos --- apps/api/src/handlers/telegram/webhook-gate.ts | 2 +- .../references/javascript-express-web-server-security.md | 2 +- .../references/javascript-jquery-web-frontend-security.md | 2 +- .../references/python-flask-web-server-security.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/apps/api/src/handlers/telegram/webhook-gate.ts b/apps/api/src/handlers/telegram/webhook-gate.ts index 3913405431..b4ff115967 100644 --- a/apps/api/src/handlers/telegram/webhook-gate.ts +++ b/apps/api/src/handlers/telegram/webhook-gate.ts @@ -107,7 +107,7 @@ const TELEGRAM_LINK_NUDGE_CHAT_TTL_SECONDS = 15 * 60; * Rate-limits the group "link your account" nudge so it cannot be used to * make the bot spam: at most one nudge per sender per chat every 6 hours, * and at most one nudge per chat every 15 minutes regardless of sender. - * Fails quiet — if Redis is unavailable, no nudge is sent. + * Fails quietly — if Redis is unavailable, no nudge is sent. */ export async function claimTelegramLinkNudge(input: { chatId: string; diff --git a/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-express-web-server-security.md b/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-express-web-server-security.md index f52e8335db..b3a5c76914 100644 --- a/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-express-web-server-security.md +++ b/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-express-web-server-security.md @@ -918,7 +918,7 @@ Severity: Medium / Low NOTE: `npm audit` often returns a large number of insignificant "vulnerabilities" which do not actually matter. You should only focus on Express or other extremely critical packages, ignoring ones listed in dev tools, bundlers, etc. -Do not upgrade packages without concent from the user. This may break existing code in unexpected ways. Instead, inform them of the outdated packages. +Do not upgrade packages without consent from the user. This may break existing code in unexpected ways. Instead, inform them of the outdated packages. Required: diff --git a/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-jquery-web-frontend-security.md b/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-jquery-web-frontend-security.md index 3fd00db430..19d9e242e2 100644 --- a/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-jquery-web-frontend-security.md +++ b/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/javascript-jquery-web-frontend-security.md @@ -156,7 +156,7 @@ Each rule contains: required practice, insecure patterns, detection hints, and r Severity: Medium (High if internet-facing app AND version is known-vulnerable) -NOTE: Before performing an upgrade, get concent from the user and try to understand if they have reasons to keep it back. Upgrading can break applications in unexpected ways. Report and recommend upgrades rather than just performing them. +NOTE: Before performing an upgrade, get consent from the user and try to understand if they have reasons to keep it back. Upgrading can break applications in unexpected ways. Report and recommend upgrades rather than just performing them. Required: diff --git a/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/python-flask-web-server-security.md b/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/python-flask-web-server-security.md index adbc599aad..625c78dd72 100644 --- a/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/python-flask-web-server-security.md +++ b/packages/cloud-agents/src/server/workflows/skills/standard/security-best-practices/references/python-flask-web-server-security.md @@ -300,7 +300,7 @@ Severity: Critical Required: - MUST NOT render templates that contain user-controlled template syntax. - MUST treat `render_template_string` and `Environment.from_string(...).render(...)` as dangerous if the template string is influenced by untrusted input. -- MUST NOT use use `.format()` on user controlled strings +- MUST NOT use `.format()` on user controlled strings - If untrusted templates are absolutely required, treat it as a special high-risk design: - MUST use a sandboxed templating approach and restrict capabilities. - MUST keep Jinja updated and assume sandbox escapes are possible; isolate further. @@ -702,4 +702,4 @@ Template safety references: - PortSwigger Web Security Academy: Server-side template injection — https://portswigger.net/web-security/server-side-template-injection HTTP semantics: -- RFC 9110: HTTP Semantics (safe methods) — https://www.rfc-editor.org/rfc/rfc9110 \ No newline at end of file +- RFC 9110: HTTP Semantics (safe methods) — https://www.rfc-editor.org/rfc/rfc9110