Skip to content

chore: translate documentation#126

Closed
kilbot wants to merge 3 commits into
mainfrom
translations-2026-03-04
Closed

chore: translate documentation#126
kilbot wants to merge 3 commits into
mainfrom
translations-2026-03-04

Conversation

@kilbot
Copy link
Copy Markdown
Contributor

@kilbot kilbot commented Mar 4, 2026

Mode: changed
Languages: [es,fr,de,ja,pt-BR,ko,it,ar,hi-IN,zh-CN]

Summary by CodeRabbit

  • Documentation
    • Added comprehensive Phone Orders (MOTO) docs (setup, taking phone orders, troubleshooting) across all localized pages.
    • Standardized "Stripe Terminal" naming and refined simulator vs. real‑reader usage, installation, POS activation, and SSL guidance.
    • Updated hardware compatibility lists (supported terminals, internet‑only connectivity, Bluetooth notes), troubleshooting entries, help links, and screenshot captions in AR, DE, ES, FR, HI, IT, JA, KO, PT‑BR, ZH.

Mode: changed
Languages: [es,fr,de,ja,pt-BR,ko,it,ar,hi-IN,zh-CN]
@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 5, 2026 8:39am

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 4, 2026

📝 Walkthrough

Walkthrough

Updated localized Stripe Terminal docs across 10 locales: standardized product terminology to "Stripe Terminal", refined installation/usage UI copy, updated supported devices/connectivity, added MOTO (phone-order) feature with setup, workflow, and troubleshooting, plus locale-specific editorial fixes.

Changes

Cohort / File(s) Summary
Localized Stripe Terminal documentation
i18n/ar/.../stripe-terminal.mdx, i18n/de/.../stripe-terminal.mdx, i18n/es/.../stripe-terminal.mdx, i18n/fr/.../stripe-terminal.mdx, i18n/hi-IN/.../stripe-terminal.mdx, i18n/it/.../stripe-terminal.mdx, i18n/ja/.../stripe-terminal.mdx, i18n/ko/.../stripe-terminal.mdx, i18n/pt-BR/.../stripe-terminal.mdx, i18n/zh-CN/.../stripe-terminal.mdx
Standardized terminology to "Stripe Terminal"; rewrote installation/setup and WooCommerce/WCPOS navigation text; clarified device connectivity and updated supported terminal lists (S700/S710, WisePOS E); added Phone Orders (MOTO) feature (setup, usage, troubleshooting); expanded common issues and help links; locale grammar/style fixes.

Sequence Diagram(s)

sequenceDiagram
  participant Clerk as Clerk (POS operator)
  participant POS as WCPOS (POS)
  participant Reader as Stripe Terminal reader
  participant Stripe as Stripe API

  Clerk->>POS: Create order, choose "Phone order (MOTO)"
  POS->>Reader: Request card entry / start card_present flow
  Reader->>Clerk: Prompt to enter card on reader
  Clerk->>Reader: Enter card details on reader
  Reader->>Stripe: Tokenize card / create payment intent (card_present)
  Stripe-->>Reader: Return payment confirmation
  Reader-->>POS: Deliver token/confirmation
  POS-->>Clerk: Show payment success, complete order
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Poem

🐰 I hopped through docs in ten tongues bright,

MOTO whispers turn into payment light.
Readers hum, terminals align,
Stripe Terminal sing — every locale fine.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: translate documentation' is partially related to the changeset—it describes a real aspect of the changes (documentation translation), but is overly broad and doesn't specify which documentation or the scope of translation updates. Consider a more specific title that indicates the product being documented (e.g., 'chore: translate Stripe Terminal documentation across 10 languages') to provide clearer context.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch translations-2026-03-04

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 14

🧹 Nitpick comments (6)
i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

194-194: Standardize the MOTO label wording across sections.

This page mostly uses “फोन ऑर्डर (MOTO)”; line 194 uses plural “फोन ऑर्डर्स (MOTO)”. Consider keeping one form for consistency.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 194, The text uses two inconsistent labels for MOTO; change the plural
"फोन ऑर्डर्स (MOTO)" (the occurrence at the shown diff) to the singular form
"फोन ऑर्डर (MOTO)" to match the rest of the document (ensure the string
replacement targets the exact phrase "फोन ऑर्डर्स (MOTO)" so all instances are
standardized).
i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

121-121: Unify “internetverbunden” terminology/casing across sections.

Line [121] uses „internetverbundenen“, while Line [157] uses „Internet-Verbunden“. Consider one consistent form to reduce translation drift.

♻️ Suggested consistency tweak
-### Unterstützte Terminals (Internet-Verbunden) {`#supported-terminals-internet-connected`}
+### Unterstützte Terminals (internetverbunden) {`#supported-terminals-internet-connected`}

Also applies to: 157-160

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 121, The translation uses two different forms for the same term
(“internetverbundenen” at the MOTO sentence and “Internet-Verbunden” in the
other section); pick one consistent casing/compound form (e.g.,
"internetverbunden" or "Internet-verbunden") and replace all occurrences so they
match across the document, including the sentence currently reading "MOTO
funktioniert nur mit kompatiblen internetverbundenen Lesegeräten..." and the
section lines containing "Internet-Verbunden", ensuring the chosen form is
applied consistently in headings and body text.
i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

169-169: Evita la data hardcoded nella nota di supporto futuro.

A Line 169, Q1 2026 diventa rapidamente obsoleto. Conviene usare una formulazione senza data fissa; qui puoi anche correggere l'WisePad 3.

Proposta di fix
-Il supporto per i terminali Bluetooth sarà aggiunto alle applicazioni iOS e Android nel **Q1 2026**. Ciò abiliterà il supporto per tutti i lettori certificati Terminal Stripe, incluso il M2 e l'WisePad 3.
+Il supporto per i terminali Bluetooth sarà aggiunto alle applicazioni iOS e Android in una prossima release. Ciò abiliterà il supporto per tutti i lettori certificati Terminal Stripe, inclusi M2 e WisePad 3.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 169, Sostituisci la frase che contiene "Il supporto per i terminali
Bluetooth sarà aggiunto alle applicazioni iOS e Android nel Q1 2026" con una
formulazione senza data fissa (es. "sarà aggiunto prossimamente" o "sarà reso
disponibile in una futura versione") e correggi "l'WisePad 3" rimuovendo
l'articolo errato (usare "WisePad 3"); cerca la stringa che inizia con "Il
supporto per i terminali Bluetooth..." per individuare il punto da aggiornare.
i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

169-169: Replace hard-coded roadmap dates with neutral language or a centralized reference.

The hard-coded date Q1 2026 appears in the source English documentation and has been propagated to all 10 localized versions (11 files total). This creates a maintenance burden: any future updates require coordinating changes across all languages simultaneously, increasing the risk of drift or missed synchronization across locales.

Recommend using neutral wording (e.g., "a future release" or "early 2026") or implementing a mechanism to maintain this date centrally.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 169, The localized string contains a hard-coded roadmap date "Q1 2026"
in the sentence about Bluetooth terminal support; replace that hard-coded date
with neutral language (e.g., "a future release" or "early 2026") or point the
sentence to a centralized roadmap reference so updates are made once for all
locales; locate the string in the Stripe Terminal doc (the sentence mentioning
Bluetooth terminals and "Q1 2026") and update it to use neutral wording or a
link/variable that pulls the canonical date from a single source.
i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

169-169: Éviter une promesse datée (“Q1 2026”) dans la doc.

Sur Line 169, ce libellé va rapidement devenir obsolète. Préférer une formulation non datée ou un lien vers une roadmap/changelog.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 169, Remplacez la phrase datée "La prise en charge des terminaux
Bluetooth sera ajoutée aux applications iOS et Android dans **Q1 2026**." (la
ligne commençant par "La prise en charge des terminaux Bluetooth...") par une
formulation non datée ou pointant vers une source maintenue (ex. "La prise en
charge des terminaux Bluetooth sera ajoutée prochainement aux applications iOS
et Android" ou "Voir la roadmap/changelog pour le calendrier de prise en
charge") afin d'éviter une promesse datée qui deviendra rapidement obsolète.
i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

17-17: 日本語の冗長表現を短くできます。

Line 17 の「受け付けることができます」は「受け付けられます」にすると自然で簡潔です。

📝 提案差分(簡潔化)
-ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して対面で支払いを受け付けることができます。
+ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使って対面支払いを受け付けられます。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 17, The sentence contains a verbose Japanese phrase "受け付けることができます";
replace that phrase with the more concise "受け付けられます" in the line that currently
reads
"ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して対面で支払いを受け付けることができます。" so
it becomes concise and natural; ensure the rest of the sentence structure
remains unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 219: The translation uses "ميلادي GitHub" incorrectly; replace the phrase
in the markdown link text "زيارة [ميلادي
GitHub](https://github.com/wcpos/stripe-terminal-for-woocommerce) للإبلاغ عن
المشاكل" with a correct Arabic term such as "مستودع GitHub" (or "صفحة GitHub")
so the line reads "زيارة [مستودع
GitHub](https://github.com/wcpos/stripe-terminal-for-woocommerce) للإبلاغ عن
المشاكل", preserving the existing URL and surrounding text.
- Line 102: The Arabic translation uses the wrong word "النقض" in the sentence
starting "MOTO (طلب عبر البريد/طلب عبر الهاتف) ..." (and the other occurrence
later) — replace each "النقض" with the correct payment terms for tap/swipe, e.g.
"النقر أو التمرير" (or "اللمس أو التمرير") so the phrase reads that the merchant
enters card details instead of tapping/swiping the card.

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 130: The instruction text "zur Eingabe des Tippens/Einfügens" is
ambiguous; update the sentence in the Stripe Terminal phone-order flow that
currently reads "Klicken Sie auf **Kartenzahlung annehmen** — der Leser zeigt
einen Bildschirm zur Eingabe der Kartennummer an, anstatt zur Eingabe des
Tippens/Einfügens aufzufordern" by replacing the phrase "zur Eingabe des
Tippens/Einfügens" with a clear alternative such as "um Kartendaten per Tippen
oder Einfügen einzugeben" (or "für die Eingabe per Tippen oder Einfügen") so the
intent is unambiguous; locate the exact string containing "zur Eingabe des
Tippens/Einfügens" in the document and update it accordingly.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 50: The StepCard title "Configurar Configuraciones de Stripe" is
redundant; update the StepCard component (StepCard number="2" title="Configurar
Configuraciones de Stripe") to a concise, non-redundant Spanish phrase such as
"Configurar Stripe" or "Configuración de Stripe" by replacing the title prop
value accordingly.

In
`@i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 102: Replace the ambiguous phrase "Commande par Mail" in the MOTO
definition text ("MOTO (Commande par Mail/Commande par Téléphone) ...") with
"Commande par correspondance" so the meaning of mail (correspondence/postal
orders) is clear; update that exact string in the paragraph and review other
occurrences of "Commande par Mail" in the document to keep terminology
consistent.
- Line 121: Replace the incorrect French translation phrase "Terminaux
Pratiques" with "Terminaux pris en charge" wherever it appears (e.g., the string
"Terminaux Pratiques" referenced at Lines 121, 128, 157, and 195 in the
stripe-terminal.mdx content); update each occurrence so links and references
(the anchor text and any in-page links like "[Terminaux
Pratiques](`#supported-terminals-internet-connected`)") use "Terminaux pris en
charge" to accurately reflect the original "supported" wording.
- Around line 162-166: Update the Verifone P400 entry under "Terminaux Non
Supportés (Bluetooth)" — locate the "Verifone P400" list item and either remove
it or change the text to indicate it is a deprecated reader no longer supported
by Stripe rather than "uniquement Bluetooth"; if you keep it, mention that the
P400 supports both Bluetooth (BLE 4.2) and Ethernet (10/100 Base-T) but is
deprecated/unsupported by Stripe Terminal so it should not be listed as
Bluetooth-only.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 177-179: The troubleshooting line contains a mixed-language typo
"k conectado"; update the string in the Stripe Terminal doc (the line reading
"सुनिश्चित करें कि टर्मिनल WiFi/Ethernet से k conectado है और ऑनलाइन है") to use
the correct Hindi term — e.g., replace "k conectado" with "कनेक्टेड" so the line
becomes "सुनिश्चित करें कि टर्मिनल WiFi/Ethernet से कनेक्टेड है और ऑनलाइन है".
- Line 202: The markdown link "[स्ट्राइप
समर्थन](https://support.stripe.com/contact)" is missing a space before the
following Hindi word "से", causing the text to render without proper spacing;
update the text in stripe-terminal.mdx (specifically the sentence containing the
link) to insert a single space between the closing parenthesis of the link and
"से" so it reads "...[स्ट्राइप समर्थन](https://support.stripe.com/contact) से
संपर्क करें".
- Line 59: Fix the Hindi grammar in the sentence "आपको वूकॉमर्स सेटिंग्स में
स्ट्राइप टर्मिनल गेटवे सक्रिय करने की आवश्यकता नहीं है। यह अगली चरण में POS के
लिए विशेष रूप से सक्रिय किया जाएगा।" by changing "अगली चरण" to "अगले चरण" so the
phrase reads "यह अगले चरण में POS के लिए विशेष रूप से सक्रिय किया जाएगा।" Update
this exact sentence in the stripe-terminal.mdx content to correct the
gender/case agreement.

In
`@i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 65: Aggiorna il percorso admin nel testo che attualmente recita "WP Admin
> POS > Impostazioni > Pagamento" cambiando "Pagamento" in "Pagamenti" per
allinearlo al resto della guida e a WooCommerce; cerca la stringa esatta "WP
Admin > POS > Impostazioni > Pagamento" nel file
(version-1.x/payment/custom-gateways/stripe-terminal.mdx) e sostituiscila con
"WP Admin > POS > Impostazioni > Pagamenti", verificando eventuali occorrenze
duplicate nello stesso documento.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: Replace the hardcoded bold date "**2026年第1四半期**" with flexible
language stating that Bluetooth terminal support is planned but timelines may
change, e.g. "Bluetoothターミナルのサポートは今後のリリースで追加される予定で、タイムラインは変更されることがあります。" Keep
the note that M2やWisePad 3などの認定リーダーが対象で, and add a one-line pointer telling
readers to check the official WCPOS release notes or Stripe documentation for
the latest status (e.g., "最新情報は公式WCPOSリリースノートまたはStripeのドキュメントを参照してください"). Ensure
you remove the specific date token "**2026年第1四半期**" and preserve the existing
Japanese wording and emphasis.

In
`@i18n/ko/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: Replace the hard-coded future-tense, date-bound sentence "2026년
1분기에는 iOS 및 Android 응용 프로그램에 블루투스 터미널 지원이 추가될 것입니다." with a neutral,
non-date-specific phrasing (for example "iOS 및 Android 응용 프로그램에 블루투스 터미널 지원이
계획되어 있습니다" or similar) or add a link to a living roadmap/changelog; edit the
same string in the stripe-terminal.mdx content so the statement remains accurate
over time without a fixed quarter.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 96: The bullet title "非接触式付款" and its description "模拟刷卡支付交易" are
inconsistent; update the description to match the title by replacing "模拟刷卡支付交易"
with "模拟感应式支付交易" so the phrase under the bullet aligns with the concept used in
the title ("非接触式付款") — look for the exact strings "非接触式付款" and "模拟刷卡支付交易" in the
stripe-terminal.mdx content and change the latter to "模拟感应式支付交易".

---

Nitpick comments:
In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 121: The translation uses two different forms for the same term
(“internetverbundenen” at the MOTO sentence and “Internet-Verbunden” in the
other section); pick one consistent casing/compound form (e.g.,
"internetverbunden" or "Internet-verbunden") and replace all occurrences so they
match across the document, including the sentence currently reading "MOTO
funktioniert nur mit kompatiblen internetverbundenen Lesegeräten..." and the
section lines containing "Internet-Verbunden", ensuring the chosen form is
applied consistently in headings and body text.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: The localized string contains a hard-coded roadmap date "Q1 2026" in
the sentence about Bluetooth terminal support; replace that hard-coded date with
neutral language (e.g., "a future release" or "early 2026") or point the
sentence to a centralized roadmap reference so updates are made once for all
locales; locate the string in the Stripe Terminal doc (the sentence mentioning
Bluetooth terminals and "Q1 2026") and update it to use neutral wording or a
link/variable that pulls the canonical date from a single source.

In
`@i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: Remplacez la phrase datée "La prise en charge des terminaux
Bluetooth sera ajoutée aux applications iOS et Android dans **Q1 2026**." (la
ligne commençant par "La prise en charge des terminaux Bluetooth...") par une
formulation non datée ou pointant vers une source maintenue (ex. "La prise en
charge des terminaux Bluetooth sera ajoutée prochainement aux applications iOS
et Android" ou "Voir la roadmap/changelog pour le calendrier de prise en
charge") afin d'éviter une promesse datée qui deviendra rapidement obsolète.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 194: The text uses two inconsistent labels for MOTO; change the plural
"फोन ऑर्डर्स (MOTO)" (the occurrence at the shown diff) to the singular form
"फोन ऑर्डर (MOTO)" to match the rest of the document (ensure the string
replacement targets the exact phrase "फोन ऑर्डर्स (MOTO)" so all instances are
standardized).

In
`@i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: Sostituisci la frase che contiene "Il supporto per i terminali
Bluetooth sarà aggiunto alle applicazioni iOS e Android nel Q1 2026" con una
formulazione senza data fissa (es. "sarà aggiunto prossimamente" o "sarà reso
disponibile in una futura versione") e correggi "l'WisePad 3" rimuovendo
l'articolo errato (usare "WisePad 3"); cerca la stringa che inizia con "Il
supporto per i terminali Bluetooth..." per individuare il punto da aggiornare.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 17: The sentence contains a verbose Japanese phrase "受け付けることができます";
replace that phrase with the more concise "受け付けられます" in the line that currently
reads
"ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して対面で支払いを受け付けることができます。" so
it becomes concise and natural; ensure the rest of the sentence structure
remains unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3ae4b9bc-f184-4c63-8642-9eeb75604507

📥 Commits

Reviewing files that changed from the base of the PR and between 38feb4d and 1ecefcb.

📒 Files selected for processing (10)
  • i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/ko/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx

@wcpos-bot
Copy link
Copy Markdown
Contributor

wcpos-bot Bot commented Mar 4, 2026

⚠️ Ada needs manual follow-up on this PR.

  • Reason: unresolved_review_threads
  • Details: Ada reported 14 unresolved review thread(s) after run verification.
  • Escalation routed to #agent-ops via model-gateway event pipeline.

Posted automatically by model-gateway.

- ar: fix "النقض" -> "النقر" (tap/swipe), "ميلادي GitHub" -> "مستودع GitHub"
- de: clarify tap/insert wording in phone order instructions
- es: fix redundant "Configurar Configuraciones" -> "Configuración de Stripe"
- fr: "Commande par Mail" -> "Commande par correspondance", "Terminaux Pratiques" -> "Terminaux pris en charge", fix Verifone P400 description
- hi: fix gender agreement "अगली" -> "अगले", fix "k conectado" -> "कनेक्टेड", add missing space before "से"
- it: "Pagamento" -> "Pagamenti" for consistency
- ja: remove hardcoded "2026年第1四半期" date, use flexible wording
- ko: remove hardcoded "2026년 1분기" date, use flexible wording
- zh-CN: fix "模拟刷卡支付交易" -> "模拟感应式支付交易" to match contactless title
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 14

🧹 Nitpick comments (8)
i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

102-102: Ajusta la expansión de MOTO para una frase más natural en español.

En Line 102, “Pedido por Correo/Pedido Telefónico” suena poco idiomático. Una forma más clara: “Pedido por correo o por teléfono”.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 102, Replace the current expansion "MOTO (Pedido por Correo/Pedido
Telefónico)" with a more natural Spanish phrasing such as "MOTO (Pedido por
correo o por teléfono)" — locate the exact string "MOTO (Pedido por
Correo/Pedido Telefónico)" in the file and update it to "MOTO (Pedido por correo
o por teléfono)" to improve idiomatic flow.
i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

169-169: Evita una data hardcoded che invecchia rapidamente.

In Line 169 “Q1 2026” diventa presto obsoleto e richiede manutenzione frequente. Conviene usare wording non vincolato a una finestra temporale fissa.

Proposta di wording stabile
-Il supporto per i terminali Bluetooth sarà aggiunto alle applicazioni iOS e Android nel **Q1 2026**. Ciò abiliterà il supporto per tutti i lettori certificati Terminal Stripe, incluso il M2 e l'WisePad 3.
+Il supporto per i terminali Bluetooth sarà aggiunto alle applicazioni iOS e Android in un aggiornamento futuro. Ciò abiliterà il supporto per tutti i lettori certificati Stripe Terminal, inclusi M2 e WisePad 3.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 169, The sentence containing the hardcoded timeline "Q1 2026" (the line
that begins "Il supporto per i terminali Bluetooth...") should be rewritten to
avoid a fixed date; replace "Q1 2026" with a neutral, long-lived phrase such as
"in un prossimo aggiornamento", "nelle prossime versioni" or "a breve" (e.g.,
"Il supporto... sarà aggiunto in un prossimo aggiornamento"), keeping the rest
of the sentence about enabling support for all Stripe Terminal readers (M2 and
WisePad 3) intact.
i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (2)

169-169: Avoid hardcoded quarter in the roadmap note.

“Q1 2026” will go stale quickly (and is already time-sensitive). Prefer a relative status statement or link to a changelog/release note.

✏️ Suggested wording
-Die Unterstützung für Bluetooth-Terminals wird in **Q1 2026** zu den iOS- und Android-Anwendungen hinzugefügt.
+Die Unterstützung für Bluetooth-Terminals wird in einem zukünftigen Update für die iOS- und Android-Anwendungen hinzugefügt.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 169, Replace the hardcoded timetable string "Die Unterstützung für
Bluetooth-Terminals wird in **Q1 2026** zu den iOS- und Android-Anwendungen
hinzugefügt." with a relative status or pointer to a changelog; for example,
change it to a phrase like "Die Unterstützung für Bluetooth-Terminals wird in
Kürze zu den iOS- und Android-Anwendungen hinzugefügt" or "Die Unterstützung für
Bluetooth-Terminals wird bald bereitgestellt; siehe unseren
Changelog/Release-Notes für Details" and include a link to the project changelog
or release notes if available so the statement stays accurate without a fixed
quarter.

45-45: Polish compound noun formatting in download step.

Line 45 reads more naturally as “ZIP-Datei”.

✏️ Suggested wording
-2. Laden Sie die neueste **stripe-terminal-for-woocommerce.zip** Datei herunter
+2. Laden Sie die neueste **stripe-terminal-for-woocommerce.zip**-Datei herunter
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 45, The compound noun in the download step
("stripe-terminal-for-woocommerce.zip Datei") should be corrected to use the
German compound noun form; update the sentence containing
"stripe-terminal-for-woocommerce.zip" so it reads for example: "Laden Sie die
neueste ZIP-Datei 'stripe-terminal-for-woocommerce.zip' herunter" (replace the
current phrase with "ZIP-Datei 'stripe-terminal-for-woocommerce.zip'").
i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (2)

225-228: Replace “future update” placeholder text in published docs.

该段当前是占位文案;若页面对外发布,建议补齐截图或移除该节以避免空承诺。

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 225 - 228, 当前段落“截图将在未来更新中添加,以显示:- WooCommerce 付款设置中的网关配置 - 带有
Stripe 终端选择的 POS 结账界面 - 使用各种付款方式的模拟器测试界面”是占位文案;在发布前请在 stripe-terminal.mdx
中用实际截图替换该占位文本(包括三张示例截图并添加简短描述),或直接删除该节以避免空承诺;如果确实需要保留占位,可改为明确的
TODO/计划说明并给出预计完成时间或外部资源链接以避免模糊承诺。

169-169: Avoid hardcoded quarter wording that will age out quickly.

“2026 年第一季度”在 2026-03-31 之后会立即过期,建议改为非日期绑定表达以减少文档维护成本。

♻️ Suggested wording
-蓝牙终端的支持将在 **2026 年第一季度** 加入 iOS 和 Android 应用程序。这将支持所有经过 Stripe 终端认证的读取器,包括 M2 和 WisePad 3。
+蓝牙终端支持将随 iOS 和 Android 应用程序后续版本提供。这将支持所有经过 Stripe 终端认证的读取器,包括 M2 和 WisePad 3。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 169, Replace the hardcoded date phrase in the sentence "蓝牙终端的支持将在 **2026
年第一季度** 加入 iOS 和 Android 应用程序。" with a non-time-bound wording (e.g., "即将" or
"将在近期") to avoid expiration; update the line in stripe-terminal.mdx where that
sentence appears (look for the exact Chinese sentence) so it conveys the same
availability information without mentioning a specific quarter or year.
i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (2)

2-3: Unify product naming style across the page.

The document mixes 「ストライプターミナル」 and “Stripe Terminal”. Consider choosing one style for consistency in headings/body text.

Also applies to: 15-17, 169-169

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 2 - 3, The page mixes the Japanese localized name "ストライプターミナル" and
the English "Stripe Terminal"; pick one naming style and make it consistent
throughout by replacing all occurrences of the other form (including the
frontmatter title/description and body headings/text). Specifically, update the
title/description lines that currently contain "ストライプターミナル" / "Stripe Terminal",
and normalize all instances referenced in the comment (around lines 15-17 and
169) so the page uses the chosen term uniformly. Ensure you update both plain
text and any headings or inline occurrences.

17-17: Consider tightening a slightly verbose phrase.

Line 17’s 「受け付けることができます」 can be shortened for cleaner Japanese (e.g., 「受け付けられます」).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 17, Replace the slightly verbose phrase "受け付けることができます" in the sentence
that describes Stripe Terminal support with the more concise "受け付けられます" to
tighten the wording; locate the sentence starting with
"ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して..." and update that
fragment accordingly to maintain natural Japanese flow.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: The sentence stating "سيتم إضافة دعم أجهزة البلوتوث إلى تطبيقات iOS
و Android في **الربع الأول من 2026**." is now outdated; update the copy in the
Stripe Terminal doc (the Arabic string in
payment/custom-gateways/stripe-terminal.mdx that begins with "سيتم إضافة دعم
أجهزة البلوتوث...") to reflect current status: either change the timeline to the
corrected ETA (e.g., "الربع الثاني من 2026" or the new quarter) or replace the
phrase with a release statement if the feature is live (e.g., "تم إضافة دعم
أجهزة البلوتوث...") and ensure the sentence still mentions supported readers (M2
و WisePad 3).
- Line 166: Update the Verifone P400 connectivity label: replace the string
"**Verifone P400** ❌ - بلوتوث فقط" with a description that reflects P400's LAN
connectivity (Ethernet and Wi‑Fi) and not "Bluetooth only" — e.g., "**Verifone
P400** ❌ - Ethernet / Wi‑Fi (LAN), not Bluetooth" — and optionally add a short
note that the P400 is no longer available for purchase; ensure you update only
the displayed text in the stripe-terminal.mdx content.

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 166: Update the "Verifone P400" entry (the bullet currently reading "Nur
Bluetooth") to reflect the correct connection methods: replace "Nur Bluetooth"
with "Ethernet (wired) or Wi‑Fi"; optionally append a clarifying note that
Bluetooth is not supported on the standard P400 (only P400 Plus supports
Bluetooth 4.2 BLE) so readers understand the distinction.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 2-3: Unifica el nombre del producto en todo el documento
reemplazando todas las ocurrencias de “Terminal Stripe” y “Terminal de Stripe”
por la forma consistente “Stripe Terminal”; revisa y corrige el valor del
frontmatter title ("Pasarela de Terminal Stripe") y los textos en las secciones
donde aparecen (líneas mencionadas en el comentario: título y cuerpos que
contienen “Terminal Stripe” / “Terminal de Stripe”) para usar “Stripe Terminal”
de manera consistente y mantener la gramática española en el resto de la frase.
- Line 169: Replace the hard-coded deadline "Q1 2026" in the sentence that
currently reads “El soporte para terminales Bluetooth se añadirá a las
aplicaciones iOS y Android en **Q1 2026**.” with a non-time-specific phrasing
(e.g., “próximamente”, “en una futura actualización” or “en próximos
trimestres”) so the text remains accurate over time; update the surrounding
sentence to something like “El soporte para terminales Bluetooth se añadirá
próximamente a las aplicaciones iOS y Android” and ensure the bold emphasis is
applied to the chosen non-dated phrase instead of the fixed quarter.

In
`@i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 96: Replace the instances of "paiement tactile" and any use of "tap" with
the standardized French term "paiement sans contact" (or simply "sans contact")
to ensure consistent, natural terminology; update the phrase "**Paiements Sans
Contact** : Simulez des transactions par paiement tactile" and the other
occurrence to use "**Paiements sans contact** : Simulez des transactions par
paiement sans contact" (or equivalent consistent wording) so both headings and
descriptive text match the standardized term.
- Line 169: Update the Bluetooth terminal support paragraph to present tense and
current status: replace the Q1 2026 future statement with a live-support
statement indicating that Stripe Terminal Bluetooth readers are now supported on
both iOS and Android; specifically, remove WisePad 3 from the unsupported
terminals list and state that WisePad 3 is actively supported in non‑US markets,
M2 is supported in the US, and Chipper 2X BT is deprecated. Locate the Bluetooth
support sentence and the unsupported terminals list (references: the Bluetooth
Terminal support paragraph and entries for WisePad 3, Chipper 2X BT, and M2) and
edit the text accordingly so the section reflects current availability rather
than a future feature.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: The user-facing doc currently hardcodes "Q1 2026" in the sentence
starting with "ब्लूटूथ टर्मिनल समर्थन ...", which risks becoming stale; update
that sentence in stripe-terminal.mdx to use timeline-safe wording (e.g., "coming
in an upcoming release" or "planned for 2026") instead of a specific quarter,
and keep the note that it will support all certified readers including M2 and
WisePad 3 so the rest of the sentence ("यह M2 और वाइजपैड 3 सहित...") remains
unchanged.
- Line 210: Update the Hindi sentence "स्ट्राइप टर्मिनल HTTPS की आवश्यकता है -
सुनिश्चित करें कि आपकी साइट में एक मान्य SSL सर्टिफिकेट है" by inserting the
missing postposition "को" after "स्ट्राइप टर्मिनल" and adjusting the second
clause for natural phrasing; e.g., change it to "स्ट्राइप टर्मिनल को HTTPS की
आवश्यकता है - सुनिश्चित करें कि आपकी साइट के पास एक मान्य SSL सर्टिफिकेट है" so
the fragment "स्ट्राइप टर्मिनल HTTPS की आवश्यकता है" becomes grammatically
correct.

In
`@i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 2-3: Uniforma il naming del prodotto sostituendo tutte le
occorrenze di "Terminal Stripe" con il brand ufficiale "Stripe Terminal" (es.
aggiorna il campo title e description e le menzioni a Line 2, Line 15, Line 17)
salvo quando una specifica stringa "Terminal Stripe" è una label UI esatta che
deve restare così; cerca e sostituisci le occorrenze nel documento (ad es.
quelle alle Linee 53/54/66) mantenendo coerenza e lasciando invariate solo le
label UI verificate.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 164-167: The entry for "Verifone P400" in the Stripe Terminal
device list is incorrect and outdated; locate the "Verifone P400" line in the
payment/custom-gateways/stripe-terminal.mdx content (the device list near the
BBPOS lines) and either remove the Verifone P400 bullet entirely or replace it
with a deprecated entry that states it's no longer supported by Stripe (as of
2026) and correct the connection type to "Internet (Ethernet/Wi‑Fi)" rather than
"Bluetoothのみ"; ensure the updated text follows the same list formatting and
localization style as the surrounding entries (e.g., use Japanese phrasing and
the same emoji/status markers).

In
`@i18n/ko/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 145: The RequirementItem text duplicates "활성" — update the
<RequirementItem label="스트라이프 계정"> node to remove the redundancy so it reads
e.g. "터미널이 활성화된 스트라이프 계정" (or alternatively "활성화된 스트라이프 계정"), keeping only one
instance of "활성(화된)" to make the sentence concise.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 23-27: Fix the duplicated and awkward Chinese wording inside the
FeatureCard nodes: in the FeatureCard with title "通过互联网连接连接物理 Stripe 终端读取器"
remove the duplicated "连接" so it reads like "通过互联网连接物理 Stripe 终端读取器", and in the
FeatureCard with title "模拟器模式" rephrase the body from "使用 Stripe 的模拟器无硬件测试付款" to
a natural Chinese sentence such as "使用 Stripe 模拟器在无硬件情况下测试付款" (or an equivalent
concise, fluent phrasing).
- Around line 34-36: Update the FeatureCard (icon="phone", title="电话订单 (MOTO)")
text to a more natural Chinese phrasing by replacing "通过将详细信息输入读取器来接受电话中的卡付款"
with "通过在读取器上输入卡片详细信息来接受电话订单中的卡付款" so the sentence reads clearly and accurately
describes MOTO.

---

Nitpick comments:
In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: Replace the hardcoded timetable string "Die Unterstützung für
Bluetooth-Terminals wird in **Q1 2026** zu den iOS- und Android-Anwendungen
hinzugefügt." with a relative status or pointer to a changelog; for example,
change it to a phrase like "Die Unterstützung für Bluetooth-Terminals wird in
Kürze zu den iOS- und Android-Anwendungen hinzugefügt" or "Die Unterstützung für
Bluetooth-Terminals wird bald bereitgestellt; siehe unseren
Changelog/Release-Notes für Details" and include a link to the project changelog
or release notes if available so the statement stays accurate without a fixed
quarter.
- Line 45: The compound noun in the download step
("stripe-terminal-for-woocommerce.zip Datei") should be corrected to use the
German compound noun form; update the sentence containing
"stripe-terminal-for-woocommerce.zip" so it reads for example: "Laden Sie die
neueste ZIP-Datei 'stripe-terminal-for-woocommerce.zip' herunter" (replace the
current phrase with "ZIP-Datei 'stripe-terminal-for-woocommerce.zip'").

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 102: Replace the current expansion "MOTO (Pedido por Correo/Pedido
Telefónico)" with a more natural Spanish phrasing such as "MOTO (Pedido por
correo o por teléfono)" — locate the exact string "MOTO (Pedido por
Correo/Pedido Telefónico)" in the file and update it to "MOTO (Pedido por correo
o por teléfono)" to improve idiomatic flow.

In
`@i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 169: The sentence containing the hardcoded timeline "Q1 2026" (the line
that begins "Il supporto per i terminali Bluetooth...") should be rewritten to
avoid a fixed date; replace "Q1 2026" with a neutral, long-lived phrase such as
"in un prossimo aggiornamento", "nelle prossime versioni" or "a breve" (e.g.,
"Il supporto... sarà aggiunto in un prossimo aggiornamento"), keeping the rest
of the sentence about enabling support for all Stripe Terminal readers (M2 and
WisePad 3) intact.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 2-3: The page mixes the Japanese localized name "ストライプターミナル" and
the English "Stripe Terminal"; pick one naming style and make it consistent
throughout by replacing all occurrences of the other form (including the
frontmatter title/description and body headings/text). Specifically, update the
title/description lines that currently contain "ストライプターミナル" / "Stripe Terminal",
and normalize all instances referenced in the comment (around lines 15-17 and
169) so the page uses the chosen term uniformly. Ensure you update both plain
text and any headings or inline occurrences.
- Line 17: Replace the slightly verbose phrase "受け付けることができます" in the sentence
that describes Stripe Terminal support with the more concise "受け付けられます" to
tighten the wording; locate the sentence starting with
"ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して..." and update that
fragment accordingly to maintain natural Japanese flow.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 225-228: 当前段落“截图将在未来更新中添加,以显示:- WooCommerce 付款设置中的网关配置 - 带有 Stripe
终端选择的 POS 结账界面 - 使用各种付款方式的模拟器测试界面”是占位文案;在发布前请在 stripe-terminal.mdx
中用实际截图替换该占位文本(包括三张示例截图并添加简短描述),或直接删除该节以避免空承诺;如果确实需要保留占位,可改为明确的
TODO/计划说明并给出预计完成时间或外部资源链接以避免模糊承诺。
- Line 169: Replace the hardcoded date phrase in the sentence "蓝牙终端的支持将在 **2026
年第一季度** 加入 iOS 和 Android 应用程序。" with a non-time-bound wording (e.g., "即将" or
"将在近期") to avoid expiration; update the line in stripe-terminal.mdx where that
sentence appears (look for the exact Chinese sentence) so it conveys the same
availability information without mentioning a specific quarter or year.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 423c4797-8b75-4e11-b9ed-6fdc809c9a66

📥 Commits

Reviewing files that changed from the base of the PR and between 1ecefcb and cafe300.

📒 Files selected for processing (9)
  • i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/ko/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx

@wcpos-bot
Copy link
Copy Markdown
Contributor

wcpos-bot Bot commented Mar 5, 2026

Fix Summary — Round 1

# Source File Category Outcome
1 CodeRabbit ar/stripe-terminal.mdx:166 Important Fixed: corrected P400 label to "deprecated, no longer supported by Stripe"
2 CodeRabbit ar/stripe-terminal.mdx:169 Minor Fixed: replaced Q1 2026 with timeline-safe wording
3 CodeRabbit de/stripe-terminal.mdx:166 Important Fixed: corrected P400 label
4 CodeRabbit es/stripe-terminal.mdx:3 Minor Fixed: unified product name to "Stripe Terminal" throughout
5 CodeRabbit es/stripe-terminal.mdx:169 Minor Fixed: replaced Q1 2026 with timeline-safe wording
6 CodeRabbit fr/stripe-terminal.mdx:96 Minor Fixed: standardized to "sans contact" terminology
7 CodeRabbit fr/stripe-terminal.mdx:169 Important Fixed: softened Q1 2026 date (P400 label was already corrected in prior commit)
8 CodeRabbit hi-IN/stripe-terminal.mdx:169 Minor Fixed: replaced Q1 2026 with timeline-safe wording
9 CodeRabbit hi-IN/stripe-terminal.mdx:210 Minor Fixed: added missing postposition
10 CodeRabbit it/stripe-terminal.mdx:3 Minor Fixed: unified product name to "Stripe Terminal" throughout
11 CodeRabbit ja/stripe-terminal.mdx:167 Important Fixed: corrected P400 label to deprecated (Q1 2026 was already fixed in prior commit)
12 CodeRabbit ko/stripe-terminal.mdx:145 Minor Fixed: removed redundant wording
13 CodeRabbit zh-CN/stripe-terminal.mdx:27 Minor Fixed: removed duplicated wording + improved phrasing
14 CodeRabbit zh-CN/stripe-terminal.mdx:36 Minor Fixed: improved MOTO description phrasing

Blast-radius fixes applied: P400 label and Q1 2026 date also fixed in pt-BR (not flagged by reviewer but same issue). All 10 translation files updated for consistency.

Blast-radius follow-up: English source file (versioned_docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx) has same P400/Q1 2026 issues — requires separate PR. Also sumup-terminal.mdx translations have stale Q1 2026 references.

Commit: 36ab7dd
Fixed: 14 | Declined: 0 | Deferred: 0

- ar/de/es/fr/hi-IN/it/ja/ko/pt-BR/zh-CN: correct Verifone P400 label
  from "Bluetooth only" to "deprecated, no longer supported by Stripe"
- ar/de/es/fr/hi-IN/it/pt-BR/zh-CN: replace stale "Q1 2026" date with
  timeline-safe wording for Bluetooth terminal support
- es: unify product name to "Stripe Terminal" throughout
- it: unify product name to "Stripe Terminal" throughout
- fr: standardize "sans contact" terminology, fix "tap/insertion" phrasing
- hi-IN: add missing "को" postposition in HTTPS requirement
- ko: remove redundant "활성" in requirement item
- zh-CN: fix duplicated "连接连接", improve MOTO and simulator phrasing

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🧹 Nitpick comments (10)
i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (2)

109-109: Minor punctuation: add comma before "pero".

In Spanish, a comma is typically required before the conjunction "pero" when it connects two independent clauses.

✏️ Suggested fix
-MOTO no está habilitado por defecto. Contacta a [soporte de Stripe](https://support.stripe.com/contact) y pídeles que habiliten los permisos MOTO para tu cuenta. Este es un proceso rápido pero requiere aprobación manual por parte de Stripe.
+MOTO no está habilitado por defecto. Contacta a [soporte de Stripe](https://support.stripe.com/contact) y pídeles que habiliten los permisos MOTO para tu cuenta. Este es un proceso rápido, pero requiere aprobación manual por parte de Stripe.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 109, Update the Spanish sentence in stripe-terminal.mdx to insert a
comma before "pero" so the two independent clauses are correctly separated;
specifically modify the sentence starting "MOTO no está habilitado por defecto.
Contacta a [soporte de Stripe]..." to read "...Este es un proceso rápido, pero
requiere aprobación manual por parte de Stripe." ensuring only the comma is
added before "pero".

166-166: Minor capitalization: consider capitalizing "Obsoleto".

When starting a phrase after a dash in a list item, capitalizing the first word improves consistency with other list items in the section.

✏️ Suggested fix
-- **Verifone P400** ❌ - obsoleto, ya no es compatible con Stripe
+- **Verifone P400** ❌ - Obsoleto, ya no es compatible con Stripe
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 166, Update the list item string "**Verifone P400** ❌ - obsoleto, ya no
es compatible con Stripe" so that the word after the dash is capitalized; change
"obsoleto" to "Obsoleto" to match capitalization style of other list items
(locate the markdown line containing "**Verifone P400** ❌ - obsoleto, ya no es
compatible con Stripe" and update the first character after the dash).
i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (2)

154-155: Wording can be clearer on support vs requirement.

Current phrasing says internet-connected terminals are “required” (必要), but this section is about compatibility/support.

✍️ Suggested wording tweak
-この実装はストライプのJavaScript SDKを使用しており、ウェブアプリケーションを介して機能しますが、**インターネット接続のターミナルのみ**が必要です。現在、Bluetoothターミナルはサポートされていません。
+この実装はストライプのJavaScript SDKを使用し、ウェブアプリケーション経由で動作します。**インターネット接続ターミナルのみ**をサポートしており、現在Bluetoothターミナルはサポート対象外です。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 154 - 155, Change the sentence in stripe-terminal.mdx that
currently reads "インターネット接続のターミナルのみが必要です" to clarify support rather than
requirement — e.g., replace it with
"この実装はインターネット接続のターミナルに対応しており、Bluetoothターミナルはサポートしていません" so the text expresses
compatibility (support) instead of a hard requirement.

17-17: Consider tightening a slightly verbose sentence.

Line 17 uses 「受け付けることができます」, which reads a bit wordy in Japanese docs style.

✍️ Suggested wording tweak
-ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して対面で支払いを受け付けることができます。
+ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使って対面支払いを受け付けられます。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 17, Replace the verbose phrase 「対面で支払いを受け付けることができます」 in the sentence
that starts
「ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して対面で支払いを受け付けることができます。」
with a tighter phrasing such as 「対面で支払いを受け付けます。」 (or 「対面で支払いを受け付けられます。」 if you
prefer passive), keeping the rest of the sentence intact and preserving the
mention of supporting both physical card readers and simulator mode.
i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

162-170: Clarifier que “non supportés” est limité à cette intégration WCPOS Web.

Sur Line 162 et Line 169, la formulation actuelle peut être lue comme une non‑prise‑en‑charge Stripe globale. Ici, c’est surtout une limite de cette implémentation (SDK JS/web). Préciser explicitement la portée éviterait les confusions produit.

✏️ Proposition de reformulation
-### Terminaux Non Supportés (Bluetooth) {`#unsupported-terminals-bluetooth`}
+### Terminaux non pris en charge dans cette intégration (Bluetooth) {`#unsupported-terminals-bluetooth`}

-:::note Support Futur
-La prise en charge des terminaux Bluetooth sera ajoutée aux applications iOS et Android dans une **future mise à jour**. Cela permettra la prise en charge de tous les lecteurs certifiés Stripe Terminal, y compris le M2 et le WisePad 3.
+:::note Évolution prévue
+Dans cette implémentation Web actuelle, les lecteurs Bluetooth ne sont pas pris en charge. Une implémentation native iOS/Android est requise pour ce type de lecteurs.
 :::
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 162 - 170, The "Terminaux Non Supportés (Bluetooth)" section
currently reads as if Stripe globally doesn't support these devices; update the
heading and bullets to explicitly scope the limitation to this WCPOS Web/JS
integration (SDK web) by adding a clarifying phrase like "non supportés par
cette intégration WCPOS Web (SDK JavaScript/web)"; adjust the three bullets
(BBPOS Chipper 2X BT, BBPOS WisePad 3, Verifone P400) to include that scope and
modify the "Support Futur" note to state Bluetooth support will be added to the
iOS/Android apps and to this web integration in a future update so readers
understand the limitation is specific to the web SDK.
i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

154-154: Melhore a fluidez da frase de conectividade.

A redação atual está compreensível, mas pode ficar mais natural em PT-BR com uma inversão simples.

✏️ Proposta de ajuste
-Esta implementação usa o SDK JavaScript do Stripe, o que significa que funciona através de aplicações web, mas requer **terminais conectados à internet apenas**. Terminais Bluetooth não são suportados atualmente.
+Esta implementação usa o SDK JavaScript do Stripe, ou seja, funciona em aplicações web, mas requer **apenas terminais conectados à internet**. Terminais Bluetooth não são suportados atualmente.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 154, Rephrase the sentence in the stripe-terminal.mdx doc that currently
reads "Esta implementação usa o SDK JavaScript do Stripe, o que significa que
funciona através de aplicações web, mas requer **terminais conectados à internet
apenas**. Terminais Bluetooth não são suportados atualmente." to improve PT-BR
fluency by inverting the clauses and smoothing connectors (e.g., make it clear
it works in web apps and that only internet-connected terminals are supported,
while Bluetooth terminals are not). Locate the sentence in the "Stripe Terminal"
section and update the wording to a more natural flow (keep the same meaning and
emphasis on "apenas" for internet-connected terminals and the note that
Bluetooth is unsupported).
i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (2)

147-147: Small phrasing polish for readability.

Current wording is understandable, but this reads more naturally in Arabic: يتطلب إصدار Pro لاستخدام الدفع في نقاط البيع.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 147, Update the Arabic phrasing inside the RequirementItem with label
"WCPOS": replace the current text "يتطلب إصدار Pro الدفع في نقاط البيع" with the
suggested more natural wording "يتطلب إصدار Pro لاستخدام الدفع في نقاط البيع" so
the RequirementItem element reads with the improved Arabic phrasing.

162-167: Consider separating deprecated devices from the Bluetooth-only subsection.

Verifone P400 is now correctly marked deprecated, but it still sits under الأجهزة غير المدعومة (بلوتوث), which can imply the wrong reason for non-support.

Proposed doc-structure tweak
 ### الأجهزة غير المدعومة (بلوتوث) {`#unsupported-terminals-bluetooth`}

 - **BBPOS Chipper 2X BT** ❌ - بلوتوث فقط
 - **BBPOS WisePad 3** ❌ - بلوتوث فقط  
-- **Verifone P400** ❌ - قديم، لم يعد مدعومًا من Stripe
+
+### أجهزة غير مدعومة (قديمة/متوقفة) {`#unsupported-terminals-legacy`}
+
+- **Verifone P400** ❌ - قديم، لم يعد مدعومًا من Stripe
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 162 - 167, The Verifone P400 is listed under the "الأجهزة غير
المدعومة (بلوتوث)" subsection which suggests Bluetooth is the reason; remove the
"Verifone P400" bullet from that Bluetooth-only list and instead add it under a
distinct deprecated/legacy subsection (e.g., "الأجهزة المتقادمة" or "الأجهزة
المهجورة") with the same deprecation note (قديم، لم يعد مدعومًا من Stripe) so
the Bluetooth-only and deprecated reasons are clearly separated; update the
headings and nearby bullets in the "الأجهزة غير المدعومة" area accordingly
(referencing the subsection title "الأجهزة غير المدعومة (بلوتوث)" and the device
name "Verifone P400").
i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

194-194: Keep MOTO label wording consistent.

Line 194 uses “फोन ऑर्डर्स (MOTO)”, while nearby headings use “फोन ऑर्डर (MOTO)”. Prefer one form throughout.

Consistency patch
-  - सुनिश्चित करें कि **फोन ऑर्डर्स (MOTO)** सेटिंग `WooCommerce > Settings > Payments > Stripe Terminal` में सक्षम है
+  - सुनिश्चित करें कि **फोन ऑर्डर (MOTO)** सेटिंग `WooCommerce > Settings > Payments > Stripe Terminal` में सक्षम है
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 194, The string "फोन ऑर्डर्स (MOTO)" in the sentence should be changed
to match the surrounding headings' wording "फोन ऑर्डर (MOTO)"; locate the
occurrence of "फोन ऑर्डर्स (MOTO)" in the Stripe Terminal doc (the sentence
currently starting with "सुनिश्चित करें कि") and replace it with "फोन ऑर्डर
(MOTO)" so the label is consistent across the document.
i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx (1)

157-160: Normalize connectivity terminology for German consistency.

Line 157 and Lines 159-160 mix forms like Internet-Verbunden and WiFi. Consider standardizing to internetverbunden and Wi‑Fi for cleaner, consistent localization.

✏️ Suggested wording cleanup
-### Unterstützte Terminals (Internet-Verbunden) {`#supported-terminals-internet-connected`}
+### Unterstützte Terminals (internetverbunden) {`#supported-terminals-internet-connected`}

-- **Stripe Reader S700/S710** ✅ - Ethernet/WiFi-verbundenes Terminal
-- **WisePOS E** ✅ - WiFi-verbundenes Terminal
+- **Stripe Reader S700/S710** ✅ - Ethernet-/Wi‑Fi-verbundenes Terminal
+- **WisePOS E** ✅ - Wi‑Fi-verbundenes Terminal
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 157 - 160, Standardize the connectivity terms in the heading "###
Unterstützte Terminals (Internet-Verbunden)
{`#supported-terminals-internet-connected`}" and the list items for "Stripe Reader
S700/S710" and "WisePOS E": replace "Internet-Verbunden" with
"internetverbunden" in the heading and change "WiFi" to "Wi‑Fi" in the "Stripe
Reader S700/S710" and "WisePOS E" lines so the localization uses a consistent
German form.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 225-226: The sentence "स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े
जाएंगे ताकि यह दिखा सके:" uses singular pronoun "यह" with plural "स्क्रीनशॉट";
update the pronoun/verb to plural to match — change it to "स्क्रीनशॉट एक भविष्य
के अपडेट में जोड़े जाएंगे ताकि वे दिखा सकें:" (or equivalent plural agreement)
in the same sentence in the Stripe Terminal doc text to fix pronoun agreement.
- Line 154: The sentence about connectivity is grammatically awkward; update the
Hindi sentence that begins "यह कार्यान्वयन..." so it reads naturally by moving
the qualifier to indicate terminals must be internet-connected—for example: "यह
कार्यान्वयन स्ट्राइप के जावास्क्रिप्ट SDK का उपयोग करता है, इसलिए यह वेब
अनुप्रयोगों के माध्यम से काम करता है और केवल इंटरनेट से जुड़े टर्मिनलों का समर्थन
करता है; ब्लूटूथ टर्मिनल वर्तमान में समर्थित नहीं हैं।" Replace the original
sentence on the same line with this clearer phrasing.

In
`@i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 23-26: Replace the inconsistent brand mentions so they use "Stripe
Terminal": update the FeatureCard with title "Terminal Stripe" to "Stripe
Terminal" and change the body text "simulador do Stripe" to "simulador do Stripe
Terminal" inside the FeatureCard with icon="desktop"; ensure both occurrences
use the exact phrase "Stripe Terminal" for consistency with the rest of the
document.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 52-56: Replace the ambiguous phrase "Stripe 密钥" in the Stripe
Terminal setup steps with the explicit term "Stripe 秘密密钥(Secret Key)" so it
matches the English source; locate the occurrence of "Stripe 密钥" in the step
list (the line reading '输入您的 **Stripe 密钥**(您可以从 Stripe 仪表板获取)') and update it to
'输入您的 **Stripe 秘密密钥(Secret Key)**(您可以从 Stripe 仪表板获取)'.

---

Nitpick comments:
In
`@i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 147: Update the Arabic phrasing inside the RequirementItem with label
"WCPOS": replace the current text "يتطلب إصدار Pro الدفع في نقاط البيع" with the
suggested more natural wording "يتطلب إصدار Pro لاستخدام الدفع في نقاط البيع" so
the RequirementItem element reads with the improved Arabic phrasing.
- Around line 162-167: The Verifone P400 is listed under the "الأجهزة غير
المدعومة (بلوتوث)" subsection which suggests Bluetooth is the reason; remove the
"Verifone P400" bullet from that Bluetooth-only list and instead add it under a
distinct deprecated/legacy subsection (e.g., "الأجهزة المتقادمة" or "الأجهزة
المهجورة") with the same deprecation note (قديم، لم يعد مدعومًا من Stripe) so
the Bluetooth-only and deprecated reasons are clearly separated; update the
headings and nearby bullets in the "الأجهزة غير المدعومة" area accordingly
(referencing the subsection title "الأجهزة غير المدعومة (بلوتوث)" and the device
name "Verifone P400").

In
`@i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 157-160: Standardize the connectivity terms in the heading "###
Unterstützte Terminals (Internet-Verbunden)
{`#supported-terminals-internet-connected`}" and the list items for "Stripe Reader
S700/S710" and "WisePOS E": replace "Internet-Verbunden" with
"internetverbunden" in the heading and change "WiFi" to "Wi‑Fi" in the "Stripe
Reader S700/S710" and "WisePOS E" lines so the localization uses a consistent
German form.

In
`@i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 109: Update the Spanish sentence in stripe-terminal.mdx to insert a comma
before "pero" so the two independent clauses are correctly separated;
specifically modify the sentence starting "MOTO no está habilitado por defecto.
Contacta a [soporte de Stripe]..." to read "...Este es un proceso rápido, pero
requiere aprobación manual por parte de Stripe." ensuring only the comma is
added before "pero".
- Line 166: Update the list item string "**Verifone P400** ❌ - obsoleto, ya no
es compatible con Stripe" so that the word after the dash is capitalized; change
"obsoleto" to "Obsoleto" to match capitalization style of other list items
(locate the markdown line containing "**Verifone P400** ❌ - obsoleto, ya no es
compatible con Stripe" and update the first character after the dash).

In
`@i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 162-170: The "Terminaux Non Supportés (Bluetooth)" section
currently reads as if Stripe globally doesn't support these devices; update the
heading and bullets to explicitly scope the limitation to this WCPOS Web/JS
integration (SDK web) by adding a clarifying phrase like "non supportés par
cette intégration WCPOS Web (SDK JavaScript/web)"; adjust the three bullets
(BBPOS Chipper 2X BT, BBPOS WisePad 3, Verifone P400) to include that scope and
modify the "Support Futur" note to state Bluetooth support will be added to the
iOS/Android apps and to this web integration in a future update so readers
understand the limitation is specific to the web SDK.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 194: The string "फोन ऑर्डर्स (MOTO)" in the sentence should be changed to
match the surrounding headings' wording "फोन ऑर्डर (MOTO)"; locate the
occurrence of "फोन ऑर्डर्स (MOTO)" in the Stripe Terminal doc (the sentence
currently starting with "सुनिश्चित करें कि") and replace it with "फोन ऑर्डर
(MOTO)" so the label is consistent across the document.

In
`@i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Around line 154-155: Change the sentence in stripe-terminal.mdx that currently
reads "インターネット接続のターミナルのみが必要です" to clarify support rather than requirement —
e.g., replace it with "この実装はインターネット接続のターミナルに対応しており、Bluetoothターミナルはサポートしていません" so
the text expresses compatibility (support) instead of a hard requirement.
- Line 17: Replace the verbose phrase 「対面で支払いを受け付けることができます」 in the sentence that
starts
「ストライプターミナルゲートウェイを使用すると、WCPOS内でストライプターミナルハードウェアリーダーを使用して対面で支払いを受け付けることができます。」
with a tighter phrasing such as 「対面で支払いを受け付けます。」 (or 「対面で支払いを受け付けられます。」 if you
prefer passive), keeping the rest of the sentence intact and preserving the
mention of supporting both physical card readers and simulator mode.

In
`@i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`:
- Line 154: Rephrase the sentence in the stripe-terminal.mdx doc that currently
reads "Esta implementação usa o SDK JavaScript do Stripe, o que significa que
funciona através de aplicações web, mas requer **terminais conectados à internet
apenas**. Terminais Bluetooth não são suportados atualmente." to improve PT-BR
fluency by inverting the clauses and smoothing connectors (e.g., make it clear
it works in web apps and that only internet-connected terminals are supported,
while Bluetooth terminals are not). Locate the sentence in the "Stripe Terminal"
section and update the wording to a more natural flow (keep the same meaning and
emphasis on "apenas" for internet-connected terminals and the note that
Bluetooth is unsupported).

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 01778eb2-bce1-4884-a522-e598b2706310

📥 Commits

Reviewing files that changed from the base of the PR and between cafe300 and 36ab7dd.

📒 Files selected for processing (10)
  • i18n/ar/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/de/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/es/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/fr/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/it/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/ja/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/ko/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx


:::important कनेक्टिविटी आवश्यकताएँ
यह कार्यान्वयन स्ट्राइप की जावास्क्रिप्ट SDK का उपयोग करता है, जिसका अर्थ है कि यह वेब अनुप्रयोगों के माध्यम से काम करता है लेकिन इसे केवल **इंटरनेट से जुड़े टर्मिनल** की आवश्यकता है। Bluetooth टर्मिनल वर्तमान में समर्थित नहीं हैं।
यह कार्यान्वयन स्ट्राइप के जावास्क्रिप्ट SDK का उपयोग करता है, जिसका अर्थ है कि यह वेब अनुप्रयोगों के माध्यम से काम करता है लेकिन केवल **इंटरनेट-कनेक्टेड टर्मिनल** की आवश्यकता है। ब्लूटूथ टर्मिनल वर्तमान में समर्थित नहीं हैं।
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Clarify the connectivity sentence for natural Hindi.

Line 154 is understandable but grammatically awkward (“...लेकिन केवल ... की आवश्यकता है”). A small rewrite will read more naturally.

Suggested wording tweak
-यह कार्यान्वयन स्ट्राइप के जावास्क्रिप्ट SDK का उपयोग करता है, जिसका अर्थ है कि यह वेब अनुप्रयोगों के माध्यम से काम करता है लेकिन केवल **इंटरनेट-कनेक्टेड टर्मिनल** की आवश्यकता है। ब्लूटूथ टर्मिनल वर्तमान में समर्थित नहीं हैं।
+यह कार्यान्वयन स्ट्राइप के जावास्क्रिप्ट SDK का उपयोग करता है, जिसका अर्थ है कि यह वेब अनुप्रयोगों के माध्यम से काम करता है, लेकिन इसमें केवल **इंटरनेट-कनेक्टेड टर्मिनल** समर्थित हैं। ब्लूटूथ टर्मिनल वर्तमान में समर्थित नहीं हैं।
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
at line 154, The sentence about connectivity is grammatically awkward; update
the Hindi sentence that begins "यह कार्यान्वयन..." so it reads naturally by
moving the qualifier to indicate terminals must be internet-connected—for
example: "यह कार्यान्वयन स्ट्राइप के जावास्क्रिप्ट SDK का उपयोग करता है, इसलिए
यह वेब अनुप्रयोगों के माध्यम से काम करता है और केवल इंटरनेट से जुड़े टर्मिनलों का
समर्थन करता है; ब्लूटूथ टर्मिनल वर्तमान में समर्थित नहीं हैं।" Replace the
original sentence on the same line with this clearer phrasing.

Comment on lines +225 to +226
स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े जाएंगे ताकि यह दिखा सके:
- वूकॉमर्स भुगतान सेटिंग्स में गेटवे कॉन्फ़िगरेशन
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix pronoun agreement in the screenshots sentence.

At Line 225, plural “स्क्रीनशॉट” pairs better with “वे ... सकें” than “यह ... सके”.

Grammar patch
-स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े जाएंगे ताकि यह दिखा सके:
+स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े जाएंगे ताकि वे यह दिखा सकें:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े जाएंगे ताकि यह दिखा सके:
- वूकॉमर्स भुगतान सेटिंग्स में गेटवे कॉन्फ़िगरेशन
स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े जाएंगे ताकि वे यह दिखा सकें:
- वूकॉमर्स भुगतान सेटिंग्स में गेटवे कॉन्फ़िगरेशन
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/hi-IN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 225 - 226, The sentence "स्क्रीनशॉट एक भविष्य के अपडेट में जोड़े
जाएंगे ताकि यह दिखा सके:" uses singular pronoun "यह" with plural "स्क्रीनशॉट";
update the pronoun/verb to plural to match — change it to "स्क्रीनशॉट एक भविष्य
के अपडेट में जोड़े जाएंगे ताकि वे दिखा सकें:" (or equivalent plural agreement)
in the same sentence in the Stripe Terminal doc text to fix pronoun agreement.

Comment on lines +23 to +26
Conecte leitores de Terminal Stripe físicos via conexão com a internet
</FeatureCard>
<FeatureCard icon="desktop" title="Modo Simulador">
Teste pagamentos sem hardware usando o simulador da Stripe
Teste pagamentos sem hardware usando o simulador do Stripe
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Padronize a marca para “Stripe Terminal” nesses trechos.

Em Line 23 e Line 26, ainda há variações (“Terminal Stripe” / “simulador do Stripe”) que quebram a consistência adotada no restante do arquivo.

✏️ Proposta de ajuste
-    Conecte leitores de Terminal Stripe físicos via conexão com a internet
+    Conecte leitores físicos do Stripe Terminal via conexão com a internet

-    Teste pagamentos sem hardware usando o simulador do Stripe
+    Teste pagamentos sem hardware usando o simulador do Stripe Terminal
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Conecte leitores de Terminal Stripe físicos via conexão com a internet
</FeatureCard>
<FeatureCard icon="desktop" title="Modo Simulador">
Teste pagamentos sem hardware usando o simulador da Stripe
Teste pagamentos sem hardware usando o simulador do Stripe
Conecte leitores físicos do Stripe Terminal via conexão com a internet
</FeatureCard>
<FeatureCard icon="desktop" title="Modo Simulador">
Teste pagamentos sem hardware usando o simulador do Stripe Terminal
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/pt-BR/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 23 - 26, Replace the inconsistent brand mentions so they use
"Stripe Terminal": update the FeatureCard with title "Terminal Stripe" to
"Stripe Terminal" and change the body text "simulador do Stripe" to "simulador
do Stripe Terminal" inside the FeatureCard with icon="desktop"; ensure both
occurrences use the exact phrase "Stripe Terminal" for consistency with the rest
of the document.

Comment on lines +52 to 56
1. 导航到 `WP 管理 > WooCommerce > 设置 > 付款`
2. 在支付方式列表中找到 **Stripe Terminal**
3. 点击 **Stripe Terminal** 以访问设置
4. 输入您的 **Stripe 秘密密钥**(您可以从您的 Stripe 控制面板获取
4. 输入您的 **Stripe 密钥**(您可以从 Stripe 仪表板获取
5. 保存设置
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Find the Stripe Terminal docs
all_files=$(fd "stripe-terminal.mdx$" 2>/dev/null || true)
echo "=== Files found ==="
echo "$all_files"
echo

# Separate source and zh-CN versions
source_file=$(echo "$all_files" | grep -v '^i18n/' | head -n 1 || true)
zh_file=$(echo "$all_files" | grep '^i18n/zh-CN/' | head -n 1 || true)

echo "SOURCE FILE: ${source_file:-not found}"
echo "ZH-CN FILE: ${zh_file:-not found}"
echo

# Check the zh-CN file content around lines 52-56
if [[ -n "${zh_file}" && -f "${zh_file}" ]]; then
  echo "=== ZH-CN file content (lines 50-60) ==="
  sed -n '50,60p' "${zh_file}" | cat -n
  echo
fi

# Check for key-related terminology in both files
if [[ -n "${source_file}" && -f "${source_file}" ]]; then
  echo "=== Source file - key terminology context ==="
  rg -n -i 'secret.*key|publishable.*key|stripe.*key|api.*key' "${source_file}" -A2 -B2 || echo "No matches found"
  echo
fi

if [[ -n "${zh_file}" && -f "${zh_file}" ]]; then
  echo "=== ZH-CN file - key terminology context ==="
  rg -n '密钥|秘钥|密钥|Key' "${zh_file}" -A1 -B1 || echo "No matches found"
fi

Repository: wcpos/docs

Length of output: 2742


Clarify the key type to avoid misconfiguration in setup docs.

Line 55 uses "Stripe 密钥", which is a generic translation that differs from the source English text. The source explicitly specifies "Stripe Secret Key", but the zh-CN translation uses the ambiguous term "密钥" (key), which could be mistaken for a publishable key. Please update to "Stripe 秘密密钥(Secret Key)" to match the source clarity and reduce setup failures.

✍️ Suggested edit
-4. 输入您的 **Stripe 密钥**(您可以从 Stripe 仪表板获取)
+4. 输入您的 **Stripe 秘密密钥**(可在 Stripe 仪表板中获取)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
1. 导航到 `WP 管理 > WooCommerce > 设置 > 付款`
2. 在支付方式列表中找到 **Stripe Terminal**
3. 点击 **Stripe Terminal** 以访问设置
4. 输入您的 **Stripe 秘密密钥**(您可以从您的 Stripe 控制面板获取)
4. 输入您的 **Stripe 密钥**(您可以从 Stripe 仪表板获取)
5. 保存设置
1. 导航到 `WP 管理 > WooCommerce > 设置 > 付款`
2. 在支付方式列表中找到 **Stripe Terminal**
3. 点击 **Stripe Terminal** 以访问设置
4. 输入您的 **Stripe 秘密密钥**(可在 Stripe 仪表板中获取)
5. 保存设置
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh-CN/docusaurus-plugin-content-docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx`
around lines 52 - 56, Replace the ambiguous phrase "Stripe 密钥" in the Stripe
Terminal setup steps with the explicit term "Stripe 秘密密钥(Secret Key)" so it
matches the English source; locate the occurrence of "Stripe 密钥" in the step
list (the line reading '输入您的 **Stripe 密钥**(您可以从 Stripe 仪表板获取)') and update it to
'输入您的 **Stripe 秘密密钥(Secret Key)**(您可以从 Stripe 仪表板获取)'.

@wcpos-bot
Copy link
Copy Markdown
Contributor

wcpos-bot Bot commented Mar 5, 2026

Fix Triage Plan — Round 3 (Escalating)

Actionable comments found: 4
Round 3 extension guard FAILED: 4 actionable comments > 3 limit. Escalating to human reviewer.

# Source File Category Plan
1 CodeRabbit hi-IN/stripe-terminal.mdx:154 Minor Escalate: Hindi connectivity sentence grammar
2 CodeRabbit hi-IN/stripe-terminal.mdx:226 Minor Escalate: Hindi pronoun agreement fix
3 CodeRabbit pt-BR/stripe-terminal.mdx:26 Minor Escalate: pt-BR brand name consistency
4 CodeRabbit zh-CN/stripe-terminal.mdx:56 Minor Escalate: zh-CN ambiguous key type clarification

All 4 comments are straightforward translation fixes. A human reviewer can batch-approve or a future round can pick these up if the limit is raised.

@wcpos-bot
Copy link
Copy Markdown
Contributor

wcpos-bot Bot commented Mar 5, 2026

⚠️ Ada needs manual follow-up on this PR.

  • Reason: round_3_extension_guard_failed
  • Details: Round 3 (extension round) requires <= 3 actionable comments to proceed. Found 4 unresolved Minor comments from CodeRabbit (hi-IN grammar x2, pt-BR brand consistency, zh-CN key type clarification). All are straightforward translation fixes but exceed the round 3 threshold. 2 prior fix commits already addressed 20+ comments across 10 languages.
  • Escalation routed to #agent-ops via model-gateway event pipeline.

Posted automatically by model-gateway.

@wcpos-bot wcpos-bot Bot mentioned this pull request Apr 8, 2026
@kilbot
Copy link
Copy Markdown
Contributor Author

kilbot commented Apr 15, 2026

Closing — superseded by #123 which was merged on 2026-03-03.

@kilbot kilbot closed this Apr 15, 2026
auto-merge was automatically disabled April 15, 2026 18:02

Pull request was closed

@kilbot kilbot deleted the translations-2026-03-04 branch April 15, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant