Lingo #151
Lingo #151
Conversation
WalkthroughThis pull request introduces Spanish localization to the documentation site by restructuring the navigation from a single-language model to a multilingual architecture with per-language navigation trees, and adding comprehensive Spanish translations of API reference documentation and changelog entries. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Key areas requiring attention:
Possibly related PRs
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 16
♻️ Duplicate comments (3)
es/api-reference/payouts/get-payouts.mdx (1)
1-5: Add comprehensive API reference documentation beyond frontmatter stub.Same issue flagged in es/api-reference/disputes/get-disputes-1.mdx. Refer to that review comment for details on required API documentation elements (parameters, responses, examples, error codes).
es/api-reference/subscriptions/patch-subscriptions.mdx (1)
1-5: Add comprehensive API reference documentation beyond frontmatter stub.Refer to the detailed review comment on es/api-reference/disputes/get-disputes-1.mdx.
es/api-reference/webhooks/update-webhook-headers.mdx (1)
1-5: Add comprehensive API reference documentation beyond frontmatter stub.Refer to the detailed review comment on es/api-reference/disputes/get-disputes-1.mdx.
🧹 Nitpick comments (8)
es/api-reference/licenses/get-license-key-instance.mdx (1)
1-5: Inconsistent frontmatter field ordering across API reference files.This file orders frontmatter as
title, description, openapi, while other files (e.g., get-disputes-1.mdx) useopenapi, title, description. Establish a consistent field order across all API reference stubs to improve maintainability and reduce automation friction.Additionally, this file is incomplete. Add comprehensive API documentation as noted in the previous review comment.
es/api-reference/licenses/validate-license.mdx (1)
1-5: Standardize frontmatter field ordering across API reference files.This file orders frontmatter as
title, description, openapi, while most other files useopenapi, title, description. Enforce a consistent order across all files for predictability and to support documentation automation.es/api-reference/webhooks/get-webhook-signing-key.mdx (1)
1-5: Frontmatter is complete. Minor note: The description uses imperative form ("Obtén") while all other descriptions in the PR use infinitive form ("Recuperar", "Crear", etc.). Consider standardizing to infinitive for consistency.es/api-reference/payments/get-payments-1.mdx (1)
1-5: Frontmatter complies with standards, but filename needs clarification.The YAML frontmatter is correct with proper title and description fields. However, the filename
get-payments-1.mdxuses a numeric suffix that lacks clarity. Consider renaming toget-payment-detail.mdxor similar to clearly distinguish this detail endpoint from the list endpoint, improving discoverability and maintainability.es/api-reference/transaction-failures.mdx (1)
28-73: Add punctuation after bullet list introductory lines.Lines 19-22 introduce the list but lack terminal punctuation. Per Spanish grammar conventions for formal documentation, each introductory line should end with a colon (
:) to properly introduce the list that follows.- Proporcionar retroalimentación clara a sus clientes - Implementar una lógica de reintento apropiada - Manejar diferentes escenarios de fallo de manera elegante - Mantener un sistema de procesamiento de pagos confiable + Proporcionar retroalimentación clara a sus clientes. + Implementar una lógica de reintento apropiada. + Manejar diferentes escenarios de fallo de manera elegante. + Mantener un sistema de procesamiento de pagos confiable.es/api-reference/metadata.mdx (1)
36-78: Consider adding Spanish comments to code examples for clarity.The code examples are well-structured but use English comments. Since this is Spanish-language documentation, adding Spanish comments would improve clarity for Spanish-speaking developers who may not be as comfortable with English variable names and explanations.
This is an optional improvement; the current examples are still understandable because the API method names and properties are in English regardless.
es/api-reference/discounts/validate-discount.mdx (1)
1-6: Incomplete API reference page—needs implementation.This file contains only frontmatter but no body content. Per coding guidelines for API documentation (
**/*.mdx), endpoint pages should include:
- Clear explanation of the endpoint purpose (introductory paragraph)
- Use cases section
- Request parameters (
<ParamField>for path, query, header, body)- Response examples with realistic data (
<ResponseField>or response blocks)- Error handling guidance
The frontmatter description indicates the validation endpoint purpose, but the actual documentation needs to be implemented before publication.
Would you like me to generate the complete implementation for this endpoint page based on the coding guidelines and patterns used in the other API reference files?
es/changelog/v0.15.1.mdx (1)
1-8: Consider using component for semantic versioning markup.Per coding guidelines and learnings, versioned changelog entries should use the
<Update>component to document changes with clear labels and descriptions. This improves semantic clarity and consistency across the documentation.Additionally, static analysis (LanguageTool) has flagged several Spanish grammar and capitalization issues throughout this changelog:
- Line 10: Capitalization issue with section heading
- Line 16: Sentence structure issue in "Actualizaciones de la Plataforma"
- Line 22: Grammar issue in "Mejoras en la Documentación"
- Line 27: Capitalization issue with "Mejoras y Corrección de Errores"
- Line 30: Style preference suggests alternative phrasing instead of "a nivel de"
Please review and address these grammar and style suggestions.
| --- | ||
| openapi: get /checkout/supported_countries | ||
| title: Obtener Países Soportados | ||
| description: Recuperar una lista de todos los países soportados para el checkout | ||
| --- No newline at end of file |
There was a problem hiding this comment.
Align title and description terminology.
The title uses "Obtener" (line 3) while the description uses "Recuperar" (line 4)—both convey similar meaning. Choose one verb and apply consistently across this endpoint and related documentation.
🤖 Prompt for AI Agents
In es/api-reference/checkout/get-checkoutsupported_countries.mdx around lines 1
to 5, the title uses "Obtener" while the description uses "Recuperar"; make verb
usage consistent by choosing one verb and applying it to both fields (e.g.,
change the title to "Recuperar Países Soportados" or change the description to
start with "Obtener una lista..."), then scan related endpoint docs to ensure
the same verb is used across similar checkout endpoints.
| --- | ||
| title: Validar Licencia | ||
| description: Este endpoint te permite validar una licencia para el usuario. | ||
| openapi: post /licenses/validate | ||
| --- | ||
|
|
||
| <Info> | ||
| **No se requiere clave API**: Este es un endpoint público que no requiere autenticación. Puedes llamarlo directamente desde aplicaciones cliente, software de escritorio o CLIs para validar claves de licencia sin exponer tus credenciales de API. | ||
| </Info> No newline at end of file |
There was a problem hiding this comment.
Add comprehensive request/response documentation and examples.
While this file includes an component (good), it still lacks essential API documentation elements:
- No parameter documentation ( for body parameters)
- No response schema documentation ()
- No example request/response payloads
- No HTTP status codes (200, 400, 401, etc.)
- No error handling details
- No rate limiting information
Per coding guidelines for API reference docs, include complete request/response cycles with realistic examples and all relevant status codes.
🤖 Prompt for AI Agents
In es/api-reference/licenses/validate-license.mdx lines 1-9, the doc only
contains title/description and an Info note but is missing full API reference
details; add ParamField entries describing the request body schema (fields,
types, required/optional, validation rules), add ResponseField entries for each
relevant status code (200 success with license validation result,
400/401/422/500 with error schemas), include realistic example request and
response payloads for success and common errors, document HTTP status codes and
error handling behavior, and add a note about rate limits and any
authentication/usage constraints per the API reference guidelines.
| --- | ||
| openapi: post /tu-url-de-webhook | ||
| --- No newline at end of file |
There was a problem hiding this comment.
Missing required frontmatter fields: title and description.
Per coding guidelines, every documentation page must begin with YAML frontmatter containing title and description. This file only contains the OpenAPI endpoint reference. All other API reference files in this PR include these fields.
Add the missing fields:
---
openapi: post /tu-url-de-webhook
+title: Enviar a tu URL de webhook
+description: Enviar un webhook a tu URL configurada.
---Please verify the exact Spanish translation for the title and description that aligns with your documentation standards.
🤖 Prompt for AI Agents
In es/api-reference/outgoing-webhooks/post-your-webhook-url.mdx around lines 1
to 3, the file is missing required YAML frontmatter fields `title` and
`description`; add a YAML frontmatter block at the very top containing a Spanish
`title` and `description` that match your docs conventions (e.g., a concise
Spanish title for the webhook endpoint and a one-line Spanish description), then
keep the existing openapi line below the frontmatter; verify the exact Spanish
wording with the documentation team or style guide before committing.
| --- | ||
| openapi: post /subscriptions/{subscription_id}/change-plan | ||
| title: Cambiar Plan | ||
| description: Modifica el plan de una suscripción existente, permitiendo tanto | ||
| actualizaciones como degradaciones a diferentes niveles de | ||
| precios.<br/><br/>Nota: Esto utilizará la información de pago existente | ||
| del cliente para actualizar/degradar el plan. | ||
| --- No newline at end of file |
There was a problem hiding this comment.
Remove HTML markup from YAML frontmatter description.
The description field (lines 4-7) contains HTML entities (:) and line breaks (<br/>) that should not appear in YAML frontmatter. Frontmatter must use plain text only. This can cause YAML parsing errors and inconsistent rendering.
Apply this correction:
---
openapi: post /subscriptions/{subscription_id}/change-plan
title: Cambiar Plan
- description: Modifica el plan de una suscripción existente, permitiendo tanto
- actualizaciones como degradaciones a diferentes niveles de
- precios.<br/><br/>Nota: Esto utilizará la información de pago existente
- del cliente para actualizar/degradar el plan.
+ description: Modifica el plan de una suscripción existente, permitiendo tanto actualizaciones como degradaciones a diferentes niveles de precios. Nota: Esto utilizará la información de pago existente del cliente para actualizar/degradar el plan.
---Also add comprehensive API documentation as noted in earlier review comments.
📝 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.
| --- | |
| openapi: post /subscriptions/{subscription_id}/change-plan | |
| title: Cambiar Plan | |
| description: Modifica el plan de una suscripción existente, permitiendo tanto | |
| actualizaciones como degradaciones a diferentes niveles de | |
| precios.<br/><br/>Nota: Esto utilizará la información de pago existente | |
| del cliente para actualizar/degradar el plan. | |
| --- | |
| --- | |
| openapi: post /subscriptions/{subscription_id}/change-plan | |
| title: Cambiar Plan | |
| description: Modifica el plan de una suscripción existente, permitiendo tanto actualizaciones como degradaciones a diferentes niveles de precios. Nota: Esto utilizará la información de pago existente del cliente para actualizar/degradar el plan. | |
| --- |
🤖 Prompt for AI Agents
In es/api-reference/subscriptions/change-plan.mdx around lines 1 to 8, the YAML
frontmatter description contains HTML tags/entities ("<br/>" and ":") and
manual line breaks; replace these with plain text only (remove HTML, use proper
punctuation and spacing), e.g. a single plain-language sentence explaining the
endpoint and the payment-note, and ensure the description is YAML-safe (no
angle-bracket tags or HTML entities). Also expand the file to include the full
API documentation requested in prior reviews: request/response schemas,
path/parameter details for subscription_id, HTTP method, example requests and
responses, status codes, and any notes about payment reuse and behavior on
upgrades/downgrades.
| <Info> | ||
| Para listar los métodos de pago existentes de un cliente, utiliza la [API de Listar Métodos de Pago](/api-reference/customers/get-customer-payment-methods). Esto te ayuda a recuperar los IDs de métodos de pago disponibles al usar `type: "existing"` para actualizar el método de pago de una suscripción. | ||
| </Info> |
There was a problem hiding this comment.
Update internal link to Spanish path prefix.
Line 22 references a payment methods API endpoint. This should use the es/api-reference/* path for Spanish documentation consistency:
-Para listar los métodos de pago existentes de un cliente, utiliza la [API de Listar Métodos de Pago](/api-reference/customers/get-customer-payment-methods).
+Para listar los métodos de pago existentes de un cliente, utiliza la [API de Listar Métodos de Pago](/es/api-reference/customers/get-customer-payment-methods).📝 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.
| <Info> | |
| Para listar los métodos de pago existentes de un cliente, utiliza la [API de Listar Métodos de Pago](/api-reference/customers/get-customer-payment-methods). Esto te ayuda a recuperar los IDs de métodos de pago disponibles al usar `type: "existing"` para actualizar el método de pago de una suscripción. | |
| </Info> | |
| <Info> | |
| Para listar los métodos de pago existentes de un cliente, utiliza la [API de Listar Métodos de Pago](/es/api-reference/customers/get-customer-payment-methods). Esto te ayuda a recuperar los IDs de métodos de pago disponibles al usar `type: "existing"` para actualizar el método de pago de una suscripción. | |
| </Info> |
🤖 Prompt for AI Agents
In es/api-reference/subscriptions/update-payment-method.mdx around lines 21 to
23, the internal link to the payment methods API uses the non-localized path
(/api-reference/customers/get-customer-payment-methods); update the href to the
Spanish localized path by changing it to
/es/api-reference/customers/get-customer-payment-methods so the doc links
consistently to the Spanish docs.
| ## Nuevas Funciones 🚀 | ||
|
|
||
| - **Función de Resumen de Cuenta**: Proporciona visibilidad detallada sobre los libros de transacciones y pagos. | ||
| <img src="/images/changelog/account_summary.png" alt="Resumen de Cuenta" /> |
There was a problem hiding this comment.
Wrap image in <Frame> component.
Per coding guidelines, all images must be wrapped in <Frame>. The bare <img> tag needs to be enclosed in a Frame wrapper.
Apply this diff to fix the image wrapping:
- **Función de Resumen de Cuenta**: Proporciona visibilidad detallada sobre los libros de transacciones y pagos.
- <img src="/images/changelog/account_summary.png" alt="Resumen de Cuenta" />
+ **Función de Resumen de Cuenta**: Proporciona visibilidad detallada sobre los libros de transacciones y pagos.
+ <Frame><img src="/images/changelog/account_summary.png" alt="Resumen de Cuenta" /></Frame>📝 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.
| <img src="/images/changelog/account_summary.png" alt="Resumen de Cuenta" /> | |
| <Frame><img src="/images/changelog/account_summary.png" alt="Resumen de Cuenta" /></Frame> |
🤖 Prompt for AI Agents
In es/changelog/v0.16.1.mdx around line 11, the bare <img> tag must be wrapped
in the <Frame> component per coding guidelines; replace the standalone <img
src="/images/changelog/account_summary.png" alt="Resumen de Cuenta" /> with the
same <img> element enclosed inside a <Frame>...</Frame> wrapper so the image is
rendered within the Frame component.
| ## Nuevas Funciones 🚀 | ||
|
|
||
| - **Soporte para Chat de IA**: Ahora puedes chatear con nuestro asistente de IA para obtener ayuda con tus consultas técnicas o consultar la documentación de manera más efectiva. | ||
| <img src="/images/changelog/ai_chat.png" alt="Soporte de Chat de IA de Dodo Payments" /> |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Use Mintlify <Frame> component instead of raw <img> tag.
Per coding guidelines, all images must be wrapped in the Mintlify <Frame> component (which supports optional captions). The raw <img> tag bypasses the framework's image handling and component consistency.
Apply this diff:
- <img src="/images/changelog/ai_chat.png" alt="Soporte de Chat de IA de Dodo Payments" />
+ <Frame>
+ <img src="/images/changelog/ai_chat.png" alt="Soporte de Chat de IA de Dodo Payments" />
+ </Frame>📝 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.
| <img src="/images/changelog/ai_chat.png" alt="Soporte de Chat de IA de Dodo Payments" /> | |
| <Frame> | |
| <img src="/images/changelog/ai_chat.png" alt="Soporte de Chat de IA de Dodo Payments" /> | |
| </Frame> |
🤖 Prompt for AI Agents
In es/changelog/v0.18.0.mdx around line 11, replace the raw <img> tag with the
Mintlify <Frame> component (e.g. <Frame src="/images/changelog/ai_chat.png"
alt="Soporte de Chat de IA de Dodo Payments" caption="Soporte de Chat de IA de
Dodo Payments" />) and remove the <img>; if the file doesn’t already import
Frame, add the appropriate Mintlify Frame import at the top of the file. Ensure
the src and alt values match the original image and add a caption if desired.
|
|
||
| - **Método de Pago UPI QR**: Se agregó UPI QR como método de pago para el mercado indio, permitiendo a los clientes pagar utilizando códigos QR de UPI. | ||
|
|
||
| <img src="/images/changelog/upi-qr.png" alt="Función UPI QR"/> |
There was a problem hiding this comment.
Wrap image in <Frame> component.
Per coding guidelines, all images must be wrapped in <Frame>. The UPI QR image needs a Frame wrapper.
Apply this diff:
- **Método de Pago UPI QR**: Se agregó UPI QR como método de pago para el mercado indio, permitiendo a los clientes pagar utilizando códigos QR de UPI.
-
- <img src="/images/changelog/upi-qr.png" alt="Función UPI QR"/>
+ **Método de Pago UPI QR**: Se agregó UPI QR como método de pago para el mercado indio, permitiendo a los clientes pagar utilizando códigos QR de UPI.
+
+ <Frame><img src="/images/changelog/upi-qr.png" alt="Función UPI QR"/></Frame>📝 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.
| <img src="/images/changelog/upi-qr.png" alt="Función UPI QR"/> | |
| **Método de Pago UPI QR**: Se agregó UPI QR como método de pago para el mercado indio, permitiendo a los clientes pagar utilizando códigos QR de UPI. | |
| <Frame><img src="/images/changelog/upi-qr.png" alt="Función UPI QR"/></Frame> |
🤖 Prompt for AI Agents
In es/changelog/v0.22.0.mdx around line 16, the image tag <img
src="/images/changelog/upi-qr.png" alt="Función UPI QR"/> must be wrapped in a
<Frame> component per guidelines; replace the standalone <img> with a <Frame>
that contains the <img> (maintain src and alt attributes) and ensure any
necessary import or surrounding JSX/MDX syntax is preserved so the file
compiles.
|
|
||
| - **Widget de Ayuda Centralizado**: Se agregó un widget de Ayuda centralizado para agilizar y mejorar el soporte. | ||
|
|
||
| <img src="/images/changelog/help-widget.png" alt="Widget de Ayuda"/> |
There was a problem hiding this comment.
Wrap image in <Frame> component.
Per coding guidelines, all images must be wrapped in <Frame>. The help widget image needs a Frame wrapper.
Apply this diff:
- **Widget de Ayuda Centralizado**: Se agregó un widget de Ayuda centralizado para agilizar y mejorar el soporte.
-
- <img src="/images/changelog/help-widget.png" alt="Widget de Ayuda"/>
+ **Widget de Ayuda Centralizado**: Se agregó un widget de Ayuda centralizado para agilizar y mejorar el soporte.
+
+ <Frame><img src="/images/changelog/help-widget.png" alt="Widget de Ayuda"/></Frame>📝 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.
| <img src="/images/changelog/help-widget.png" alt="Widget de Ayuda"/> | |
| <Frame><img src="/images/changelog/help-widget.png" alt="Widget de Ayuda"/></Frame> |
🤖 Prompt for AI Agents
In es/changelog/v0.22.0.mdx around line 55, the help widget image is not wrapped
in the required <Frame> component; update the file by replacing the raw <img
src="/images/changelog/help-widget.png" alt="Widget de Ayuda"/> with the image
wrapped inside a <Frame> component (e.g., <Frame>...image...</Frame>) so the
image follows the project's coding guidelines.
| - Se introdujo la funcionalidad para crear y agregar cupones de descuento a sus productos y servicios. Puede crear cupones con descuentos porcentuales, establecer fechas de caducidad y más. Vaya a `Dashboard > Sales > Discounts` para crear y gestionar cupones de descuento. | ||
|
|
||
| - Dodo Payments ahora admite más de 25 métodos de pago locales, incluidos Apple Pay, Google Pay, Klarna, Affirm, Cash App, UPI y todas las principales tarjetas de crédito/débito. Esto ayuda a aumentar las conversiones y reducir las abandonos en el proceso de pago. | ||
|
|
||
| <Frame> | ||
| <iframe | ||
| className="w-full aspect-video rounded-md" | ||
| src="https://www.youtube.com/embed/bf9_2iXWZOA" | ||
| title="Anuncio de Métodos de Pago Locales | Dodo Payments" | ||
| frameBorder="0" | ||
| allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" | ||
| allowFullScreen | ||
| ></iframe> | ||
| </Frame> | ||
| - Se agregó la funcionalidad para personalizar el descriptor de estado que aparece en los estados bancarios de sus clientes cuando realizan un pago. Puede encontrar la opción para personalizar el descriptor de estado en `Dashboard > Business > Business Profile`. | ||
|
|
||
| - Renovación completa de la interfaz de usuario de la página de inicio de sesión de Dodo Payments. |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Inconsistent feature bullet formatting.
Feature bullet points lack bold titles, which is inconsistent with the established pattern in other changelog entries (e.g., - **Feature Name**: description). This file uses plain dashes without title bolding on lines 12, 14, 26, and 28, while other v0.x and v1.x changelog entries consistently bold feature titles for clarity and scannability.
Standardize the formatting to match the established pattern:
- - Se introdujo la funcionalidad para crear y agregar cupones de descuento a sus productos y servicios. Puede crear cupones con descuentos porcentuales, establecer fechas de caducidad y más. Vaya a `Dashboard > Sales > Discounts` para crear y gestionar cupones de descuento.
+ - **Cupones de Descuento**: Se introdujo la funcionalidad para crear y agregar cupones de descuento a sus productos y servicios. Puede crear cupones con descuentos porcentuales, establecer fechas de caducidad y más. Vaya a `Dashboard > Sales > Discounts` para crear y gestionar cupones de descuento.
- - Dodo Payments ahora admite más de 25 métodos de pago locales, incluidos Apple Pay, Google Pay, Klarna, Affirm, Cash App, UPI y todas las principales tarjetas de crédito/débito. Esto ayuda a aumentar las conversiones y reducir las abandonos en el proceso de pago.
+ - **25+ Métodos de Pago Locales**: Dodo Payments ahora admite más de 25 métodos de pago locales, incluidos Apple Pay, Google Pay, Klarna, Affirm, Cash App, UPI y todas las principales tarjetas de crédito/débito. Esto ayuda a aumentar las conversiones y reducir los abandonos en el proceso de pago.
- - Se agregó la funcionalidad para personalizar el descriptor de estado que aparece en los estados bancarios de sus clientes cuando realizan un pago. Puede encontrar la opción para personalizar el descriptor de estado en `Dashboard > Business > Business Profile`.
+ - **Descriptor de Estado Personalizable**: Se agregó la funcionalidad para personalizar el descriptor de estado que aparece en los estados bancarios de sus clientes cuando realizan un pago. Puede encontrar la opción para personalizar el descriptor de estado en `Dashboard > Business > Business Profile`.
- - Renovación completa de la interfaz de usuario de la página de inicio de sesión de Dodo Payments.
+ - **Renovación de UI de Página de Inicio de Sesión**: Renovación completa de la interfaz de usuario de la página de inicio de sesión de Dodo Payments.Note: The diff also corrects "reducir las abandonos" to "reducir los abandonos" (article agreement in Spanish).
🧰 Tools
🪛 LanguageTool
[grammar] ~14-~14: Cambia la forma del articulo.
Context: ...a a aumentar las conversiones y reducir las abandonos en el proceso de pago. ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_DETERMINER_FORM)
[style] ~26-~26: Se recomienda emplear una alternativa al verbo comodín ‘realizar’.
Context: ...stados bancarios de sus clientes cuando realizan un pago. Puede encontrar la opción para...
(REALIZAR)
🤖 Prompt for AI Agents
In es/changelog/v0.24.0.mdx around lines 12 to 28, the four feature bullets are
missing bolded titles and one sentence has an article agreement typo; update
each bullet to follow the established pattern "- **Feature Name**: description"
(bold the short feature title for the coupon feature, the expanded local payment
methods feature, the statement-descriptor customization feature, and the login
UI revamp) keep the iframe block intact inside the payment-methods bullet, and
correct "reducir las abandonos" to "reducir los abandonos".
2 participants
📋 Description
🎯 Type of Change
📖 What documentation does this PR affect?
✅ Checklist
mintlify devdocs.json(if applicable)🧪 Testing
📸 Screenshots (if applicable)
🔗 Related Issues
Closes #
📝 Additional Notes
👥 Reviewers
@dodopayments/documentation-team
Summary by CodeRabbit
New Features
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.